Files
angular__angular/adev
Kam 93f17e0bdf docs: fix the docregion marker in the apache config example
The marker was written `# docregion`, but the hash matcher expects
`# #docregion`, one hash for the comment and one for the marker. It was not
recognised, so it was never stripped and rendered as the first line of the
Apache config on https://angular.dev/guide/i18n/deploy.

The sibling `nginx.conf`, shown on the same page, already has the correct form.
2026-09-09 16:18:39 +02:00
..
2026-06-03 17:54:49 +02:00
2025-11-19 08:10:09 -08:00

Angular.dev

This site is built with Angular.

The content is written primarily in Markdown format located in src/content. For simple edits, you can directly edit the file on GitHub and generate a Pull Request.

Local Development

For local development, pnpm is the preferred package manager. You can set up a local environment with the following commands :

# Clone Angular repo
git clone https://github.com/angular/angular.git

# Navigate to project directory
cd angular

# Install dependencies
pnpm install

# Build and run local dev server
# NOTE: Initial build will take some time
pnpm adev

If you are having issues with the docs building, see the FAQs section.

Contributing

Want to report a bug, contribute some code, or improve the documentation? Excellent!

Read through our contributing guidelines to learn about our submission process, coding rules, and more.

And if you're new, check out one of our issues labeled as help wanted or good first issue.

Code of Conduct

Help us keep Angular open and inclusive. Please read and follow our Code of Conduct.

FAQs

The build is failing and I'm seeing bazel:bazel failed: missing input file messages.

This is most likely due to a bazel dependency / caching issue. To resolve this, run the following command:

# Try this first
pnpm bazel clean

# If that doesn't work, try it with the expunge flag
pnpm bazel clean --expunge

High level architecture

The angular.dev website is a modern Angular application that utilizes Static Site Generation (SSG) to deliver pre-rendered, high-performance content to users.

The architecture is designed for efficiency and maintainability:

Content Sources: The documentation is sourced from two main places within the monorepo. The guides and tutorials are written in Markdown files, while the API reference pages are automatically generated by extracting documentation directly from the TypeScript source code of the Angular framework packages.

Build Process: During the build process, the Markdown files are converted into HTML. Simultaneously, the API documentation is extracted from the code comments. This content is then integrated into the Angular application.