Designing the documentation #78
Labels
No Label
automation
bug
community organising
democracy
design
documentation
duplicate
enhancement
finance
funding
help wanted
invalid
publishing
question
security
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#78
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I think it would be great to think about how to design the documentation now that we have time and money for it. In our proposal we said we'd do:
I am thinking about some examples that I thought were wonderful:
Any other examples people know about? It might be cool to try to get in touch with people who are doing this kind of documentation and see if they want to work with us.
We might want to orientate it around "roles", so, individual, tech co-op, tech collective.
mkdocs
is pretty rad I think, so I am fine with sticking with it as the technical tool underneath if others are. Also we need to think about #74.I really like the idea of the "Public Stack" and its docs:
You can click on the blocks on the left and it unpacks them. That is nice.
Manga assisted docs!