> 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/tutorials/editors-manual/getting-started-with-umbraco/editing-existing-content.md).

# Editing Existing Content

## Content Within the Tree View

When you are looking to edit content, locate the ***page*** you want to edit in the section tree on the left-side of the screen.

![Viewing Pages in Content Section](https://3872888104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgEH4FChbCn7eDDqREvdE%2Fuploads%2Fgit-blob-e774152442c19ffedbbf9713f17fdd4cc76cefa4%2FView-page-v9.png?alt=media)

To edit existing content, follow these steps:

1. Go to the **Content** section.
2. Select the page in the section tree you wish to edit. The content of the page is loaded in the right-side editor.
3. Edit the contents of the page.
4. Click **Save** to save the edits without publishing it.
5. Click **Save and preview** to preview the changes.
6. Click **Save and publish** to publish the changes. For more information, see the [Save and Publishing Pages](/umbraco-cms/13.latest/tutorials/editors-manual/getting-started-with-umbraco/creating-saving-and-publishing-content.md#saving-and-publishing-pages) article.

## View Page Layout

You can view Page layouts in three ways:

1. **Tree View**

   The tree view is present in the section tree on the left-side of the screen. For a growing website with multiple content pages, the tree view can become very large and unmanageable.

   ![Tree View](https://3872888104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgEH4FChbCn7eDDqREvdE%2Fuploads%2Fgit-blob-87fdf4a7ff57f5051fe88a3503c5b2c891eb5f8b%2FPick-page-v9.png?alt=media)
2. **List View**

   When you enable listview on a page, there will be no standard tree view for that page. Clicking on the parent page displays the child pages in the list view.

   ![Shows the regular listview.](https://3872888104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgEH4FChbCn7eDDqREvdE%2Fuploads%2Fgit-blob-9fd087275e8f7b3db3847560a9f78c0b12f19cef%2FList-view-v9.png?alt=media)

   To enable list view:

   1. Go to **Settings**.
   2. Navigate to the Document Type/page you wish to enable list view.
   3. Go to the **List View** tab.
   4. Toggle **Enable List view** and click **Save**.

      ![Shows the regular listview.](https://3872888104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgEH4FChbCn7eDDqREvdE%2Fuploads%2Fgit-blob-6f6d1734e4ed420eef09a46452c2582c4a6739fa%2FEnabling-List-View-v9.png?alt=media)

   Additionally, you can sort the column **Name**, **Last edited**, and **Created by** in ascending or descending order to sort the list items.
3. **Tiles View**

   You can switch between list view and tiles view by clicking the view icon in the top-right of the screen:

   ![Tiles View.](https://3872888104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgEH4FChbCn7eDDqREvdE%2Fuploads%2Fgit-blob-768dd9a0a617a527d94e8c671d2d10a197d025f2%2FTiles-View-v9.png?alt=media)


---

# 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/tutorials/editors-manual/getting-started-with-umbraco/editing-existing-content.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.