# Routing

Get an overview of how the Umbraco pipeline is structured. See what happens from user request to content delivery.

## Request Pipeline

### [Inbound request pipeline](/umbraco-cms/implementation/default-routing/inbound-pipeline.md)

Matching a URL to a content item & determining the rendering engine (MVC or Webforms).

### [Controller selection](/umbraco-cms/implementation/default-routing/controller-selection.md)

Match an MVC Controller and Action to handle the request.

## [Execute request](/umbraco-cms/implementation/default-routing/execute-request.md)

The MVC Action and View are executed. During this execution you can query for published data to be displayed/rendered.

### [IPublishedContent](/umbraco-cms/reference/querying/ipublishedcontent.md)

IPublishedContent is a strongly typed underlying model used in all Umbraco views.

### [UmbracoHelper](/umbraco-cms/reference/querying/umbracohelper.md)

Use UmbracoHelper to query published media and content.

### [Members](/umbraco-cms/reference/querying/imembermanager.md)

This section covers the IMemberManager.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.umbraco.com/umbraco-cms/implementation/default-routing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.