Difference between revisions of "representative-h-card-authoring"

From Microformats Wiki
representative-h-card-authoring
Jump to navigation Jump to search
(remove XFN parser claim; if you have citations otherwise, please update)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
Line 1: Line 1:
<entry-title>representative h-card authoring</entry-title>
+
{{DISPLAYTITLE:representative h-card authoring}}
  
 
To publish a [[representative h-card]] on a page, in addition to properly following [[h-card-authoring]] instructions, you need to do at least one of two of the following (you can do both).
 
To publish a [[representative h-card]] on a page, in addition to properly following [[h-card-authoring]] instructions, you need to do at least one of two of the following (you can do both).

Latest revision as of 16:32, 18 July 2020


To publish a representative-h-card on a page, in addition to properly following h-card-authoring instructions, you need to do at least one of two of the following (you can do both).

1. hyperlink to the page itself, perhaps around your icon or name (or both), and use both the u-url and u-uid class names in the class attribute on the hyperlink. e.g.:

<span class="h-card">
 <a href="http://tantek.com/" class="u-url u-uid">Tantek Çelik</a>
</span>

2. markup your links to other profiles with both rel="me" and the u-url class name. e.g.:

<span class="h-card">
 <span class="p-name">Tantek Çelik</span> 
 (<a href="http://twitter.com/t" rel="me" class="u-url">my Twitter</a>)
</span>

Or better yet do both:

<span class="h-card">
 <a href="http://tantek.com/" class="u-url u-uid">Tantek Çelik</a>
 (<a href="http://twitter.com/t" rel="me" class="u-url">my Twitter</a>)
</span>

which has the following advantages over either individual example above:

  • a richer, more semantic h-card (e.g. providing two URLs for the person rather than just one)

see also