-
Notifications
You must be signed in to change notification settings - Fork 52
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
Set up Docusaurus #534
Set up Docusaurus #534
Conversation
This is ready for initial feedback, note that the setup isn't polished and needs some clean-up |
Considering we have both Actually we could also separate the community section into another sidebar (thought about this for nebari too) as the main sidebar can grow a lot and hide the sections |
Following up since I forgot to ask - shall we add Netlify here so we can get website previews? I find it really useful when reviewing PRs and making changes to the website as some settings/features are slightly different when developing locally and in "production" mode within Docusaurus. |
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 left a couple of minor comments, overall all looks good and I would like to get this merged ASAP so we can start iterating on this.
Will approve and if you get those minor changes in you can merge @pavithraes
@trallard Thanks for your review and suggestions! I've moved your comments(#534 (comment) and #534 (comment)) to corresponding issues where we can address them individually. I'll merge this PR with the blank files so that we have files to re-arrange to test the multi-instance setups (i.e., separate community docs, etc.). |
Addresses #397
Set up the Docusaurus skeleton and a documentation structure. Took a lot of inspiration from the nebari setup: nebari.dev
Note:
and I think it does; won't be committing them, will open new issues to track the work.Preview:
Screen.Recording.2023-08-11.at.5.45.15.AM.mov