-
Notifications
You must be signed in to change notification settings - Fork 62
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
Documentation #20
Comments
I'd prefer /docs, for no good reason other than Personal preference. I'm not a huge fan of docusaurus tbh and I'd prefer nextra as it integrates nicely into the nextjs app. There's a nextjs13 compatible repo/guide by github.com/shadcn/taxonomy I'll have to check out mintlify |
But either way it'll be markdown I suppose, so we can start on content. |
I'll check out nextra, it does seem like it integrates nicer with Next13 (and yeah content is the most important) |
If you want I can setup the docs and you start on actual content |
That'll work for me! I have a notion doc where I'm working on the content, I havent had the time to spin up the actual doc implementation so if you can get it up, I'll fill it out |
This Notion doc I have is a running list of the content that the documentation will have: Feel free to leave comments (I was going to allow it to be editable but the problem is that this gh issue is publicly viewable and I worry about people finding it and editing the notion doc 😂 ) |
I'm thinking of starting the documentation for EnvShare (docs.envshare.com or envshare.com/docs) that'll host information pertaining to the service.
It will have
Any other thoughts/ideas?
I tend to use mintlify/docusaurus for documentation so it can be easily hosted on Vercel or GH Pages.
The text was updated successfully, but these errors were encountered: