> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/13.latest/fundamentals/get-to-know-umbraco.md). # Get to know Umbraco All the fundamentals of using Umbraco - from making a local installation to extending the backend. In this part of the Umbraco CMS documentation, you can get to know the product and the default functionality. It is here you start your Umbraco journey with the installation, setup, and basics of working with the CMS.


Setup	Find requirements for both local development and hosting as well as guides for installing and upgrading Umbraco CMS.	Setup	setup-image (1).png
Backoffice	Learn about the different sections found in the Umbraco CMS backoffice and get an overview of the available features.	Backoffice	setup (1).png
Data	Dive a little deeper and learn how to create different types of data directly from the Umbraco CMS backoffice.	Data	data (1).png
Design	Get to know the different options the Umbraco CMS backoffice provides for designing your website.	Design	design (1).png
Code	A high-level overview of working with some of the more advanced elements like services and notifications.	Code	code-image (1).png

--- # 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.umbraco.com/umbraco-cms/13.latest/fundamentals/get-to-know-umbraco.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.