There’s a section on writing in the lesswrong faq (named Posting & Commenting). If any information is missing from there, you can suggest adding it in the comments.
Of course, even given that such instructions exists somewhere, it’s important to make sure that it’s findable. Not sure what the best way to do that is.
Copying all relevant information from the lesswrong faq to an EA forum faq would be a good start. The problem of how to make its existence public knowledge remains, but that’s partly solved automatically by people mentioning/linking to it, and it showing up in google.
I suggest a putting a “help” button in the editor, right next to the “save as draft” and “submit” buttons. This info should be super easy to find when someone’s writing a post.
Relatedly, when the instructions are being refreshed for the planned update I think it’s important to run them by someone non-technical (and probably at least one generation older than the person writing the instructions) to see if they can understand them.
There’s a section on writing in the lesswrong faq (named Posting & Commenting). If any information is missing from there, you can suggest adding it in the comments.
Of course, even given that such instructions exists somewhere, it’s important to make sure that it’s findable. Not sure what the best way to do that is.
Copying all relevant information from the lesswrong faq to an EA forum faq would be a good start. The problem of how to make its existence public knowledge remains, but that’s partly solved automatically by people mentioning/linking to it, and it showing up in google.
I suggest a putting a “help” button in the editor, right next to the “save as draft” and “submit” buttons. This info should be super easy to find when someone’s writing a post.
Relatedly, when the instructions are being refreshed for the planned update I think it’s important to run them by someone non-technical (and probably at least one generation older than the person writing the instructions) to see if they can understand them.