the only way this will be False is if the menu template has been added to PAGE_MENU_TEMPLATES , and then not selected for a page in the admin interface. Sometimes you might need to use regular Django applications within your site, that fall outside of Mezzanine's page structure. Mezzanine fully supports using regular Django applications. All you need to do is add the app's urlpatterns to your project's urls.py module. Mezzanine's blog application for example, does not use Page content types, and is just a regular Django app. Mezzanine provides some helpers for your Django apps to integrate more closely with Mezzanine. The abstract model mezzanine.core.models.Displayable and associated manager mezzanine.core.managers.PublishedManager provide common features for items that can be displayed on the site with their own URLs (also known as slugs). Mezzanine's Page model subclasses it. Some of its features are: Models that do not inherit from the Page model described earlier should subclass the Displayable model if any of the above features are required. An example of this can be found in the mezzanine.blog application, where BlogPost instances contain their own URLs and views that fall outside of the regular URL/view structure of the Page model. A common requirement when using regular Django apps with Mezzanine is for pages in the site's navigation to point to the urlpatterns for the app. Implementing this simply requires creating a page with a URL used by the application. The template rendered by the application's view will have a page variable in its context,