Every day, millions of new web pages are added to the internet. Most of them are unstructured, uncategorized, and nearly impossible for software to understand. It irks me. Look no further than Sir Tim Berners-Lee's Wikipedia page: The markup for Tim Berners-Lee's Wikipedia page; it's complex and inc...
We definitely need more rich mark up that’s parseable and usable. I’m not sure that additional HTML tags would necessarily be taken up heavily to be of much use.
I do like having some solid microformats on my own content and it works out well with many of the parsing tools that I use regularly for consuming content. I’m curious what Dries has tried out in terms of options he’s dogfooded into Drupal? I do notice that when my website parses his article, it does pull in more data than most sites I come across. The one thing my parser didn’t find was his avatar in the “correct” place. It popped up as a page photo rather than an avatar for him as an author.
Putting microformats into Wikipedia seems like an interesting idea. Anyone want to manually add microformats to tbl’s Wikipedia page? 🙂
h-shitpost?! This should parse without any additional work:
<div class="h-entry"> <time class="dt-published">2017-01-20</time>: <p class="p-content">I do solemnly swear that I will faithfully execute the Office of President of the United States, and will to the best of my ability, preserve, protect and defend the Constitution of the United States.</p> <span class="p-author">Donald John Trump</span> <span class="p-category">shitpost</span> </div>
The current microformats include pattern offers two methods — using <object> or <a> — to include in a microformat element parts of a document that are outside of that microformats element's DOM tree. Both patterns have problems, and have not been widely adopted. Also, the include pattern has not been updated for microformats 2. This page is a proposal for a new include pattern using a custom element without any semantics.
It’s a reasonably good example of how web standards are evolved for those who might like to see how the sausage is made (pun intended.)
Dan Cederholm's logo but now adjusted for the microformat dinners. :D
::dan don't hurt me:: :D
Micropub 2.2.3 for WordPress has been released. It fixes a variety of warning notices. Published, updated, name, and summary properties are no longer stored in post meta. When queried, they will be pulled from the equivalent WordPress properties. Content should be as well, however as content in th...
Theme components are bite sized code snippets that can be reused across multiple themes, but are either too small or don’t make sense to be released as a plugin. Stop cluttering up your functions.php file and start using theme components! Who are theme components for? Th...
Let’s get together as a community and host a theme raising (a play on the idea of the old barn raising). We can all work/hack together to make some of the popular WordPress themes more IndieWeb friendly. We’ll discuss methods for adding the necessary Microformats and best ways to indieweb-ify a WordPress theme.
Either bring your own favorite theme or work from one on a list.
All levels are welcome!
Beginners and those without coding experience are welcome/encouraged to attend. We’ll try to help newcomers learn to begin tinkering with some WordPress theme code. If you don’t have a GitHub account yet, you might create one beforehand and we’ll show you how to use it for development, but even without it you can still do a lot with just a text editor.
When: 2020-09-26 9:30 – 11:30 AM (Pacific) / 12:30 – 2:30 PM (Eastern)
hashtag: for social media and used to create an Etherpad for the session: #WPandMicroformats
Etherpad: https://etherpad.indieweb.org/WPandMicroformats for note taking during the session
Streaming video/audio platform: Zoom (link to come)
Demos: Yes – when we’re done, show off how well your new hacked theme works on your site.
Newcomers can post a comment on this post below or reply yes via Twitter to https://twitter.com/ChrisAldrich/status/1300562134699393024. Or you can feel free to just show up on the morning of the event.
Bring your own theme or a theme you’d like to make more IndieWeb friendly by adding Microformats v2 support. Ideas for possible themes can be found at https://indieweb.org/WordPress/Development#Themes
(Optional) Create a GitHub account which you can use/learn during the process. Those who don’t want a GitHub account can simply use their text editor of choice to modify the relevant theme files.
We’re always happy to have additional help! If you’d like to volunteer or help organize and run the session, please touch base with Chris Aldrich or David Shanske in the IndieWeb Meta chat room.
I look forward to seeing everyone there!
September 12, 2020
Sat 9:30am - 12:00pm (America/Los_Angeles)
Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.
Let's discuss how we can close out some outstanding microformats2 issues. See: https://indieweb.org/2020/Pop-ups/Microformats#Agenda for links to sets of issues to consider, optionally add your own issues to those sets as well. This is an intermediate session, with a prerequisite of basic knowledge of HTML and microformats. Experience with publishing and/or parsing is a plus. All are welcome.
listen-ofand potentially other similar future verbs which may have a variety of “tenses” or a sense of progress across time, I wonder if it may be more advisable to have a completely separate progress/tense related microformat? This would provide the broader benefit of allowing it to be reused in those other cases rather than being specific to the read case only.
Perhaps a grow-able spectrum of statuses like:
p-finished? (These are placeholder suggestions as we may do better with some thought on naming). These could be used in combination with the other proposed read, watch, and listen related microformats (or other potential future classes of verbs). The “want” status is reasonably well attested for activities like want to read, want to watch, want to listen, want to buy (or acquire), etc. Most of these are often finished in relatively short (or very long) time frames such that on-going statuses like watching, listening, or owning may not be posted frequently the way that an ongoing “reading” progress-like status might be used over the days, weeks, months that books are being read. I could see myself using ongoing statuses like these being used with to-do list items or project management related functionality as well. Longer term checkins at on-going events (conferences, festivals, vacations, etc.) might benefit from these statuses as well.
Separating the progress (tense) from the verb/action may also make it easier to create collections of posts around the related content. (An example may be the collection of all the posts about a particular book: the want post, the progress posts, notes, annotations, etc.)
On a separate note, I’ll mention that @swentel’s Indigenous for Android has added publishing support for both
p-read-status (as well as all the proposed values) in the past few months.