codewars / blog Goto Github PK

Proposed by @kazk:

I'd like to have a post summarizing what was done in 2020 and 2021 so far.

• Finished huge backend refactoring with significant performance improvements
• Finished huge frontend refactoring, modernizing tools, and improved UX by making navigation much snappier
• Created the community team and added many features for them to moderate
• Started to work on the new documentation with the community team
• New languages: Prolog, CFML, COBOL, Lean, Haxe, CommonLisp, Perl, Raku, Pascal

To keep the post short, I think I will just organize the points in a form of an overview without too many specifics, and then create a follow-up post on points which deserve it.

Listing page does not distinguish between old and new posts, making it difficult to spot whether new posts were published recently. Provide some visual clue that a post is new: newer than some time threshold, not read, or added after the last visit of a viewing user, or some other criteria.

Ideas:

• replace Forum in the left menu with Blog ( I don't know how that would work in a mobile version of the page - I don't use that )
• if there's a new post, send notifications like for new translations ( and ranks? - it's been a while )
• or, if you don't want to do that, just in the top right corner thingy

Create a post announcing that the moderation team has been formed, and explain how it could be helpful for users.

I wonder whether (and how) it would be necessary to stress the fact that moderators are "officially recognized" thing.

I am also not sure how detailed the post should be.

Blocked by codewars/docs#250

Create a post announcing documentation for Codewars.

• explain ideas behind it
• encourage users to contribute and explain how
• provide some insight about plans for it

• Link to new server.
• Explain or hint rules of Discord server. Link to server readme.
• Encourage to share feedback.

Possibly could be combined or accompanied by #21 . I think an explicit post would make authors aware why it's needed and prevent occurrences of such: https://www.codewars.com/kata/5b7c80094a6aca207000004d/discuss#600c14a4a4982600221d4a62 or https://www.codewars.com/kata/598d91785d4ce3ec4f000018/discuss#600c0ea383491c002b5adf45 or https://www.codewars.com/kata/586e6d4cb98de09e3800014f/discuss#600c15faa49826001c1d880a when authors do not admit the problem because "it works".

• announce the list,
• explain why kata have to be updated,
• encourage users (especially authors) to fix kata
• provide links to Python documentation to inform users how to update kata: https://docs.codewars.com/languages/python/authoring/#testing-framework and https://docs.codewars.com/languages/python/codewars-test/#python-codewars-test-framework

From this blog post: https://blog.codewars.com/2021/updates-from-the-past-year/#new-languages

We've added support for the following languages: Prolog, CFML, COBOL, Lean, Haxe, CommonLisp, Perl, Raku, and Pascal.

[...] Many of the existing languages were also updated to newer versions. More details will be provided in a dedicated post.

Create a post which lists added languages and updates with the potentially biggest impact:

• changes in APIs and testing frameworks, or changes visible directly to users, like finally fixed, annoying issue in Snowhouse
• the fact that some kata do not work anymore and need to be updated (links to lists), encourage users to fix them
• encourage users to provide new content for beta languages
• credit users who helped setting up the runner

Maybe the previous post on the topic: https://blog.codewars.com/2019/new-languages/ could be used for inspiration?

@kazk it would be nice to have a list of recently updated languages, I guess it can be extracted from the runner board? How far back should it go? I think not all updates have to be listed, just ones with the biggest impact on authors.

Not all features are of any interest for regular users, but some of them would be worth to be announced, so users know that some specific issue can be addressed in general:

[...]

• Let mods hide solution group from the list (audited)
• Let mods invalidate solution group without verifying (audited)
• Let mods recalculate buggy beta votes (audited)
• Let mods unpublish beta kata (audited)
• Let mods remove rank assessments and votes (audited)

[...]

• inform users that some issues are now possible to be handled
• ask users to report problematic instances, so mods could handle them
• say "thanks" to maintainers who did the hard work of implementing these

Announce content issues board when it finally gets organized (*cough* @hobovsky *cough*)

• explain why it was created,
• encourage users to report problematic content,
• encourage users to fix problems with content which can be handled by community.