Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DRAFT] Add documentation #117

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from
Draft

[DRAFT] Add documentation #117

wants to merge 4 commits into from

Conversation

BowTiedRadone
Copy link
Collaborator

This PR adds the Rendezvous documentation. It is still a draft. Resolves #108.

This commit adds the table of contents for the Rendezvous docs.
Copy link
Member

@moodmosaic moodmosaic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good! Thank you @BowTiedRadone. I think the nested layout can easily get out of sync? I was thinking having a flat structure like https://github.com/moodmosaic/bookmarks. Easy to scan, harder to accidentally break. Also, users no longer read the web, they scan it and perhaps a flat layout is easier. What do you think?

@moodmosaic
Copy link
Member

After some consideration, we'll try https://rust-lang.github.io/mdBook/.

Initialized `mdbook` in `docs/`, tweaking `book.toml` to fit our flat layout.
Renamed `book/` to `dist/`, since that's where built assets go (GitHub Pages
friendly). Instead of `src/`, we keep markdown files in the root for clarity.

Now, anyone browsing `docs/` can actually see the docs—whether they
read the book or just skim the pages.
Inserted placeholder content for all sections to outline a possible
structure. Adopted a flat directory layout temporarily, to simplify
navigation and organization.
Copy link
Collaborator Author

@BowTiedRadone BowTiedRadone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fantastic! The structure is exactly what we need! I'm pretty sure we can start adding text content to the docs from this point 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Usage documentation
2 participants