Maintenance
This section is for people who maintain Vortex itself: the template, the installer, the tooling package, the documentation, and the releases. Its pages explain how each part works and how to change, test, and publish it. If you're building a site from Vortex, the rest of the documentation, starting from the Introduction, is where you want to be.
The maintenance tooling lives in .vortex/, a directory the installer
leaves out of every consumer site. The ahoy commands on these pages come
from .vortex/.ahoy.yml, so run them from .vortex/, or from the
repository root with ahoy --file .vortex/.ahoy.yml <command>.
The following table lists the maintenance pages:
| Topic | Description |
|---|---|
| Template | Writing the template's shell scripts and testing the template |
| Installer | How the template installer works and how its snapshot tests run |
| Tooling | Maintaining the drevops/vortex-tooling scripts package |
| Documentation | Writing, checking, and publishing the Vortex documentation |
| Release | The versioning strategy and the release process |
The .vortex/skills/ directory holds AI agent skills for the same work.
Claude Code loads them as the vortex plugin, which the repository's
.claude/settings.json enables. The directory holds 5 skills:
prepare-vortex-release- runs the operations of the release checklist and drafts the release notescreate-vortex-tooling-release-notes- drafts the release notes for adrevops/vortex-toolingtagpropagate-vortex-main-to-2x- forward-ports commits frommainto the2.xbranchupdate-vortex-ci-runner- tests a canary build ofdrevops/ci-runner, then pins its released versionupdate-vortex-dev-deps- refreshes the Composer and Yarn development dependencies of.vortex/docs,.vortex/installer, and.vortex/tests