-
Notifications
You must be signed in to change notification settings - Fork 69
Migrate docs to mkdocs #253
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
Conversation
for more information, see https://pre-commit.ci
|
Lovely, go for it I just setup readthedocs builds for PRs so we can get a preview. Hope this just needs another commit to be triggered |
|
Yep, that tricked the did. |
|
Out of the box so much better! One thing is now that we lost all git file history when renaming to Basically, it just needs a rename commit at the beginning (instead of 5287890). But I can also fix that before we merge with some git magic, so that's fine |
I'll let you do the magic under the condition that you teach me (the) magic. |
|
TODO post merge of #254 :
|
fneum
left a comment
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.
Excellent!
for more information, see https://pre-commit.ci
Sorry @lkstrp , I over eargerly merged and forgot about your comment. |
I was wasting time with SPHINX and considered it to be faster to migrate to
mkdocs.I tried to migrate as much as closely as possible, but I introduced some changes to be a bit more consistent and foreward looking towards a harmonised doc structure with
pypsav1 docs.Checklist
doc.doc/release_notes.rstof the upcoming release is included.