Documentation Site
See original GitHub issueHi @cristianbote,
Congratulations on creating goober! I’ve created a documentation website and would like to check if you like the idea of having a website for goober. The website was created using Docusaurus 2 and is currently hosted at https://gooberjs.github.io. I’ve also invited you to the organization gooberjs
that I created for hosting additional resources in the future.
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Docusaurus: Build optimized websites quickly, focus on your ...
An optimized site generator in React. Docusaurus helps you to move fast and write content. Build documentation websites, blogs, marketing pages, and more....
Read more >4. Building a Documentation Site - Working with Static Sites ...
The first characteristic of a documentation site is that they tend to have multiple, and often numerous, contributors. In the case of project...
Read more >Read the Docs: Home
Read the Docs simplifies technical documentation by automating building, versioning, and hosting for you. Build up-to-date documentation for the web, print, ...
Read more >docsify
A magical documentation site generator. Simple and lightweight; No statically built html files; Multiple themes. GitHub Getting Started.
Read more >MkDocs
Project documentation with Markdown. MkDocs is a fast, simple and downright gorgeous static site generator that's geared towards building project documentation.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
woohoo! That did it! @vandreleal! 👍 Thank you so much! 😄
Wooow!
Thank you @vandreleal! Much appreciate the effort! Amazing! 👍 😃
Do you think a new organisation for
gooberjs
would be a great fit? I’ve played around with the idea a while back as well, trying to consolidate the ecosystem, and it felt a bit odd to me.My reasoning was that for documentation, like you’ve so amazingly generated the docs 🎉 , a
docs
folder in the main repo would do it. Then for the rest of packages, they could live under thepackages
folder due to tight integration between the main source. Which if they would be to be moved outside the main repo some sort of package alias orchestration should have to happen and I am not that good at it nor I want to spend time on it.Also this relates to #112.
Would you be open to move the docs and pages into the main repo?
Thank you so much! Waw, I’m blown away by this. Amazing.