MVC Url Pattern

You're not passing the NodeAliasPath paramater you are creating into anything.

A normal routing is set up something like this:

 routes.MapRoute(
                name: "Default",
                url: "{controller}/{action}/{id}",
                defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
            );

Not sure how your controller is set up but I would imagine you would need to do something like this:

routes.MapRoute(
    name: "Default",
     url: "{ NodeAliasPath }",
    defaults: new { controller = "universal", action = "Index", NodeAliasPath = UrlParameter.Optional }
);

This will pass the entire URL into your controller.

How does your "universal" controller retrieve page content?

I am still testing this out, but i believe you can create a catch-all route at the end (that if nothing else matches, run it) which can then take a look at the current url, do a lookup on the Nodes to grab the matching TreeNode, and based on it's page type/class (which should have a Url pattern in the page type of that class) you can redirect to the proper controller.

I could be wrong, that was my understanding, i am testing that out next once i get the widgets going.

Just to give an update, i have created this exact thing, took a custom RouteHandler to catch a "Control Not Found" and do a lookup on the NodeAliasPath, and then dynamically set what Controller should handle the request. I have the code and will be writing a blog (devtrev.com) about it end of this month, if you want contact me at tfayas@gmail.com and i can get it to you early!

I was looking everywhere for this. This seems like important, fundamental CMS functionality to allow content editors to be able to create arbitrary pages at the root level. Why isn't this covered by the official doc/tutorials?