> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/introduction/essentials.md). # Essentials Aurelia is a modern JavaScript framework that empowers you to build exceptional web applications with clean, maintainable code. If you're familiar with HTML, CSS, and modern JavaScript/TypeScript, this essentials guide will introduce you to Aurelia's core concepts and get you productive quickly. This section provides a practical overview of Aurelia's fundamental building blocks. Each concept links to comprehensive documentation where you can dive deeper, but these essentials give you everything needed to start building with confidence. ## What Makes Aurelia Different Aurelia stands out by embracing web standards and keeping things simple: * **Standards-based**: Built on modern web standards without unnecessary abstractions * **Convention over configuration**: Intuitive patterns that reduce boilerplate * **Powerful templating**: Rich binding system with excellent performance * **Dependency injection**: Clean, testable architecture out of the box ## Core Concepts ### [Components](/introduction/essentials/components.md) Components are the building blocks of your Aurelia application. Learn how to create reusable UI elements with clean separation between view and view-model logic. ### [Templates](/introduction/essentials/templates.md) Aurelia's templating system provides powerful data binding, event handling, and conditional rendering with a syntax that feels natural and expressive. ### [Dependency Injection](/introduction/essentials/dependency-injection.md) Aurelia's dependency injection system promotes clean architecture by managing your application's services and their dependencies automatically. ### [Reactivity](/introduction/essentials/reactivity.md) Understand how Aurelia's observation system automatically tracks changes and updates your UI efficiently without virtual DOM overhead. ## Next Steps Ready to build something? Try our [Quick Start Guide](/getting-started/quick-start-guide.md) to create your first Aurelia application. For comprehensive coverage of all features, explore the full documentation sections on [Templates](/templates/overview.md), [Components](/components/components.md), and [Getting to Know Aurelia](https://github.com/aurelia/aurelia/blob/master/docs/user-docs/getting-to-know-aurelia/introduction/README.md). The [Tutorials](https://github.com/aurelia/aurelia/blob/master/docs/user-docs/tutorials/README.md) section contains step-by-step guides for building real applications, while [Developer Guides](https://github.com/aurelia/aurelia/blob/master/docs/user-docs/developer-guides/README.md) covers advanced topics and best practices. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.aurelia.io/introduction/essentials.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.