Post History

Since no one has posited anything yet...

I think everything but the last three bullets can be kept. Other than that, we could add in the tips about challenge specifications.

## Challenges

> ### Posting Tips
>
> - Your title should be a one sentence summary of your question.
> - Break different topics up into paragraphs. Multiple paragraphs are easier to read than a wall of text.
> - Use clear, simple language. Be specific.
> - Reread your post before saving (preferably out loud) and rewrite anything that sounds awkward.
> - Challenges should have a **clear specification**, with which entries can objectively be said to be valid.
> - Including test cases and an example (un-golfed) solution is encouraged.
> - Challenges should also have **objective winning criteria**.
> - If you are unsure about your challenge, please post in the [Sandbox](https://codegolf.codidact.com/categories/50) before release.

## Sandbox

Basically the same thing except for the last line

> ### Posting Tips
>
> - Your title should be a one sentence summary of your question.
> - Break different topics up into paragraphs. Multiple paragraphs are easier to read than a wall of text.
> - Use clear, simple language. Be specific.
> - Reread your post before saving (preferably out loud) and rewrite anything that sounds awkward.
> - Challenges should have a **clear specification**, with which entries can objectively be said to be valid.
> - Including test cases and an example (un-golfed) solution is encouraged.
> - Challenges should also have **objective winning criteria**.
> - Try to note down specific questions you have instead of asking for blanket feedback.