Routing

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

    </div>
    <div class="col-xs-3">
    	<span class="dot big icon-Download">
    		<span class="line v-line"></span>
    		<span class="line h-line"></span>
    	</span>
    </div>
    <div class="col-xs-9">
    	<div class="row explain">
    		<div class="col-xs-12">
    			<h4 class="text-right">User Request</h4>
    			<small>A front-end request is made...</small>
    		</div>
    	</div>
    </div>
    
    <div class="col-xs-9">
    	<div class="row explain">
    		<div class="col-xs-12">
    			<h4 class="text-right">Request Pipeline</h4>
    		</div>
    		<div class="col-sm-6">
    			<h5><a href="Inbound-Pipeline/">Inbound request pipeline</a></h5>
    			<small>Matching a URL to a content item & determining the rendering engine (MVC or Webforms)</small>
    		</div>
    		<div class="col-sm-6">
    			<h5><a href="Controller-Selection/">Controller selection</a></h5>
    			<small>Match an MVC Controller and Action to handle the request</small>
    		</div>
    	</div>
    </div>
    

    Execute request

    The MVC Action and View are executed. During this execution you can query for published data to be displayed/rendered.
    IPublishedContent
    IPublishedContent is the underlying model used in all Umbraco views
    DynamicPublishedContent
    The dynamic version of IPublishedContent that can be used in all Umbraco views
    UmbracoHelper
    Use UmbracoHelper to query published media and content
    Members
    This section covers the MembershipHelper

    Content is delivered