I am facing some challenges writing editorials for a round. Some of them were discussed in this blog.
Now I am preparing my second Div. 2 contest (which is going to take place soon!) and I came to a point, where I want to start writing the editorial for the problemset.
My first contest was a total success in terms of editorial, it got heavily upvoted. Here are some key factors, which might have to do with it:
- Problems. First and foremost, if the people were to hate the problems, it would definitely affect the rating of the editorial. Good problems are an essential part.
- Timing. I published the editorial less than a minute after the contest, so more people would actually read it. Don't be like tourist in the recent rounds :D
- Hints and spoilers in general. The editorial doesn't look messy, you can open only the tasks you need and hints are a great thing when trying to actually improve reading an editorial. Treat hints as if they're as important as the problem statements.
- Implementations. My approach here was based on not copy-pasting the code to the blog, but actually making all the needed submissions after the contest and then add the links to the editorial. This way one could actually see, that the code is working, not look at some plain (or colored) text. This took a few hours, since you can't submit before the system testing is done. I had solutions in both C++ and python, which is nice for python CPers.
- Responsiveness. There will be typos and bugs in the editorial, listen to the people, that are trying to point them out. Even the small inconsistencies might affect the understanding of a bunch of people. Especially the last problems, which are often overlooked, since very few actually read it.
There are a few adjustments that I might propose for codeforces team:
- Let us add solutions for the problems beforehand, not after the system testing. By this, I mean automatically give access to the pre-written solutions after the round ends (I know you already make the submissions to test beforehand, just make them public).
- Post the editorial automatically after the round ends.
I have questions to the more experienced problemsetters:
- How do you synchronize editorials in Polygon and Codeforces blog? I like the idea of keeping everything in one place, which is Polygon for me. But with every small change I have to paste it to the blog by hand. Like, this is cringe.
- How do you write editorial with spoilers in Polygon so that it doesn't say
use quotes like ``text'' instead of "text" in tutorial. I am a perfectionist, I don't like this warning :(
Any other advice would be highly appreciated.