mirror of
https://github.com/mleem97/gregWiki.git
synced 2026-04-11 03:29:19 +02:00
e2839584f4
- Move markdown and wiki-import tree into docs/; keep app shell at repo root - Point docusaurus docs path to docs/; edit links to mleem97/gregWiki - Sync and i18n scripts use gregWiki root and ../.wiki under gregFramework - Sidebars: workspace layout from root docs ids; plugins under mods/extensions - Fix redirects, module catalog URLs, release note paths, and wiki-import category keys - Update repo inventory for split repos; Dockerfile for single-repo context Made-with: Cursor
958 B
958 B
id, title, slug
| id | title | slug |
|---|---|---|
| docusaurus-workflow | Docusaurus Contributor Workflow | /contributors/docusaurus-workflow |
Local workflow
Markdown and MDX live in the repo-root docs/ folder. The Docusaurus app is in wiki/.
cd wiki
npm install
npm run start
Build workflow
cd wiki
npm run build
npm run serve
Can we hide Docusaurus build stuff from non-contributors?
Short answer for a public repo: not fully.
What you can do:
- Keep generated output (
build/,.docusaurus/,node_modules/) out of Git using.gitignore. - Put docs tooling under
wiki/so core runtime contributors can ignore it; content stays indocs/. - Use path-based CODEOWNERS to limit review noise.
- Trigger docs CI on
docs/**andwiki/**changes.
What you cannot do in a public repo:
- Fully hide tracked source files from non-contributors.
If you need true visibility restriction, use a private repo/submodule for docs infra.