-
-
Notifications
You must be signed in to change notification settings - Fork 628
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: introduce documentation website #2279
Conversation
I'd like to balance "light and simple to navigate" vs "complete" so feel free to push on these suggestions. What do you think about adding:
happy to discuss that later and if we agree to add have as a later change |
we could potentially use https://mysql2.js.org domain . To get it we would need to open https://github.com/js-org/js.org/pulls PR and get it approved and merged |
Yes, in a simple way, Docusaurs can be seen as a React App that parses markdowns to React Components ⚛️ So we have a flexible way to create documentations using both markdown ( The "stability" badge for example, could be a React page. An important point is that it should be easy to maintain by:
I don't get it 😟 By lastly, you can set a custom domain on GitHub Pages settings, case not, it will be the default https://sidorares.github.io/node-mysql2 🌞 |
see "history" blocks in nodejs docs, for example here https://nodejs.org/api/async_hooks.html#class-asynchook Basically an earliest version before which documented api cannot be used |
This comment has been minimized.
This comment has been minimized.
Hey @sidorares, a simple question about options: A or B?
|
Both look good, I trust your taste here |
@sidorares, finally, it's ready 🎉✨ Notes
What's Next?
An Overview of the New Sections
|
Just some refinements and a Donate following link to https://github.com/sponsors/sidorares 🧑🏻🔧 |
sorry very busy last few days but I promise I'll give some attention very soon! |
Hey, everything's fine. |
its live 🎉 Thank you for this amazing effort @wellwelwel ❤️ I'll think about domain later and next steps in improving documentation ( I have few new topics in mind for FAQ ) but this is already looking very very good |
Yeah 🎉 The second step would be to remove the "old" docs and examples from
I'd like to get this done before I go on my vacation 🌞 |
@sidorares , a small suggestion would be to flag the "Use your GitHub Pages website" on repository details: Then: |
done, thanks for the suggestion! |
Introducing a documentation website 🦖✨
How it works (for now)?
gh-pages
) and compile the website in this branch.gh-pages
branch, it will create a GitHub URL (https://sidorares.github.io/node-mysql2) with this branch contentpackage.json
andpackage-lock.json
are separate from main code.Required actions:
Before merge it:
Read and write permissions
.After merge it:
Deploy from a branch
gh-pages
Unofficial temporary favicon (this isn't a logo):
TODO
.md
filesHistory
Stability
FAQ
Tech stack includes:
.tsx
files).mdx
files).scss
files).ts
files)Naturally, ask any questions you like 🧙🏻
To discuss (resolved)
promise-based
first.