External content repos #1066
lgastler
started this conversation in
Feature Requests
Replies: 1 comment
-
This is more a question if this would be in mind sometime in the future. I am aware that the way the markdown files are fetched having the "locally" / in the same repo at build time etc. is much easier right now, f.e. using Astro's Content-Collections. But was just wondering if that maybe on the timeline in the future. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What version of
starlight
are you using?0.12.0
What is your idea?
Allow the source / content markdown to be in a separate repo than the source code for the docs / starlight page.
Why is this feature necessary?
We have multiple repos with our documentation, which we currently aggregate into a single docs site to be read / consumed. Our own implementation of how the
*.md
files are fetched from the git repos and then displayed is not even close to being as good as the starlight docs. But we do not want to put all different repos together and include all the docs page / starlight source code. This is for multiple reasons, like different access rights, some non-tech people working on those, different responsibilities etc.Do you have examples of this feature in other projects?
No response
Participation
Beta Was this translation helpful? Give feedback.
All reactions