Table of contents about community-handbook HOT 5 CLOSED

This is the moment when we need to understand and/or decide tooling for converting from Markdown files to a webpage.

This should be handled by the GitHub Pages process. We should be able to hand it the source for a "book" as as Markdown file with an organized table of contents of (all the) .md files.

For now, let's start a mock-ToC for what we have and what we want to have. We can put in stubs for content that doesn't exist, too. For some ideas, we can look to the slidedeck from Nuritzi & Jaskirat that has these suggested areas:

About: Mission, Vision, Values, History, Governance model, Code of Conduct

Teams/Groups: how to onboard onto each team, and specific processes that they follow

Handbook: How to use the handbook

Social: How to meet other community members and tools you use to communicate

Another slide notes these topics in their handbook:

About
Community
Contributing
Mentorship

That is also in the CHAOSS repo for testing GitBook.

Maybe a short meeting to or Slack with whiteboard to get some clarity on all this? I wonder who else in the community is interested in documentation tools and knows a bit about what can be done with GitHub Pages?

from community-handbook.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from community-handbook.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

from community-handbook.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

from community-handbook.

@sesheta: Closing this issue.

from community-handbook.