-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rearchitect documentation generator from markdown #1429
Comments
relates to - #1278 |
also - defenseunicorns/UnicornUI#86 |
We can also add DocsGPT support by training the model for Zarf , it can give better understanding to the users and also handle most of the queries . |
Summarizing this thread (https://kubernetes.slack.com/archives/C03BP9Z3CMA/p1678915928812279): I think this is a good place to build off from for an ADR I know @mike-winberry is working this: defenseunicorns/UnicornUI#86 to see if docs can just be inside of Zarf and there are other options we should explore (including Kiwix which we experimented with a while back: https://github.com/defenseunicorns/zarf/tree/example/kiwix) in addition to the more traditional md to docs generators. The biggest thing will be offline support most likely since our primary deploy persona (Ashton) is usually less tech savvy, and won't always have internet access. |
## Description Port docs to Starlight, restructure to delineate differences between reference material and guides. Greatly consolidates information in miscellaneous `.md` files across the repo to live within `site/src/content/docs`. Lays a pathway for future docs work, and hopefully no more large docs PRs. ## Related Issue Fixes #1429 Fixes #1460 Fixes #1532 Fixes #1134 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Other (security config, docs update, etc) ## Checklist before merging - [x] Test, docs, adr added or updated as needed - [x] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed --------- Signed-off-by: razzle <harry@razzle.cloud> Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com> Co-authored-by: Lucas Rodriguez <lucas.rodriguez9616@gmail.com>
Describe what should be investigated or refactored
We have had issues with Docusaurus and would like to explore other options for hosting a documentation site. This should explore:
This should not lose the following:
This will also need an ADR comparing different options and explaining why we went a particular direction.
Links to any relevant code
https://github.com/defenseunicorns/zarf/tree/main/docs-website
Additional context
This comes out of us looking at our docs and thinking about how we could incorporate them into Zarf to bring it along to the airgap.
The text was updated successfully, but these errors were encountered: