Maintainer Overview

This section is for llamadart maintainers, not general Docusaurus usage.

Repository ownership map#

• llamadart (this repo): Dart API surface, hooks integration, docs/tests.
• llamadart-native: native build graph, runtime bundle matrix, release assets.
• llama-web-bridge: web bridge runtime source/build behavior.
• llama-web-bridge-assets: published bridge artifacts consumed by this repo.

Local maintainer workspace convention#

Many maintainers keep sibling checkouts one level above this repo:

../llamadart
../llamadart-native
../llama-web-bridge
../llama-web-bridge-assets

Verify these paths before running cross-repo workflows.

Core maintainer responsibilities in this repo#

1. Keep public Dart APIs stable and documented.
2. Keep runtime wiring aligned with native/web owning repos.
3. Keep docs, migration notes, and examples aligned to actual behavior.
4. Keep CI green on format, analyze, tests, and docs checks.

Daily verification commands#

From repo root:

dart format --output=none --set-exit-if-changed .
dart analyze
dart test
./tool/docs/build_site.sh
./tool/docs/validate_links.sh

Use targeted test commands when iterating quickly, then run full checks before release-related merges.

Analytics and SEO maintenance#

• Global GA4 tracking is configured in website/docusaurus.config.ts and reads DOCS_GA_MEASUREMENT_ID from the docs deployment workflow.
• Update the GitHub Actions repository variable DOCS_GA_MEASUREMENT_ID when rotating the docs site's GA4 stream.
• Keep website/static/robots.txt, sitemap generation, and the social card in sync with the production domain https://llamadart.leehack.com.
• Latest stable user-facing docs stay indexable, /docs/next plus archived versions are noIndex, and maintainer pages remain reachable but unlisted.