feed-brainstorming: Difference between revisions
(draft) |
m (Replace <entry-title> with {{DISPLAYTITLE:}}) |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
{{DISPLAYTITLE:feed brainstorming}} | |||
Part of the [[feed]] microformat development effort per the [[process]]. | Part of the [[feed]] microformat development effort per the [[process]]. | ||
This page is for documenting [[brainstorming]] proposals based on analysis of real world [[feed-examples]] and previous [[feed-formats]]. | This page is for documenting [[brainstorming]] proposals based on analysis of real world [[feed-examples]] and previous [[feed-formats]]. | ||
== previous efforts == | |||
* [[blog-description-brainstorming]] | |||
* [[blog-description-format-brainstorming]] | |||
== h-feed == | == h-feed == |
Latest revision as of 16:22, 18 July 2020
This article is a stub. You can help the microformats.org wiki by expanding it.
Part of the feed microformat development effort per the process.
This page is for documenting brainstorming proposals based on analysis of real world feed-examples and previous feed-formats.
previous efforts
h-feed
In microformats2 simply using a root class name like class="h-feed" on an element that contains all the h-entry elements would be sufficient to create a feed microformat object that can be parsed with all the h-entry elements as children.
root class name: h-feed
example:
<div class="h-feed">
...
<div class="h-entry"> ... entry 1 and properties ... </div>
<div class="h-entry"> ... entry 2 and properties ... </div>
...
</div>
Serves as a way of containing separate sets of related/grouped/sequential h-entry elements on a single page. With HTML ID attributes on the h-feed elements, tools can reference different feeds on the same page and operate on them individually or collectively.