The solution proposed by Jürgen can be used to upgrade Simple_Blog to version 3.5 and can be uploaded to the Typesetter site so it can be used by everyone.
[…] but i must say that the arrows of the details - summary - version make a better impression. This should be done - evtl. colored arrows - before publishing a new version [...]
When making plugins that deal with dynamically created content, one of the harder decisions always is, how much default front-end style and user experience behavior it should come with.
I personally prefer as-lean-as-possible solutions that …
A) can still be easily overruled via custom CSS and
When it comes to SimpleBlog, there are a few things in the markup that should be improved for better styling possibilities and DOM manipulation.
The problem is, SimpleBlog is very popular and any changes in the html output will cause issues with existing and custom styled installations, when the plugin gets the update.
That's why I always use customized versions, adapted for the current use case.
IMO SImpleBlog should in fact become part of Typesetter core. This would allow much better (Bootstrap) integration and interoperability with other plugins.
But that's nothing done in a few hours, at least not for me.
Edited: 9 months ago