Author style guide

The DGF Style Guide describes the overarching theme of the DGF Wiki. In short, follow the currently accepted DGF wiki page template.

Design Considerations

Wiki self-similar design leads to better

1. Understanding/navigation/learning
2. Quicker Wiki development
3. 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.
• Lengths of pages should be constrained above and below. A page that is too complicated should be summarized and split into multiple pages. A page that is too short is a stub and should be elaborated. Otherwise it should be deleted and reincorporated in the root page.

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:

Short intro

Contents = Links to sections in current page Overview

Bottom:

links to

1. Detailed design of this subject
2. Applications
3. Mathematical formulas related to this subject
4. Code related to this subject
5. Downloads available for this subject
6. See also [internal links]
7. Notes [footnotes for this page]
8. Citations [auto-generated footnotes with shorthand for the full references below]
9. References

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.

Typography

When defining a term, use italics. For example: "The minting ratio determines the proportional number of REP minted to the fee."

Reference style

Articles

Author1 First Name Second Name & Author2 & ... (Date published) "Title", Publisher.

Available at: http://website (Retrieved date: year month day)

Example:

Craig Calcaterra & Wulf Kaal & Vlad Andrei (2018 February 18) "Blockchain Infrastructure for Measuring Domain Specific Reputation in Autonomous Decentralized and Anonymous Systems", University of St. Thomas (Minnesota) Legal Studies Research Paper No. 18-11. Available at SSRN: https://ssrn.com/abstract=3125822 or http://dx.doi.org/10.2139/ssrn.3125822 (Retrieved 2023 April 11)

Books

Author1 First Name Second Name & Author2 & ... (Date published) Title, Publisher.

Available at: http://website (Retrieved date: year month day)

Example:

Craig Calcaterra & Wulf Kaal (2021) Decentralization, De Gruyter, pp. 57-59.

See Also

• Code Formatting
• Contributors guide
• Ethical considerations
• Governance philosophy
• Guiding principles
  • Individual code of conduct
  • Group governance code of conduct
• Transcendental Values