-
Notifications
You must be signed in to change notification settings - Fork 18
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
docs(mkdocs): migrating documentation engine #221
docs(mkdocs): migrating documentation engine #221
Conversation
Added dependencies to pyproject.toml under docs group |
f4bb8f5
to
99996fa
Compare
Could you please review it, @Saransh-cpp? Also, the tests seem to be failing because |
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.
Thanks for working on this, @Naman-Priyadarshi!
79a6ea0
to
7c6733c
Compare
7c6733c
to
846f452
Compare
Hey @Saransh-cpp , just a friendly reminder for the PR review! 😄 |
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.
Thanks for working on this, @Naman-Priyadarshi! The website looks really good now. Could you please also add site/
to .gitignore
?
I have made the requested changes, but it appears there are conflicts. Could you help me resolve these? I haven't solved conflicts using an IDE like VSCode before. I'm accustomed to using a web editor for conflict resolution, but that doesn't seem to be an option here |
Something like this should work:
Once done, you'll see that the command errors out. Go to the "Source Control" tab in VS Code (left pane) and you'll see files under "Merge changes" (IIRC) there. These are the files that have conflicts. Open the file from there itself and VS Code will show you the conflicted lines of code. You can then select which lines you want to keep using the VS Code GUI. Once the conflicts are resolved -
Let me know if you need assistance over a google meet! |
I'll try this and let you know! 😄 |
So, I used these commands and now git is listing that I have a lot of files to be committed
|
…o migrate-doc-engine
Thank You @Saransh-cpp , this did the trick! |
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.
Thanks, @Naman-Priyadarshi! This looks amazing now!
🎉 This PR is included in version 0.7.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Pull Request description
Migrates the documentation engine of SciCookie from Jupyterbook to mkdocs with material theme
Fixes #176
How to test these changes
mkdocs serve
Pull Request checklists
This PR is a:
About this PR:
Author's checklist:
Additional information
I have not yet added the dependencies to SciCookie's installation files.Also, have not removed the config files for jbookThe dependencies are:
markdown-callouts>=0.2
mkdocs>=1.3.1
mkdocs-include-exclude-files>=0.0.1
mkdocs-jupyter>=0.21
mkdocs-material>=8.3.9
mkdocstrings-python>=0.7.1
mkdocstrings-python-legacy>=0.2.3
pymdown-extensions>=9.5
Reviewer's checklist
Copy and paste this template for your review's note: