h-feedh-feed is a microformats2 experiment with a top level feed object to contain h-entry posts. It is functionally a DRYer replacement for RSS/Atom feed files and thus could supersede them.
HowHow to markupMark up your
How to testFeeds marked up with h-feed should work in the same way as simple lists of h-entries. See How to Test Feeds. How to consumeWhySo indie readers who subscribe to your site can display:
WordPress and HFeedA large percentage of WordPress themes use hfeed on every page, as opposed to only on pages with multiple hentrys. Due to the popularity of WordPress, this is present on a large number of websites. IndieWeb ExamplesIndieWeb community members that support h-feed: TantekTantek Çelik supports h-feed on his tantek.com home page using an index.html template and Falcon since 2012-07-16, at Sandeep Shetty's encouragement, to help with the indie reader he is building. Shane BeckerShane Becker supports h-feed on his veganstraightedge.com home page using for his composite feed of posts and on each post-type specific feed (/notes, /articles, /bookmarks, /videos, /notes) since 2012-11-18 (private repo). He previously supported just hfeed on his feeds since 2010-06-04 (private repo). Will NorrisWill Norris supports h-feed on his willnorris.com home page since mid-2013 using WordPress and a modified version of wordpress-uf2 (modifications to be sent upstream at soonish?) Kevin Marks
Barnaby WaltersBarnaby Walters supports h-feed on his waterpigs.co.uk home page since 2014-01-21 JeenaJeena supports h-feed for his blog posts and notes on https://jeena.net since 2014-02-25 Tom MorrisTom Morris supports h-feed for posts on tommorris.org since 2014-02-25. Bear
Pelle Wessman
gRegor Morrill
Ben Roberts
rhiaro
Jonny BarnesTemplate:jonnybarnes supports h-feed for notes at https://jonnybarnes.uk/notes since ? Brainstormingpartial feedsPartial (e.g. truncated) vs full h-feeds. A lot of blogs have feeds with partial content, where the entries only have post names/titles, permalinks, and sometimes summaries but not full post content. This could be done for UX reasons where the reader is not subjected to a full long post but a quick list of shorter summaries. If you do have a partial feed (e.g. on your home page), it is good (for indie reader consumption) to also have a separate full feed page. The partial feed can use a
<div class="h-feed" id="partial_feed">
<h1 class="p-name">
<a class="u-url" href="#partial_feed">Partial Feed</a></h1>
<a class="u-uid u-url" href="/feed.html">Full Feed</a>
<ol>
<li class="h-entry"><a href="permalink1">Article1 name</a></li>
<li class="h-entry"><a href="permalink2">Article2 name</a></li>
</ol>
</div>
design freedomThe possibility of separate partial vs full feeds provides more design freedom for content publishers, since they can choose to have a full or partial (or no!) feed on their homepage and thus design accordingly. acegiak: KartikPrabhu: my wife's site (which I'm helping her add microformats etc to) is a potential test for this because she's an artist and wants her landing page to be quite specific in appearance. from: http://indiewebcamp.com/irc/2014-03-27/line/1395970560 canonical feed autodiscoveryprior workFeed readers discover the links to legacy RSS/Atom feed files automatically from HTML pages by parsing for links with When such links use the Example from adactio.com in Feedly How can (possibly multiple) h-feed feeds be discovered similarly? rel feedLink to h-feed marked-up html pages from the home page using More on: 1. http://tools.ietf.org/html/draft-ietf-atompub-autodiscovery-01 2. http://blog.whatwg.org/feed-autodiscovery url uidAlternatively, if an h-feed has a u-url u-uid property that is not the URL of the current page itself, then that u-url u-uid URL can be treated as the canonical full feed. Articles
See AlsoLegacy: |



















