> 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/getting-started/creating-websites-with-umbraco.md).

# Creating websites

This section provides beginner-friendly tools and guidance to get started with Umbraco

In this section, you will find information about which frameworks, languages, and platforms work best with Umbraco to create user-friendly, responsive websites.

Before diving in, it’s helpful to familiarize yourself with some key concepts. This section introduces these concepts and explains how they are used in the Umbraco backoffice.

## How Umbraco Works

Your website’s content is structured using **Document Types**, which define the types of content you can create. Each Document Type is composed of Properties, which utilize **Data Types** to define the type of data that can be entered. Every Data Type relies on a **Property Editor**, which determines how content is edited in the backoffice.

Once content is created using Document Types, it is displayed on your website through **Templates**.

### Key Terminology

There are a lot of terminologies here. Let's look at breaking these terms down:

* [**Document Types**](https://docs.umbraco.com/umbraco-cms/fundamentals/data/defining-content)**:** Define the structure and type of content on your website.
* [**Data Types**](https://docs.umbraco.com/umbraco-cms/fundamentals/data/data-types)**:** Specify the kind of data a Property can store (for example, text, number, date).
* [**Property Editors**](https://docs.umbraco.com/umbraco-cms/13.latest/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors)**:** Control how content is entered and displayed in the backoffice.
* [**Templates**](https://docs.umbraco.com/umbraco-cms/fundamentals/design/templates)**:** Determine how content is rendered on the front end of your website.

## Try it out

* [Creating a basic website Tutorial](/umbraco-cms/13.latest/tutorials/creating-a-basic-website.md): Learn how to create a basic website and start exploring Umbraco CMS hands-on.
* [Video: Create an Umbraco website](https://www.youtube.com/watch?v=_Is_bk2xnKg): Watch a step-by-step guide to creating your first website with Umbraco.

## Other Resources

* [How can translations be used with content?](/umbraco-cms/13.latest/fundamentals/backoffice/variants.md)
* [Customize the Backoffice](https://docs.umbraco.com/umbraco-cms/customizing/overview)
* [Extending Umbraco](https://docs.umbraco.com/umbraco-cms/extending/build-on-umbraco-functionality)


---

# 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/getting-started/creating-websites-with-umbraco.md?ask=<question>&goal=<user_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.