We currently use a single page to display threads or forums; they are dynamic. Since all the "logic" is contained in a paragraph, the page currently can't have relevant breadcrumbs. Example: current breadcrumbs are
Magnolia Community Forums > Thread list > Thread, and the page title is something along the lines of Magnolia Community Forums - Thread, which is really not that useful. It should be something along the lines of
Magnolia Community Forums > Help > How to do this or that and Magnolia Community Forums - How to do this or that, respectively. *

Other dynamic pages such as "events" have the same problem.

One way of doing this would be:

1. customize the page template to override the breadcrumbs and page title etc. Breadcrumbs should be a breeze, since they're a well extracted "include" in the stk templates. Page title might involve more copy and paste.
2. and/or : all such page-level "meta" information should be provided via the page model. This would allow simply overriding the page model to provide the forum-specifics for these page (i.e override getBreadCrumbsProvider() and getPageTitle() methods, for instance)

As far as the forum is concerned, this shouldn't cause much of a performance overhead, since we retrieve the content by uuid, and we assume the repository provided will keep that node warmly in its cache. It might not be that simple for other use cases, so I'm not sure how much this can be generalized. Option #2 is still probably a valid approach to be moved to STK anyway.

* (and yes, those breadcrumbs are there on forum.magnolia-cms.com, only because we've hacked them in the paragraph template)