(Libre 2 is a refreshed version of the Libre theme, with more features and added flexibility.)
Libre 2 brings a stylish, classic look to your personal blog or site for longform writing. The main navigation bar stays fixed to the top of the screen while your visitors read, keeping your most important content at hand, while three footer widget areas give your secondary content a comfortable home. Customize Libre 2with a logo or a header image to make it your own.
This could be a good pared-down theme to consider.
(Skip to the end for the TL;DR summary)
After an evening of debugging and rewriting sections of the HTML in “K”, I think I’ve fixed the markup and parsing issues I mentioned yesterday.
It turns out that X-Ray, the parsing engine used by IndieNews, Aperture, and probably others, was only findin...
I’m taking the new #Indieweb WordPress by @pfefferle and man, this is really, really nice. I haven’t played with all the options yet but if you want to take the theme for a spin you can get it from GitHub. I’ll write more about it once I’m done putting it through its paces. More Indieweb themes is always better, more accessible themes is even better than that. This one is made of semantic HTML, Microformats, Microformats 2, and schema data. I haven’t explored the templates yet but it has full post kinds and post formats support as well.
After a user of the Storefront WordPress theme, (WooCommerce’s default theme), reported accessibility challenges with the theme’s focus outlines and text decoration with regard to links, the Storefront theme has been modified to address the issue with focus outlines by modifying the default outl...
I’ve been chipping away at several things over the last two weeks, mostly focussing on markup, presentation, and theme file organisation. I want to get these finalised before I look at theme customisation options. If you’ve visited the home page, you might have noticed the display of certain pos...
New IndieWeb friendly themes for WordPress are always a welcome thing. I hope he’s open-sourcing it for others to tinker with as well.
Over the last months, one of the regular problems mentioned with the Indieweb on WordPress is the lack of compatible themes. Most themes do not properly mark up their content in microformats, or support some of the customizations that would integrate with Indieweb plugins.
I had already been working...
I’ve written about my forays into the IndieWeb movement before. I have even written about how I feel like I’m moving to a philosophy of sharing my work that is kind of old school. Last week, I had the occasion to see a perfect example of how the “new” ways that I’m working are actually the old ways.
Kudos Cathie for rolling up your sleeves and delving in like this! You’re getting some fairly solid results and have far stronger grasp of what is going on than I certainly did in my first year–not to say that I’m much better off now to be honest.
The tougher part is that some of your post seems a bit misleading to me.
The couple of microformats related lines you’re adding in your child theme like add_theme_support( ‘microformats2’ ); are in fact declaring that your theme properly supports microformats v1, v2, and microdata which it doesn’t quite. Those lines don’t actually add support (as the hook might indicate), but tell other WordPress plugins that your theme is microformats compatible which may prevent them from adding particular pieces of redundant microformats related code.
While you’ve got an h-entry in your header file, you’re closing the related </div> just after the title so that if the body of your post includes a p-summary or an e-content microformat, parsers are likely to have problems. Instead you might want to do something similar in either your content.php (or other file that adds the body of your post) or your footer.php files where you close that div in one of those two files instead of in your header.php file. If you need it the article page on the wiki has a simple example of what the final result should look like.
My favorite template for how to add microformats to a WordPress theme is David Shanske’s fork of the TwentySixteen theme. Because of GitHub’s interface and the fact that he made changes in relatively small increments, you can look at the history of his changes (start with the oldest ones and move forward) and see the highlights of what he added and removed in individual files to effect the necessary changes. (He made some other drastic changes like removing Post Formats in preference to Post Kinds as well as some other non-microformats changes, so you’ll necessarily want to skip those particular changes.) I think I learned more about WordPress Themes by going through this one example a change at a time than any of the books or tutorials I’ve ever seen.
Another tool in addition to indiewebify.me is the Pin13 parser which will parse your page and give you some indication about what it is finding (or not) and how things are being nested (or not).
If you need some help, feel free to catch one of the WordPress folks in the IndieWeb chat. I suspect that since you’ve got the fortitude to dive into the code the way you have, that you’ll be able to puzzle it out.
Lately I found myself posting a lot about IndieWeb, and thinking about how useful it could be for the next versions of the Log Lolla theme.
I ran across this article today as the result of a refback of all things (hooray for old web infrastructure!). The site had reposted a few IndieWeb related articles I wrote in the past year.
Since they don’t support webmention and don’t seem to have comments on their site open, I’ll say “Hello!” by syndicating to Twitter. I hope you haven’t given up on the idea of what the IndieWeb stands for and are still thinking of making your Log Lolla theme directly compatible with how the IndieWeb works with WordPress. There are a bunch of us out here who’d love to give you any help and support you need as we’d all love to see more IndieWeb friendly themes in the WordPress repo. Feel free to join us in the #IndieWeb chat or the #WordPress chat to say hello.
As a first step to better understand the different layers of adding microformats to my site (what is currently done by the theme, what by plugins etc.), I decided to start with: what is supposed to go where?
I made a post-it map on my wall to create an overview for myself. The map corresponds to the front page of my blog.
Green is content, pink is h- elements, blue u- elements, and yellow p- elements, with the little square ones covering dt- and rel’s. All this is based on the information provided on the http://microformats.org/wiki/Main_Page, and not on what my site actually does. So next step is a comparison of what I expect to be there from this map, to what is actually there. This map is also a useful step to see how to add microformats to the u-design theme for myself.
Earlier this week I discussed microformats with Elmine. Microformats make your website machine readable, allowing other computers and applications to e.g. find out where my contact information is, and the metadata from my postings.
It was a discussion that branched off a conversation on online repre...
All my themes and plugins are now free. At the moment I feel that’s a permanent decision but you’ll never know.
I want to thank all who have supported my journey. Either by purchasing, helping, or sharing ideas. I’ll do my best to answer some of the questions you might have. Why free?