Jump to: navigation, search

h-example is a microformats-2 standard for representing Examples. It builds upon the classic hExample microformat.

Translations: link to each translation as hCard does



All properties are optional and are parsed according to the microformats-2-parsing specification.


Implied examples, if any:

Full example:

<div class="h-example">
  <span class="p-name">An Example Example</span>
  <p>Published <time class="dt-published" datetime="2013-05-02 12:00:00">two days ago</time></p>
  <p class="p-author h-card">Mr. Author</p>
  <img class="u-photo" src="" alt="" />
  <p class="p-summary">An example example showing you how to example</p>
 "type": ["h-example"],
 "properties": {
  "name": ["An Example Example"],
  "published": ["2013-05-02 12:00:00"],
  "author": [{
    "type": ["h-card"],
    "properties": {
     "name": ["Mr. Author"]
    "value": "Mr. Author"
  "photo": [""],
  "summary": ["An example example showing you how to example"]

Examples in the wild


What this was based off, why it was created etc.

See Also


Properties first or examples first? returning viewers are most likely to want quick reference to properties, first time viewers are most likely to want an example. Perhaps do as hCard does with the property list => markup 1:1 thing, unless that ends up looking too noisy?


For each property, give:

Perhaps link to common, shared/implied property classnames (p-name, u-url etc) to their own page? TODO: how to handle properties which probably should be a nested microformat but can also be a plain value? E.G. author:


Ideally all examples will be shown 1:1 with their JSON representation, OR editable with JS to submit it to a parser and show the JSON — this would encourage people to experiment and greater understand the relationship between markup and parsed structure.

mf2-spec-template-brainstorming was last modified: Thursday, June 6th, 2013