Hi Carole,

Sorry I've gotten a little behind on documenting that due to holiday travel. With the Blog I've added new DisplaySettings rather than module settings, partly because I wanted to provide different settings for list view and detail view whereas the  Html Content feature only has one view and is more likely to need different settings per instance.

I've just updated the article Blog Display Settings with notes about the new options. I've also added an example snippet of CSS for the author bio in the Important Skin Changes article.

Hope that helps,

Joe

I know some of it is a bit inconsistent, but I'm trying to keep from adding more and more settings to the UI, the blog has a daunting number of them already. Also by making more settings themeable we can disable them for example in the mobile skin which we can't do if its a module setting unless we make it possible to override it somehow from the theme.skin. So on a case by case basis it may seem inconsistent but generally there is a method to the madness. Avatars can be disabled from theme.skin by themeable settings on the Avatar control itself but author bio isn't a control with separate themeable properties so it made more sense to be in BlogDisplaySettings. 

Best,

Joe

I think I probably should have made those Author Bio settings true by default. I will do that for the next release and update mobile skin pro to make them false there.

Best,

Joe

ok, after more thought, I will add a module setting in the blog for author bio in the next release and just let it be an override in theme.skin so it can be disabled in a mobile skin but discovered and enabled from the UI.

Best,

Joe

I've been thinking about this some more and realized what was really bothering me about adding the author bio as a module setting in the blog. It makes sense in the html content feature because it is just one article, but what is bothering me about the blog is that we have more and more settings at the module instance level that really should be at the post level so they can be set per post. I've had to do item for a long time for example to make the map settings per post, so any given post can have the map configured any way that makes sense for the post itself instead of having to make them all use the same settings in every post.

So my plan now is to try to get to these things that really should be configurable per post. I will probably also add a module setting for "Show Author Bio" but it will really be just a default so that the corresponding checkbox for Show Author Bio in the post edit page would be pre-checked on new posts if true in the module setting but it could be unchecked on any given post. I'm going to review each of the blog module settings and consider whether to remove them after making the post level settings or whether it makes sense to keep them for default purposes.

Best,

Joe