Author style guide: Difference between revisions
m (Craig Calcaterra moved page DGF Wiki Author Style Guide to Author Style Guide) |
|||
| Line 6: | Line 6: | ||
# More convergent vision of the document, so it helps resolve debates. | # More convergent vision of the document, so it helps resolve debates. | ||
The goal is to build an accurate, useful, and attractive document. | |||
We will try to follow most of the conventions of Wikipedia. For example, each time a term is used for the first time on a page, it is linked to the page/section that defines it. The second and later time it is used, there is no link. We follow Wikipedia’s style guide for three reasons. First, out of respect for the best decentralized organization ever created. Second, because people have already trained themselves how to navigate the pages, so it will lead to greater learning efficiency. Third, if we have an improvement, we should first try to convince Wikipedia to change. | |||
== Page Structure == | == Page Structure == | ||
| Line 14: | Line 15: | ||
'''Top:''' | |||
Overview | |||
Contents = Links to sections in current page | |||
'''Bottom:''' | |||
links to | |||
# Mathematical formulas related to this Subject | |||
# Code Related to this Subject | |||
# See also [internal links] | |||
# Notes [footnotes for this page] | |||
# Citations [auto generated footnotes with shorthand for the full references below] | |||
# References | |||
# External links | |||
'''Bottom Bottom:''' smaller font grey | |||
<small>Members; Contributors’ Guide; general announcements...</small> | |||
'''Body''' | |||
Split into 3 sections, based on information theory triad: | |||
1. Overview/judgements/perceptions/ info storage | |||
Current conclusions on the subject | |||
[Followed by Contents Links] 2. Why?/theory/legislation/thought/ info processing | |||
History | |||
Why it's right | |||
Future | |||
3. Execution/action/ info transmission | |||
Applications | |||
Each of these subjects can be further broken down into subsections along the same lines. If necessary, within the page, but preferably in a linked page for that subject. | |||
= See Also = | = See Also = | ||
[[Contributors Guide]] | |||
Revision as of 09:14, 26 February 2023
Design Considerations
Wiki self-similar design leads to better
- Understanding/navigation/learning
- Quicker Wiki development
- More convergent vision of the document, so it helps resolve debates.
The goal is to build an accurate, useful, and attractive document.
We will try to follow most of the conventions of Wikipedia. For example, each time a term is used for the first time on a page, it is linked to the page/section that defines it. The second and later time it is used, there is no link. We follow Wikipedia’s style guide for three reasons. First, out of respect for the best decentralized organization ever created. Second, because people have already trained themselves how to navigate the pages, so it will lead to greater learning efficiency. Third, if we have an improvement, we should first try to convince Wikipedia to change.
Page Structure
This is the archetypical design for organizing the content in each page on the DGF Wiki.
Top:
Overview
Contents = Links to sections in current page
Bottom:
links to
- Mathematical formulas related to this Subject
- Code Related to this Subject
- See also [internal links]
- Notes [footnotes for this page]
- Citations [auto generated footnotes with shorthand for the full references below]
- References
- External links
Bottom Bottom: smaller font grey
Members; Contributors’ Guide; general announcements...
Body
Split into 3 sections, based on information theory triad:
1. Overview/judgements/perceptions/ info storage
Current conclusions on the subject
[Followed by Contents Links] 2. Why?/theory/legislation/thought/ info processing
History
Why it's right
Future
3. Execution/action/ info transmission
Applications
Each of these subjects can be further broken down into subsections along the same lines. If necessary, within the page, but preferably in a linked page for that subject.