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

[POC] Developer Documentation Revamp using mkdocs #14179

Closed
wants to merge 10 commits into from

Conversation

relrod
Copy link
Member

@relrod relrod commented Jun 28, 2023

SUMMARY

I started on this a few months ago, and dusted it off and did some more work on it tonight.

Just a proof of concept for what would dev docs could look like using mkdocs.

I moved the docs files around to roughly organize them, but I am not happy with the organization yet.

mkdocs-material (the theme I am using here) has a "tags" feature which helps to group documents together, and I think this is more useful than the directory structure. But the directory structure determines the hierarchy of the navbar on the left of the site.

Front page 📄

image

Tags index 🏷️

image

Search 🔍

image

Built-in Mermaid graphs(!) 📈

image

ISSUE TYPE
  • Bug, Docs Fix or other nominal change
COMPONENT NAME
  • Docs

relrod added 10 commits July 5, 2023 13:39
…layout yet though

Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
Signed-off-by: Rick Elrod <rick@elrod.me>
run: |
mkdocs build --clean

# TODO: Deploy the site somewhere (gh pages?)
Copy link
Member

Choose a reason for hiding this comment

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

Reading up on the limitations of this... github pages seem to want an index.html at the root level. Since this would be an artifact of the build process, we probably don't want to keep that in source ourselves. Then the URL would be somewhat limited, as we could have maybe http://ansible.github.io/awx, which would maybe be okay, maybe not.

Given what other projects are doing...

I would just assume we go with readthedocs.io

@relrod relrod closed this Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants