id | title | desc | updated | created | documentId | revisionId |
---|---|---|---|---|---|---|
ebpudfrf6rg5uut75d29lhg |
Standard Documentation |
1655334184660 |
1651791209320 |
1DD6ROb22u-BpLeSY_WUlqedMqVCI25wm-gB6EXw0liI |
ALm37BW7VAZzSGhBaAheH7CbILKCGcs-bHKa36Lcv6j2ghpsb7cKWc7c9XUmVbA_QnTZWyg2avSgftzVn8h04w |
This leaflet proposes some general guidelines for the Dendron public docs.
-
Goals:
- make it umnabiguous where to add docs on features and capabilities
- make it umnabiguous where to find docs on features and capabilities
- identify gaps in tooling that will make refactoring into and applying the standard easier in future iterations
-
Non-goals:
- every note be 100% the same: we are still iterating on this standard and it will likely change in the future. it is more important we have a standard that people can follow than an XML spec that accounts for every possible permutation of docs
-
NOTE: this note was exported from this note. If certain links don't resolve, check the original note on github
For the purposes of this discussion, howtos/reference/discussions/tutorials refer to the four types of documentation
A topic branch is a feature in Dendron. It is represented using [[dendron.topic]] hierarchy
There are two areas that this leaflet addresses.
- the overall structure of the docs
- the structure for features
This leaflet proposes the following changes:
- simplify user guide (less children)
- simplify dendron.* hierarchy to be product related topics
- make contribution its own top level hierarchy
- rename "Guides" to "How tos"
Resulting hierarchhy:
- dendron
- dendron.quickstart (Getting Started)
- dendron.user-guide (User Guide)
- Basic
- Edit
- Retrieve and Navigate
Navigation-
fold into Retrieve
-
OrganizeStructure-
Rename to
Structure (Organization and Format)
-
Refactoring-
Fold into
Structure (Organization and Format)
-
- Sharing and Syncing
Transferring-
Rename to
Sharing and Syncing
-
- Extending
dendron.principles-
fold into
dendron
home page
-
FAQ-
move under
dendron.resource
-
dendron.contribute-
move to
contribute
(becomes top level hierarchy)
-
dendron.guides-
Rename to
dendron.howtos
(How)
-
- dendron.concepts (Concepts)
- dendron.ref (Reference)
- dendron.res (Resources)
- dendron.res.faq
- dendron.res.troubleshooting
- dendron.res.support
- contribute
-
everything from dendron.contribute gets moved here
-
- community
- changelog
- careers
All features today are added in the form dendron.topic.{feature}[.{sub-feature}|{sub-component}]
These are headers for features and are directly inside dendron.topic.{feature}
[[dendron://dendron.dendron-site/templates.topic]] (NOTE: link on handbook won't resolve on website, url: https://github.com/dendronhq/dendron-site/blob/dev/vault/templates.topic.md#L9:L9)
These are the children of features and are located in dendron.topic.{feature}.*
[[Topic|dendron://dendron.dendron-site/dendron.contribute.documentation.tutorial.topic]] (NOTE: link on handbook won't resolve on website. url: https://github.com/dendronhq/dendron-site/blob/dev/vault/dendron.contribute.documentation.tutorial.top-level-feature.md#L8:L8)
![[dendron://dendron.handbook/leaflet.journal.2022.05.10.standard-documentation.references]]
- [[PR refactoring a topic branch to new format|dendron://private/proj.2022.06-standard-docs.conv.refactor-pr]]