Make documentation available via/in Backstage #3815
Labels
honeybadger/ui
In Team Honeybadger and dealing with user interfaces
team/honeybadger
Team Honey Badger
topic/documentation
ui/backstage
The next generation web UI for Giant Swarm
User story
This issue is mainly for gathering ideas.
Ideas
TechDocs
Backstage provides the TechDocs function to make some documentation available directly in Backstage. The most common use case for TechDocs is to provide access to docs for a specific software component. The documentation source resides within the component code repository (
docs
folder typically).As of now (Dec 2024) only few Giant Swarm components provide TechDocs (i.e. docs folder in the repo). Should we move more documentation into the repos? What to do with content that resides in docs.giantswarm.io exclusively, should this be duplicated? (technically difficult, as we use Hugo in docs but don't use Hugo in TechDocs).
Linking to docs.giantswarm.io
We can (and should) simply link to documentation at docs.giantswarm.io. We may introduce a special link format / icon for this, or do this in some other particular way so that users recognize the special sort of link.
The most difficult parts here are (1) adding all the relevant links and (2) maintaining them. This requires some sort of process.
APIs
APIs have a special place in Backstage. Our CRD documentation might be covered by APIs at some point. There is a separate issue for that.
The text was updated successfully, but these errors were encountered: