Micro.blog launched with 6 unique themes, and advanced CSS support to customize many aspects of the design. I love seeing users take one of the existing themes and make it their own, such as what Dan Counsell has done with colors and fonts on his site.
The publishing engine for Micro.blog is based on Jekyll, so of course the themes are Jekyll themes as well. I wrote last year about why I chose Jekyll. I’ve forked several themes to improve their support for microblogs, JSON Feed, and IndieWeb standards.
A few of these changes are now up on GitHub. You can find these themes in the @microdotblog repository:
I’ll be updating the other themes on GitHub soon. While you can’t upload an entirely new theme to your Micro.blog account yet, many people have asked for that, and hopefully these themes will provide a starting point.
Kirby Turner has a detailed write-up on his workflow for posting from his iPhone. It uses a combination of Editorial, Working Copy, and Jekyll:
The workflows save me time and simplify the publish steps. For instance, Jekyll uses YAML as front matter for each post. There’s no way I want to write this front matter by hand on my iPhone each time. I can use TextExpander, but seeing the front matter can be distracting on my iPhone. So I let Editorial’s workflow work its magic to generate the YAML front matter before handing off the document to Working Copy.
Check out his embedded video for what it looks like in action. I love Jekyll, and it’s a big part of Micro.blog, but there’s no denying that the nature of static sites makes mobile posting more difficult. Looking forward to seeing more iPhone workflows like this that make microblogging easier.
If you were to build a weblog publishing system, would you start from scratch or build on an existing tool? There’s a healthy market for WordPress-powered hosting, for example, from WordPress.com itself to WP Engine. People know and trust these tools.
I was faced with this question for my microblogging platform. My requirements were pretty simple:
- The published site needed to be 100% static, so that I could host it anywhere.
- The template system needed to be widely used, so that I could draw on existing themes and provide customization for users later.
Jekyll looked like a great choice. I’m so happy with how well this has worked that I mention Jekyll in the marketing and footer of published sites. It’s a brand that can help give users confidence that this is built on something solid, and that if they need to migrate to self-hosted, there’s a path.
On top of Jekyll, I built a web interface for publishing and deleting posts, changing themes, and I added XML-RPC support so that you can use external blog editors like MarsEdit. Plus there’s a native iPhone app for posting.
All of this enables another feature that I’m very excited about: full mirroring to GitHub Pages. When you publish a microblog site, you can have it upload all the Markdown and HTML to a GitHub repository. This is a great way to export or mirror your content.
I think it’s a good foundation. Publishing is actually a small part of the overall microblog platform I’ve built, but it’s an important one. I can’t wait to share more and keep building features up around Jekyll.
I’m writing a short e-book about everything I’ve learned, and I’ll have news soon about early access to the platform. You should sign up on the announce mailing list before next week.