All of the official Micro.blog themes have now been updated with Microformats fixes and other missing markup. Also improves Cactus, an older neglected theme that fell over in the transition to Hugo 0.91. There are now over 30 themes in the plug-in directory. 🎉

@gr36 @news I second the petition. It’d be great to know what changed, because some of these formatting changes might be already in my custom theme.

@news Thanks, @sod

@news Does this mean I have to update my current theme?

@gr36 @iPabloSB The changelog (commit history) is available for each theme over at GitHub. Here's Cactus, for example. I've run a test suite on each theme that checks for:

• Microformat presence
• Plug-in JavaScript, CSS, and HTML include compatibility
• Custom CSS and Footer support
• Conversation.js inclusion
• RSD and Webmention presence

For now, the test suite mostly runs on my machine and is not designed to be easy to use. But we might pack it up and release it for third-party theme developers to test their own themes. Of course, nothing is stopping you from doing that now, if you feel adventurous. 😊 But it's not officially released yet and unsupported for now.

@alexink You don't have to, but you can if you want. 😊

@news Wow! Cool. I have found one that I’m going to try and modify a little.

@sod thanks for clarification 👌

@sod @news Thanks for all your hard work on this. I still recall when there were only a handful of themes in the directory — which itself didn’t exist at the time. Exciting to see how much the theming and plugin ecosystem has grown in such a seemingly short time!

@sod This is awesome. I need to figure out how to run it on Tiny. Or at least work out what all you’re checking for specifically and do it manually.

@sod what a great tool! I got it running on my machine without a hitch and even fixed some of the low hanging fruit in my own theme. 👌

@Mtt There are some rudimentary instructions on how to get started on a Mac in the root of the project for theme developers feeling brave. 😊 Tiny passes all but three tests, great work! I've opened a pull request with the necessary changes to get to a 100%.

@kottkrig Yay! 🙌 Thanks for trying it out. Any and all feedback is welcome. One thing I'm still pondering is whether it feels natural to have a test-blog directory in one's theme directory and run the tests from there (the way it works now) or if that's too much hassle? I can see an alternative approach where the test suite is installed like a tool instead that runs from the terminal like micro-blog-test path/to/your/theme (similar to html-validate).

@sod Could you check labarum if you get a chance?

@sod You're the best. I really appreciate it!

@sod Okay, thanks, really appreciate all the hard work going on!