I'm confusing myself about how each of these boxes is working and is connected to the navigation, and am tempted to refactor this a bit for the long term.
Possible approach of having subclasses of something like MPInfoBox that has:
Methods
setup(member_obj)
yield_sub_menu_items()
get_context()
properties
template_name
mp_page
page_order
Where a view will then initialise a model with with the MP info, and render the contents in order (so these pages themselves become quite simple, with the complexity more isolated in each MpInfoBox subclass.
The simplest approach is of course to just do mild tweaks, but I think in the long run the flexibility might be nicer. Writing up to come back to later.
I'm confusing myself about how each of these boxes is working and is connected to the navigation, and am tempted to refactor this a bit for the long term.
Possible approach of having subclasses of something like MPInfoBox that has:
Methods
properties
Where a view will then initialise a model with with the MP info, and render the contents in order (so these pages themselves become quite simple, with the complexity more isolated in each MpInfoBox subclass.
The simplest approach is of course to just do mild tweaks, but I think in the long run the flexibility might be nicer. Writing up to come back to later.