Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
53 lines (27 sloc) 4.71 KB

How to help

To help with the project, start by copying the contents of the post template into a new markdown file.

The name of the markdown file should be a very short topic description, and placed in a subfolder based on the community.

Using the template

The template should be clear (or clear once you submit a pull request to improve it!) on the front matter components, what they are for, and how they should be configured.

It should also be clear on the sections that should be included, their order, and what they should contain. Text that should be changed is [written in brackets]. Comments on what a section should contain {::comment}are surrounded by Kramdown comment markup{:/}, which will not be rendered in the final website.

Be careful with the yaml front matter. Text can generally be entered without quotes, but if your text contains yaml special characters (sorry, that link sucks) you need to surround your text in 'single quotes'. If your text contains single quotes and the front matter displays atypically in the preview (as code rather than as a table), surround the entire line in single quotes and escape the single quote in your text by doubling it. E.g., you don't say becomes 'you don''t say'


Acceptable subjects are problems that attract downvotes that can be reversed. If a post is not salvageable (i.e., nothing can be done to reverse the downvote), then the subject probably shouldn't be broached here. Problems that can only be solved by deleting the post, thereby gaining back lost reputation points, should be kept to an absolute minimum. It is hard to keep a positive and helpful tone when the only thing you can tell someone to do is "delete your post". These should only be created for extraordinary circumstances.


Be conscious of the tone of your topic. Talk about the problem as if it was its own entity, not the result of what any specific person did. If you aren't sure what this means, check the history of this document for an example.

Avoid the use of pronouns. Pages must state facts as they exist. Don't speak of an individual's actions. For example, consider the following paragraph:

If their question is important enough to ask, it should be important enough for them to check back regularly to respond to anyone commenting on it. If they ignore their question, they're also ignoring people who are trying to help them. Their time spent analyzing their question, asking for clarification, and waiting for a response is wasted. If they provide an answer that ends up being incorrect, the time spent on that is wasted. Wasting the time of people who are trying to help them is seen as very rude.

When correctly rewritten to avoid all pronouns:

If a question is important enough to ask, it's important enough to check back regularly to respond to anyone commenting on it. Ignoring a question means ignoring people who are trying to help. Time spent analyzing the question, asking for clarification, and waiting for a response is wasted. If an answer is provided that ends up being incorrect, that time is wasted, as well. Wasting the time of people who are trying to help is generally considered quite rude.

Note that any references to individuals that remain are in the third person.

Pages must not make asumptions that could shed a dire light on the subject. For example, this is not acceptable:

Homework questions show laziness and often attract downvotes.

This is making the asumption that the user is lazy. Not only does it not help, it can also make readers feel insulted or targeted. Instead:

Homework questions are often frowned upon by users as they are generally low quality and show little effort in learning the assigned material.

Again, try to avoid targeting users in any way. They are likely to be upset already and feel that they are being personally down-voted. Re-enforcing this felling will not help the website contribute to their learning.


Images should be stored under /images in a subfolder by community (the same as the one you are posting about). Try to keep images as small as possible, focusing on what is important. We don't want to see your browser tabs. Also, images without freehand circles will be rejected. More freehand circles, pls.


Prefer https over http for outgoing links. For organizations that are https only (e.g., Stack Overflow), make sure all their links are https.


The site uses Kramdown for markdown processing. It's got some special features over and above standard markdown. Here's a quick reference guide to its syntax.

You can’t perform that action at this time.