The controlling of xBlog plugins should be easy:
Users control relevant properties by the flexforms
Administrators control properties by the constant editor
The core of xBlog is the bridge.
For example: a list view is publishing usually the elements:
a short (sometimes)
An administrator allocates to each element fields like
subtitle: margin_subtitle // teaser_subtitle // subtitle // my_extension_subtitle
xBlog is looking for a value from a field margin_subtitle and if it is empty, xBlog looks for a value from a field teaser_subtitle, and if it is empty, it takes the next for rendering. And so on.
This concept enables a ready-to-use configuration for most of use cases.