Thanks for your interest in contributing! This is an Alpha-stage project — feedback and bug reports are especially valuable right now.
There is no automated test suite. Validate changes by running the setup flow end-to-end:
# From the repo root
chmod +x setup.sh
./setup.shA successful run creates drupal-backend/ and astro-frontend/. Then verify:
# Confirm Drupal JSON:API responds
cd drupal-backend && ddev start
# Visit http://<project>.ddev.site/jsonapi in your browser
# Confirm Astro builds successfully
cd ../astro-frontend && npm run build
# Check that dist/ is generated with HTML filesThe audit toolkit provides structured, non-mutating checks:
cd audit && npm install && npm run audit:all- Setup flow changes belong in
setup/ui.jsandsetup/cli.js - Astro template changes belong in
templates/astro-src/(not in the generatedastro-frontend/) - Script changes belong in
scripts/ - Documentation changes belong in
docs/orREADME.md
Never edit drupal-backend/ or astro-frontend/ directly — these are generated by ./setup.sh and are gitignored.
.agent/execplans/ — Internal planning documents used by maintainers and AI agents to track feature work and decisions. Not required reading for contributors, but available if you want to understand the project's evolution.
.github/agents/ and .github/prompts/ — Optional AI workflow tools for maintainers. Contributors do not need to use them.
Use the GitHub issue templates:
- Bug report — for failures during setup, build, or deployment
- Setup feedback — for anything confusing, unclear, or that could be improved
Issues are the best way to contribute at this stage. Every report helps.
By contributing, you agree that your contributions will be licensed under the MIT License (for tooling/templates) or GPL-2.0-or-later (for Drupal recipe packages), as appropriate for the component you are modifying. See LICENSE for details.