Hi Hundebol

Essentially each 'stacked item' in your stacked content implementation is represented by an IPublishedContent object. Which means you can work with each item, in the same way that you would with a published page in Umbraco.

So if you have a StackedContent property called say 'StackedItems' you could get a reference in your template to each repeated item like so:

var stackedItems = Model.Content.GetPropertyValue<IEnumerable<IPublishedContent>>("stackedItems");

and then loop through this collection of stacked items to build up your page:

@if (stackedItems!=null && stackedItems.Any()){

foreach (var stackedItem in stackedItems){

<li>
//each repeating stackedItem has the same properties as Model.Content would... eg
@stackedItem.Name
//if you have different types of documents stacked, you can read the alias of the current item being written out
@stackedItem.DocumentTypeAlias
//you can read the values from the stacked content item in the same way
@stackedItem.GetPropertyValue<string>("title")

</li>
}
}

If I've got quite a few different types of stacked items in my stack, or if I use the same types of content on different stacks across the site, then I'll tend to create a 'partial view' for each type of stacked content item, and call that within the loop, just to neaten things up a bit.

eg

    foreach (var stackedItem in stackedItems){
@Html.Partial("/views/partials/Stacked/type-" + stackedItem.DocumentTypeAlias + ".cshtml", stackedItem);
}

and then in a 'stacked' folder inside view/partial I'd create a partial view following the convention

type-MyContentItemAlias.cshtml

and have an inherits at the top of the partial as

    @inherits UmbracoTemplatePage<IPublishedContent>

<h1>@Model.Content.Name</h1>

This gives one place to update implementation if it's the same and used in different stacks, but also makes it easier to read if you have more than 3 different content types stacked...