You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So sphinx-collections is designed to give the user a free choice of how the documentation is structured.
It just allows to collect the different parts into a joint, single folder-structure during the build.
I think the above quote by @danwos explains some of what I've seen by reading so the features and code bases in mkdocs solutions such as mkdocs-monorepo-plugin or mkdocs-multirepo compared to sphinx-collections.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What are pros of
sphinx-collections
compared to any of the current mkdocs monorepo plugins?Mostly trying to brainstorm and assess the pros of sphinx-collections versus mkdocs-monorepo-plugin or mkdocs-multirepo.
Quoting @danwos :
I think the above quote by @danwos explains some of what I've seen by reading so the features and code bases in mkdocs solutions such as mkdocs-monorepo-plugin or mkdocs-multirepo compared to sphinx-collections.
Beta Was this translation helpful? Give feedback.
All reactions