To make sure we have consistent format, here are the guidelines we have tried to keep for writing Sponge Documentation.
Headings Should Be Written in Title Case (<- example)
Page headings should be meaningful (the heading appears as a link)
Program code is contained in quotes or code blocks
i. Try not to put too much text in - code blocks are not translated
Separate areas for Users, Plugin Devs, and Sponge Devs
Avoid repetition by sharing pages where possible
Link to external resources rather than reproduce them
i. Some exceptions are made for translation purposes
Make distinction between Sponge (coremod), SpongeVanilla and Sponge API
If it looks awful in your language, invent your own rules
Sponge is the project Title and preferably should NOT be translated.
i. Some languages may wish to use a phonetic translation as well
Automated translations (eg. Google Translate) are strongly discouraged. These often contain serious errors, and are very likely to be rejected
Page Titles and Headings should use plain text, avoiding literal blocks and other formatting.
References to class names should have no extra spaces (eg. blockstate, not block state) and be formatted as a literal (eg. ``class``)
Lines should have a maximum length of 120 characters.
Imports should be written out in code blocks the first time they are referenced in each article, but not repeated after the first time.
This list may get added to (or bent out of shape) as the Docs get bigger, and is reproduced in Contributing to Spongedocs
I hope this helps our Contributors and Translators.
Contributions, suggestions and corrections are always welcome.
After discussion with some of the docs team, a new Style guideline has been added:
. 9. Sponge is the project Title and preferably should NOT be translated.
. Some languages may wish to use a phonetic translation as well.
Basically, Sponge is the product name - a proper noun. It’s like a corporate brand, and should not be translated unless there is no reasonable alternative. For some alphabets, a phonetic translation may be helpful.
The preferred option is to use the word “Sponge” in the English alphabet, the same as it appears in the code. For good or ill, English is embedded in Sponge, Java, and the Internet at large.
One more guideline to add, which has been SpongeDocs policy for some time:
.10. Automated translations (eg. Google Translate) are strongly discouraged. These often contain serious errors, and are very likely to be rejected.
Please don’t waste your time providing un-reviewed Google translations (or similar). Anyone can do that for themselves, and they would rapidly discover how unreliable it is.
A new guideline has been added regarding import statements.
So when you write a page that contains code snippets make sure that for every class / static method that is used there is exactly one import statement, namely at the beginning of the first code snippet to use that class/method.
Good to have this 
