-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Remove mdbook, transition docs to Docusaurus #10806
Conversation
@danpaul000 looks like we'll need to adjust the |
Docusaurus has no search feature? That's a bummer. I use that in gitbook all the time :-/ |
Why did everything in |
How does the deployment work? |
@mvines Docusaurus does have search — we just have to deploy it first and then we can use https://docsearch.algolia.com/apply/ |
@danpaul000 That's how Docusaurus structures their markdown compartmentalization. I can rename the internal folder to whatever you might want, e.g. |
We can either use GitHub Pages, Netlify, Vercel, or any other static site host. I've used Vercel for the beta.docs.solana.com deployment just for ease of use. |
Yeah, |
Oh we're going to want to backport this to 1.2, heads up! |
Can we wait on the backport to soak test master and whatever deployment changes? I really don't want to break the main docs branch, we are getting a lot of traffic there lately. |
💯 |
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.
I'll review again once docs/src
is restored, too much churn here otherwise
@rmshea, Rebase? |
@danpaul000, are you working on CI changes for this? |
yeah, looking in to it |
* Delete gitattributes and other theme related items
* all docs need to be moved to /docs * can be changed in the future
* initialize docusaurus repo
* No need to rename the folder! Change a setting and we're all good to go.
Open items for integration:
I'm not sure what is the right approach to use the native docusaurus versioning setup, which has all versions as separate subdirs, rather than separate branches (https://v2.docusaurus.io/docs/versioning#directory-structure), unless we build this dynamically and push to a docs repo. Their UI for jumping between versions of docs is nice, and doesn't require separate domains, ie beta.docs.solana.com, edge.docs.solana.com. It should look similar to gitbook setup, ie docs.solana.com/v1.2.0, docs.solana.com/v.1.1.0. @garious I can work on some of this later but don't think I'm going to be able to get it all over the line today. More likely EOW. |
docs/src/css/custom.css
Outdated
--ifm-color-primary-lightest: #abd5c6; | ||
--ifm-code-font-size: 95%; | ||
--ifm-spacing-horizontal: 1em; | ||
--ifm-font-family-base: "Rubik", system-ui, -apple-system, Segoe UI, Roboto, Ubuntu, Cantarell, Noto Sans, sans-serif, BlinkMacSystemFont, 'Segoe UI', Helvetica, Arial, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; |
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.
Does our style guide offer any different typefaces for multi-paragraph text? Rubik looks great in small chunks on solana.com, but I find it uncomfortable to read in the context of the docs, especially in dark mode.
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.
@CriesofCarrots let me ask Raj and see what we can do. I agree with this completely. Maybe we can keep Roboto.
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.
@CriesofCarrots let me know if you are a fan of Roboto!
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.
Yes, I am!
@danpaul000 — let me know what you'd like my help with in terms of addressing your items above. |
@danpaul000, any news here? Is this being worked on someplace else? |
* Some fonts are hard to read. Others, not so much. Rubik, you've been sidelined. Roboto, into the limelight! * As much as we all love tutorials, I think we all can navigate around a markdown file. Say goodbye, `mdx.md`.
Problem
Gitbook, while it remains a formidable documentation rendering solution, has provided a myriad of issue for our purposes. We're moving back to Solana-hosted and controlled docs with a formal transition to Docusaurus, a React-based Markdown renderer with plenty of flexibility and functionality.
You can see the current Docusaurus implementation here.
Summary of Changes