Repository navigation
Moving docs to a separate repo + using another tool for its maintaining #1334
Closed
andrii-bodnar
started this conversation in
Ideas
Replies: 2 comments 2 replies
|
Think this is a very good change. I would love to help out. I could sponsor a version of the Tailwind UI Protocol template. It's a more bespoke package than a docusaurus or nextra. But it keeps things simple and uses Next, MDX and tailwind as its core. |
2 replies
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I would like to discuss the possibility to move the Docs into a separate repo alongside its redesign and migrating to some modern documentation framework.
Storing the documentation code along with the rest of the code (monolithic repository):
Pros:
Cons:
Storing the documentation code in a separate repository:
Pros:
Cons:
Also, there are a lot of popular and great tools for docs management, for example:
These tools are based on MD/MDX which is the leading way of managing documentation nowadays (this discussion has already had place before - #837).
In the case of using such tools, it makes even more sense to split the docs into a separate repository.
All reactions