> I need to create a series of 'activities' that can be categorised under > Math and Science and further sub-categorised according to the concepts they > teach. > Now I would like to display these categories on the menu. Does that mean > that my 'activity' is essentially a page? When I am defining Activity > model, should it inherit from Displayable or Page? > The docs have a bit about Displayable vs Page[1]. Basically, Page integrates Displayable into the navigation. Your subclass would be available to add from the dropdown of the Pages admin page.
What I would do is use two classes, an ActivityCategory and an Activity class. Activity subclasses Displayable while ActivityCategory subclasses Page. Activities are linked to an ActivityCategory. Then when you create your ActivityCategories, the hierarchy would automatically be accessible through the navigation. The docs also have an example of this[2]. And you may want to see how the blog app is built[3]. You could also do what the blog app does and not use Page at all. But then you would have to manually create a Page with the same URL as each ActivityCategory to get it in the navigation[4]. [1] http://mezzanine.jupo.org/docs/content-architecture.html#displayable-vs-page [2] http://mezzanine.jupo.org/docs/content-architecture.html#creating-custom-content-types [3] https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/blog [4] http://mezzanine.jupo.org/docs/content-architecture.html#third-party-app-integration -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
