Skip to main content
Version: v1

Documentation

Vortex provides 2 types of documentation:

  1. Vortex template documentation (this site) - generic information on how to perform operations, applicable to all projects built with Vortex. Deployed to https://www.vortextemplate.com/docs/
  2. Per-project documentation - project-specific information on what the project does, distributed in the docs/ directory when Vortex is installed.

Per-project documentation describes what applies to the project (coding standards, testing requirements, release configuration) and references the Vortex documentation for how to perform specific operations.

www.vortextemplate.com​

This documentation provides generic "how-to" guides suitable for any project using the Vortex template. It covers tooling, automation, and operations that are common across all Vortex-based projects.

The source is written in Markdown and located in the .vortex/docs directory. This is removed when you install Vortex for a consumer site.

Local build​

Run the docs commands from the .vortex/ directory:

cd .vortex

# Start the local development server with live reload.
ahoy docs

# Build the production site. The build fails on broken internal links.
ahoy build-docs

Parts of the documentation are generated automatically from the codebase. To update them, run:

cd .vortex
ahoy update-docs

If you have the documentation site running locally, the content changes are available immediately.

Lint, spellcheck, and test​

cd .vortex

# Lint the Markdown, check American English spelling, and check the prose style.
ahoy lint-docs

# Run the Jest component tests and the spellcheck.
ahoy test-docs

If required, add spelling exclusions to the .vortex/docs/cspell.json file.

These commands don't check internal links. The Docusaurus build (ahoy build-docs) checks them and fails on broken internal links.

Lines are limited to 76 characters, and markdownlint enforces the limit. Code blocks, tables, and headings are exempt. Code inside a JSX element such as <TabItem> still counts, so split a long command there with \.

Prose style​

Vale checks the prose of every page against the house style. It enforces product names and their casing, sentence-case headings, contractions, the Oxford comma, inline code formatting, and bold Vortex. It also warns about long sentences and wordy phrases. Errors fail the run and the continuous integration build. Warnings are advisory.

The rules come from 3 places:

  • The Google and write-good style packages. They're pinned by release URL in .vortex/docs/.vale.ini and downloaded by vale sync when you run yarn install.
  • The house style in .vortex/docs/.vale/Vortex/, with 1 small YAML file for each rule. A rule that adjusts a Google rule inherits it with extends and edits its word lists, and .vale.ini switches the original off.
  • The vocabulary in .vortex/docs/.vale/config/vocabularies/Vortex/accept.txt, which lists product names with their exact casing.

To lint a single page while you write:

cd .vortex/docs
yarn lint-prose --glob='content/installation.mdx'

When a rule blocks a correct sentence, fix the rule instead of silencing the alert. Add the product name to the vocabulary, add the proper noun to Headings.yml, or remove the word from the rule's list. tests/unit/vale-rules.test.js runs every rule against a valid and an invalid fixture page, so update the fixtures together with the rule.

Block quotes are skipped because they quote upstream projects verbatim. The generated table in development/variables.mdx is skipped too, while the prose before the table is linted.

Documentation videos​

The 9 terminal demo videos embedded in the docs are regenerated with ahoy update-videos [names] from .vortex/. See Installer > Installer video for the pipeline.

Combined site​

The published site serves 2 majors at once. The VORTEX_CURRENT_MAJOR repository variable (default 1) selects the current major. Its branch is snapshotted as the default version at /docs, and the other major's {N}.x branch content is served at /docs/v{N}.

Each branch writes its content against the bare /docs mount, so an absolute link such as /docs/tools/behat points at the current major. When that content is assembled under /docs/v{N}, those links are re-pointed at the major they were written for, and a link that already names a version is left alone. Write links the way they read on their own branch.

Static assets work the same way. Both majors record their own demo videos and diagrams under the same static/img names, so the other major's static/ is served from /v{N} and its asset references are re-pointed to match. Each version therefore shows its own screenshots and recordings. Reference assets the way they read on their own branch, from the bare /img.

To build and browse the combined site locally:

cd .vortex

# Build both majors into 'docs_combined'. Fails on broken internal links.
ahoy docs-combined

# Serve the result on port 4000. Pass a port to override.
ahoy docs-combined-serve

Everything the build writes stays inside docs_combined, a git-ignored copy of docs that's rebuilt from scratch on every run and safe to delete at any time. The tracked docs directory is only ever read, so ahoy docs and ahoy build-docs keep working on this branch's documentation alone.

Publishing​

Automated continuous integration builds publish this documentation:

Consumer site documentation​

Vortex ships a scaffold of consumer site documentation in the docs directory. It's installed into every consumer site, where the site maintainers keep it up-to-date with their project.

The scaffold covers what applies to each project:

  • Coding standards and agreements specific to the project
  • Testing requirements and configuration
  • Release and deployment configuration
  • Project-specific procedures and decisions

The scaffold references this site for how to perform each operation instead of duplicating instructions. So when you maintain the template, keep the scaffold pointing at the right pages here. Keep the how-to content on this site rather than in the shipped docs/ files.