-
Notifications
You must be signed in to change notification settings - Fork 1
Migrate docs to mkdocs #12
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Pawel Langowski <[email protected]>
@@ -110,18 +110,11 @@ to generate detailed code documentation automatically. | |||
To generate the documentation run the following: | |||
|
|||
```bash | |||
(venv) make html | |||
(venv) mkdocs serve | |||
python -m http.server 8000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mkdocs serve already starts http server, so below python command should not be necessary anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PLangowski do you plan to address this?
Comparing the overall look and feel After: In my opinion it looks so much worse... It was @macpijan idea/request to migrate to mkdocs: #5 (comment) so maybe he can review as well. |
@miczyg1 I agree, it's much less readable. |
@macpijan Have you looked at this? |
@macpijan we would like to have the release by the end of the week. We would appreciate your review and opinion about mkdocs vs sphinix. I would also prefer mkdocs, but the question is how to make it look reasonable. |
Have you researched alternative themes or mkdocs @PLangowski ? |
No description provided.