I have a couple of frustrations with utilizing a php-based blog tool, such as b2evo, to serve our pages:
1) We have keywords for our site and while our site is largely about things that those keywords relate to, I write on enough diverse subjects that the site keywords often are a complete and utter mis-match with the post contents when viewed in a single pane mode.
So ... I would like to see a back-office feature that allows one to add keywords, along with a post entry. IF the post closely matches the site keywords ... one can leave the keyword field blank. But IF the post content differs from the site keywords, one can add "post keywords" that are then served up in the meta keyword tag, when the page is views in single pane mode OR served up with 5/7/$pages other post keywords, when viewed in "posts paged" or some other mode.
This way, the page is more properly formed and there is a better relevancy match between the keywords of the PAGE and the post content.
2) Likewise, there are times when I would like to control the CSS for an individual post. I don't wan to have to burden the client with loading this CSS EVERY time our page loads, only when the page for which the CSS is APPLIED loads.
While I know that I can use inline CSS for many post-specific styling, there are some selectors (a:hover, being one) that does not have an inline equivalent. Also, for posts that contain a CSS technique, it is often beneficial to have the CSS in the <head> tag (or separate, external file) so that a user can view it using 'view source' (or Ffox web developer).
I'm not certain regarding feasiblity, but it would be nice to have the ability to define post-specific CSS.
This would allow users to have one-off CSS files associated with a particular blog entry, without bloating the skin CSS file with (often) non-used selectors and directives.
I do not know how popular either of these enhancement requests might be to others, but both have been niggling at me for some time. (1) Is partly a matter of semantics, but because b2evo is standards compliant, it would seem natural to seek a higher relevancy between page keywords and page content ... that's just good XHTML. (2) Is mostly a matter of personal need, but I believe others would like this capability as well.