-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Freeze Sphinx content to Markdown #2084
Conversation
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Co-authored-by: Gonzalo Peña-Castellanos <goanpeca@gmail.com>
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.
It appears that some of the static content images have been moved? This may break the status page again.
We should either keep the links the same or go back and fix the status page later. |
When we fixed it last time we pinned the commit hash, so it should be ok. |
One awesome part of having in everything in Docusaurus is that we can leverage the cool bits of the JS world. Like this live editor with built-in preview: |
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.
Looks good to me. Thanks for doing this!
PR Checklist:
note any issues closed by this PR with closing keywords
put any other relevant information below
Part of Redesigning conda-forge.org #1971
In the last conda-forge core call meeting, we discussed the pros and cons of removing the render-to-markdown pipeline altogether because the maintenance complexity was not worth in the long run and Sphinx was not providing any features we were really missing in Docusaurus. In this PR I have rendered
/docs
permanently and reworked some00_intro.html
pages with Docusaurus-equivalent features (card lists, mostly).