All things being considered here, I would suggest that you employ something like HTML::FormFu to let you quickly generate a simple CRUD (Create/Read/Update/Delete) functionality for a simple table of “included text.”   Provide such niceities as a start/end date, an active/inactive flag, and so on, as well as a text-box into which text can be entered using some familiar markup system, e.g. [b]...[/b] to represent Boldface and so-on.   “Just like a blog would do it.”   Any HTML-tag content would be stripped out, if you consider that to be a relevant issue.   (If you trust ’em ... and you well might then, if they mess up their own bed, they’re the ones who have to lie in it.)

Then, build a template on the server-side which defines how all such items will be displayed.   The front-page code (or what have you...) SELECTs the content in question, and displays it, using the template.   (If you are using Template::Toolkit, you can simply use a stock “filter” to sanitize the content.)   In this way, you are maintaining full control over how the text will be presented.   (You can, if you like, offer a drop-down list of template choices that they can choose from.)