representative-h-card-authoring - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:32:37Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:32, 18 July 2020
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).

GRegorLove: remove XFN parser claim; if you have citations otherwise, please update

2018-07-20T22:29:37Z

remove XFN parser claim; if you have citations otherwise, please update

← Older revision		Revision as of 22:29, 20 July 2018
Line 22:		Line 22:

	which has the following advantages over either individual example above:		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)		* a richer, more semantic [[h-card]] (e.g. providing two URLs for the person rather than just one)
	* works with both h-card-only parsers/crawlers and XFN-only parsers/crawlers

	== see also ==		== see also ==
	{{representative-hcard-related-pages}}		{{representative-hcard-related-pages}}

GRegorLove: h-card-specific version

2018-07-20T22:19:30Z

h-card-specific version

New page

<entry-title>representative h-card authoring</entry-title>

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 <code>u-url</code> and <code>u-uid</code> class names in the class attribute on the hyperlink. e.g.:
<source lang=html4strict>
<a href="http://tantek.com/" class="u-url u-uid">Tantek Çelik</a>
</source>

2. markup your links to other profiles with both <code>[[rel-me|rel="me"]]</code> and the <code>u-url</code> class name. e.g.:
<source lang=html4strict>
Tantek Çelik
(<a href="http://twitter.com/t" rel="me" class="u-url">my Twitter</a>)
</source>

Or better yet do both:

<source lang=html4strict>
<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>)
</source>

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)
* works with both h-card-only parsers/crawlers and XFN-only parsers/crawlers

== see also ==
{{representative-hcard-related-pages}}