Updated documentation structure and fixed typos.

Author: AlexSkrypnyk

.vortex/CLAUDE.md

@@ -804,6 +804,7 @@ Each system:
 - Run spellcheck before committing content changes
 - Test interactive components in both development and production builds
 - Maintain consistent terminology across all documentation
+- **Use sentence case for all headings** - only the first letter is capitalized, except for proper nouns (Vortex, GitHub, Drupal, Docker Compose, CircleCI, etc.) and acronyms (CI/CD, SSH, API, BDD, PHPUnit, etc.)
 
 ### 2. Installer System (.vortex/installer/)
 

.vortex/docs/content/README.mdx

@@ -24,8 +24,8 @@ platforms. Everything is pre-configured and ready to use, so teams can focus on
 building features instead of setting up infrastructure.
 
 By standardizing project structure and tooling, **Vortex** ensures a consistent
-developer experience across every project that uses it. Whether you’re starting
-fresh or joining an existing Vortex-based site, you can get up to speed quickly
+developer experience across every project that uses it. Whether you're starting
+fresh or joining an existing **Vortex**-based site, you can get up to speed quickly
 and start contributing right away.
 
 The template is actively maintained and kept in sync with the latest tools.
@@ -45,25 +45,25 @@ projects over time.
   <li>📖 Project documentation</li>
 </ul>
 
-Refer to [Features](getting-started/features.mdx) and [Architecture](getting-started/architecture.mdx) for more details.
+Refer to [Features](features) and [Architecture](architecture) for more details.
 
 ## 🚀 Quick start
 
 ```bash
 curl -SsL https://www.vortextemplate.com/install > installer.php && php installer.php
 ```
 
-Refer to [Installation](getting-started/installation.mdx) for more details.
+Refer to [Installation](installation) for more details.
 
-## 🛟 Getting Help
+## 🛟 Getting help
 
-Refer to [Support](../support) for more details on how to get help with Vortex.
+Refer to [Support](support) for more details on how to get help with **Vortex**.
 
 ## 🤝 Contributing
 
 Refer to [Contributing](contributing) for more details.
 
 ## ⚖️ License
 
-Vortex is licensed under the [GPL-3.0](https://www.gnu.org/licenses/gpl-3.0.en.html) license. See
+**Vortex** is licensed under the [GPL-3.0](https://www.gnu.org/licenses/gpl-3.0.en.html) license. See
 the [LICENSE](https://github.com/drevops/vortex/blob/develop/LICENSE) file for more details.

…content/getting-started/architecture.mdx .vortex/docs/content/architecture.mdx.vortex/docs/content/getting-started/architecture.mdx renamed to .vortex/docs/content/architecture.mdx .vortex/docs/content/getting-started/architecture.mdx renamed to .vortex/docs/content/architecture.mdx

@@ -7,7 +7,7 @@ This page provides a high-level overview of how the template is structured, how
 its components work together, and how your project benefits from its
 architecture.
 
-## Design Principles
+## Design principles
 
 **Vortex** is guided by principles that prioritize simplicity, visibility, and
 maintainability:
@@ -21,7 +21,7 @@ maintainability:
 - **Explicit logging helps**: Scripts log every major step, so it’s easy to
   follow what’s going on.
 
-## System Components
+## System components
 
 The system is made up of several modular pieces that work together:
 
@@ -41,7 +41,7 @@ You can see how these parts connect in the diagram below:
 <img src="/img/diagram-light.png#gh-light-mode-only" alt="System components"/>
 </picture>
 
-## Local Development Environment
+## Local development environment
 
 Your project includes a containerized local environment using Docker Compose and
 production-grade Lagoon images. This ensures consistency between local, CI, and
@@ -66,9 +66,9 @@ Because provisioning is centralized, it runs exactly in the same way in every
 environment: local, CI, or hosting. This eliminates "works on my machine"
 problems and makes the process predictable for everyone.
 
-➡️ See [Drupal > Provision](../drupal/provision)
+➡️ See [Drupal > Provision](./drupal/provision)
 
-### Module and Theme Scaffolds
+### Module and theme scaffolds
 
 We include examples of a custom module and theme, each fully integrated with
 tests. These show you how to:
@@ -79,10 +79,10 @@ tests. These show you how to:
 
 Use these scaffolds as starting points for your own work.
 
-➡️ See [Drupal > Module Scaffold](../drupal/module-scaffold)
-and [Drupal > Theme Scaffold](../drupal/theme-scaffold)
+➡️ See [Drupal > Module Scaffold](./drupal/module-scaffold)
+and [Drupal > Theme Scaffold](./drupal/theme-scaffold)
 
-### Settings Management
+### Settings management
 
 **Vortex** includes a structured way to manage Drupal settings per environment.
 Here's how it works:
@@ -95,9 +95,9 @@ Here's how it works:
 This structure gives you clarity, avoids config sprawl, and lets you remove a
 module’s settings cleanly when no longer needed.
 
-➡️ See [Drupal > Settings](../drupal/settings)
+➡️ See [Drupal > Settings](./drupal/settings)
 
-## Code Quality and Testing
+## Code quality and testing
 
 **Vortex** ships with pre-configured tools for maintaining code quality:
 
@@ -111,10 +111,10 @@ You’ll also find scaffolds for:
 - **PHPUnit**: Unit and kernel testing
 - **Behat**: Behavior-driven testing with screenshot capture and extra steps
 
-➡️ See [Tools > PHPStan](../tools/phpstan), [Tools > PHPCS](../tools/phpcs),
-[Tools > Behat](../tools/behat), and [Tools > PHPUnit](../tools/phpunit)
+➡️ See [Tools > PHPStan](./tools/phpstan), [Tools > PHPCS](./tools/phpcs),
+[Tools > Behat](./tools/behat), and [Tools > PHPUnit](./tools/phpunit)
 
-## Continuous Integration Workflows
+## Continuous integration workflows
 
 **Vortex** supports GitHub Actions and CircleCI. You choose which one to use in your
 project. The workflows include:
@@ -128,9 +128,9 @@ project. The workflows include:
 Each continuous integration configuration mirrors what happens locally and in hosting to ensure
 uniformity.
 
-➡️ See [Continuous Integration](../continuous-integration)
+➡️ See [Continuous Integration](./continuous-integration)
 
-## Hosting Integrations
+## Hosting integrations
 
 Out of the box, **Vortex** supports Acquia and Lagoon hosting. These integrations:
 
@@ -140,9 +140,9 @@ Out of the box, **Vortex** supports Acquia and Lagoon hosting. These integration
 You can use **Vortex** with other platforms too, but these are first-class
 integrations.
 
-➡️ See [Hosting](../hosting)
+➡️ See [Hosting](./hosting)
 
-## Automated Dependency Updates
+## Automated dependency updates
 
 **Vortex** includes configuration for RenovateBot to automate dependency upgrades:
 
@@ -153,14 +153,25 @@ integrations.
 You can host RenovateBot yourself or use the cloud version, and you can tweak
 the schedule as needed.
 
-➡️ See [Tools > Renovate](../tools/renovate)
+➡️ See [Tools > Renovate](./tools/renovate)
 
-## Documentation & Onboarding
+## Documentation & onboarding
 
 **Vortex** includes centralized documentation (what you’re reading now), as well as
 a scaffold for adding project-specific docs within your own repository.
 
-## Workflow Scripts
+## Complete code lifecycle
+
+<details>
+<summary>Expand to see the complete code lifecycle diagram</summary>
+
+import CodeLifecycle from './workflows/_code-lifecycle.mdx';
+
+<CodeLifecycle />
+
+</details>
+
+## Workflow scripts
 
 A workflow is a sequence of steps to achieve a goal. In **Vortex**, those are
 defined via POSIX-compliant Bash scripts in `scripts/vortex`.
@@ -180,12 +191,12 @@ During initial project setup, `.env` file is updated with project-specific
 values like project name, email etc. Then, environment variables (secrets,
 tokens, etc.) are set in CI or hosting environments.
 
-Refer to the [Workflows](../workflows) section for more details.
+Refer to the [Workflows](./workflows) section for more details.
 
 ### Router scripts
 
-Most ****Vortex**** commands are implemented as router scripts entry points like
-`download-db.sh` or `deploy.sh—that` dynamically invoke a more specific logic
+Most **Vortex** commands are implemented as router scripts entry points like
+`download-db.sh` or `deploy.sh` that dynamically invoke a more specific logic
 for your setup, based on configuration or environment variables.
 
 For example:
@@ -207,4 +218,4 @@ For example:
 
 </details>
 
-➡️ See [Workflows](../workflows)
+➡️ See [Workflows](./workflows)

.vortex/docs/content/continuous-integration/README.mdx

@@ -5,9 +5,9 @@ sidebar_position: 1
 
 # Continuous Integration
 
-**Vortex** offers continuous integration configurations for GitHub Actions and
-CircleCI providers that allows to automate the process of building, testing, and
-deploying your site.
+**Vortex** offers continuous integration configurations for [GitHub Actions](/docs/continuous-integration/github-actions)
+and [CircleCI](/docs/continuous-integration/circleci) providers that allow you to
+automate the process of building, testing, and deploying your site.
 
 The workflow configuration is identical for both continuous integration
 providers. You would need to choose one of them and follow the setup
@@ -16,7 +16,7 @@ instructions.
 The continuous integration pipeline consists of multiple jobs executed in a
 containerized environment to ensure consistency across runs.
 
-## Trigger Conditions
+## Trigger conditions
 
 The continuous integration pipeline is triggered by:
 
@@ -31,7 +31,16 @@ The continuous integration pipeline is triggered by:
 - **Pull requests** to these branches
 - **Scheduled runs** for automatic database caching
 
-## Workflow Structure
+## Workflow structure
+
+<details>
+<summary>Expand to see the complete code lifecycle diagram</summary>
+
+import CodeLifecycle from '../workflows/_code-lifecycle.mdx';
+
+<CodeLifecycle />
+
+</details>
 
 ### 1. Database
 
@@ -43,6 +52,8 @@ The continuous integration pipeline is triggered by:
 
 - Runs after the `database` job
 - Uses Docker Compose to set up the environment
+- Validates Composer lock and audits dependencies
+- Assembles the codebase by installing dependencies
 - Provisions a website
 - Lints code (only on the first instance)
 - Runs unit tests
@@ -57,7 +68,7 @@ The continuous integration pipeline is triggered by:
 - Adds required secrets and environment variables
 - Triggers a deployment using a router script
 
-## Caching Strategy
+## Caching strategy
 
 Database is downloaded overnight and cached so that the next continuous integration run on the same
 day uses the cached database dump.

.vortex/docs/content/continuous-integration/circleci.mdx

@@ -0,0 +1,8 @@
+# CircleCI
+
+:::note Content coming soon
+
+  This section will provide detailed information about using **Vortex** with
+  the [CircleCI](https://circleci.com/) continuous integration platform.
+
+:::

.vortex/docs/content/continuous-integration/github-actions.mdx

@@ -0,0 +1,8 @@
+# GitHub Actions
+
+:::note Content coming soon
+
+  This section will provide detailed information about using **Vortex** with
+  the [GitHub Actions](https://github.com/features/actions) continuous integration platform.
+
+:::

.vortex/docs/content/contributing/maintenance/documentation.mdx

@@ -21,7 +21,7 @@ cd .vortex/docs
 ahoy build
 ```
 
-Parts of the documentation is generated automatically from the codebase.
+Parts of the documentation are generated automatically from the codebase.
 To update it, run:
 
 ```bash

.vortex/docs/content/contributing/maintenance/release.mdx

@@ -1,6 +1,6 @@
 # Release
 
-Follow the steps below to release a new version of the Vortex:
+Follow the steps below to release a new version of **Vortex**:
 
 1. Run renovate bot locally to update all dependencies outside of the schedule:
 ```
@@ -13,6 +13,6 @@ renovate --schedule= --force-cli=true drevops/vortex
 6. Increment minor version of all packages in `composer.json`. Run `composer update -W && composer bump`.
 7. Update minor version of dependencies in theme's `package.json`.
 8. Increment the cache version in `.circleci/config.yml` and `.github/workflows/build-test-deploy.yml`.
-9. Updated documentation with `cd .vortex && ahoy update-docs`.
+9. Update documentation with `cd .vortex && ahoy update-docs`.
 10. Update installer video with `cd .vortex && ahoy update-installer-video`.
 11. Create new release notes using [release template](./release_template.md).