Best Practice for Small Shared Content or Components?

When designing Kentico websites, I frequently encounter situations where I need to have different templates on a page, but have the pages share a common header or other content which can't be done through normal hierarchy / inheritance means.

Does anyone have any best practices for this? I'm sure there's a dozen ways to do it, but say, for example, you had a common header element that needed to be on multiple areas of the site that contained a macro to pull the correct title (and maybe a brief description).

• Where would you store this common content? A custom page type? A custom table? Somewhere else?
• How do you render it on a page? All of the "viewer" web parts seem overkill as they all expect a list of content items, not just a single item. All I want is to be able to point Kentico at a page in the tree and either say "Render this field" (the field would contain HTML/K#), or "Render the editable contents of this page" (by editable text control ID perhaps?).
• Is there a solution that can be achieved with out-of-the-box Kentico (no custom controls or code)? I'm open to writing a reusable web part if it means never having to worry about this again, but I don't want to write a custom control for each bit of content I want to re-use.

I understand that since we're using the portal engine, we're a bit limited, but basically what I'm looking for is an ASP MVC Partial View (but with Kentico Macro support, obviously) - essentially a small bit of content that is parsed and displayed on the page wherever I'd like.

Anyone have any tips for working with content like this?