There is - that is one of the quick starts I will work on. It doesn't come up as much in my applications because many enterprise customers treat it as an application, like on the desktop, that is delivered over the Internet, as opposed to a "richer
set of web pages" that make more sense with the navigation paradigm.
It will work, and I will post a quick start, but in essence, you'll do this:
(1) Create a JounceNavigator.xaml view with one ContentControl region (or, if you want to animate between pages, one ItemsControl region).
(2) Map all URIs to the JounceNavigator.xaml
(3) Instead of creating pages, create UserControls.
(4) When JounceNavigator is navigated to, you can inspect the Uri and raise the corresponding control event and it will map into the region.
This was lower on my list of priorities, but I will definitely do it - if others are struggling with this specific paradigm, please reply here and I will bump it on the priority list (next item was going to be the CRUD example with the entity view model).