I have followed this nice tutorial which explains how you can take even more advantage of using Umbraco as a content delivery system. Tutorial MVC Umbraco => Your model and views should not depend on specific Umbraco implementations which is a huge advantage for real front-end developers.

Controller:

 public class FrontPageController : MasterDocTypeController
{
    public ActionResult FrontPage(RenderModel renderModel)
    {   
        FrontPageModel blobsList = renderModel.Content.Map();
        blobsList.FillBlobList(storageContainer.ListBlobs(useFlatBlobListing: true));

        return View(blobsList);
    }}

View:

Model:

 public class FrontPageModel:MasterModel
{
    public string Title { get; set; }
    public IHtmlString BodyText { get; set; }
    public string Answer { get; set; }
    public List<CloudFile> Files { get; set; }

    //CONSTRUCTOR
    public FrontPageModel()
        : this(null)
    {
        Files = new List<CloudFile>();
    }

    public FrontPageModel(IEnumerable<IListBlobItem> list)
    {
        FillList(list);
    }

    //METHODS
    public void FillBlobList(IEnumerable<IListBlobItem> list)
    {
        FillList(list);
    }
}

As you can see, most of the things are the same as in tutorial.

When playing around, i faced an issue with the Actionlink in my view.

<a href="">Upload Another File</a>

The link doesn't work because the HREF value has not been populated. This link should redirect the page to the same Controller (FrontPage). It seems this is causing the problem, because it is working when redirecting to a "surfacecontroller" instead of "renderMVCcontroller".

I feel that redirecting to other controller is breaking the normal MVC Structure. Is it right to say that one can not redirect to other pages when action is defined inside "rendermvccontroller"? How would you resolve this issue?