writing-guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| writing-guide [May 25, 2026 at 13:29] – Ivan Janevski | writing-guide [June 11, 2026 at 00:00] (current) – removed Ivan Janevski | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | # Writing guide | ||
| - | Every article should preferably start with a main section followed by a few paragraphs. | ||
| - | ## Sections | ||
| - | Sections should have a certain flavor. For example, if a section is titled "List of concepts related to X" it should only contain a list and no additional description. Similarily, if a section is titled "C++ code illustrating X" it should only contain a code block and preferably no prose. Any additional description can be added in the code comments. Same goes for equations. A section like " | ||
| - | |||
| - | The first section should preferably always start with a paragraph that starts with the name of the article in **bold** followed by a short description (two-three sentences) of what the concept is. The subsequent paragraphs should expand the concept in the most nautral way. | ||
| - | |||
| - | ## Code block | ||
| - | A code block is a larger piece of code that. Preferably all code blocks should be self-contained MVEs (minimum viable examples). At the top there should be a comment block on how to compile and run the code. | ||
| - | |||
| - | ```cpp | ||
| - | // Compile: | ||
| - | // Run: | ||
| - | // Description: | ||
| - | |||
| - | #include < | ||
| - | |||
| - | int main() | ||
| - | { | ||
| - | printf(" | ||
| - | return 0; | ||
| - | } | ||
| - | ``` | ||
writing-guide.1779715794.txt.gz · Last modified: by Ivan Janevski
