Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we improve h-entry backcompat to handle common WordPress hentry streams? #7

tantek opened this issue Mar 24, 2018 · 2 comments


None yet
3 participants
Copy link

commented Mar 24, 2018

h-entry Parser Compatbility specifies typical hAtom hentry properties and how to consume them as h-entry equivalents. This appears to be insufficient for some common WordPress themes. We should investigate examples of WordPress blogs with hAtom to see if we can do better with additional hentry backcompat parsing.

h-entry has two proposed additions so far that we should validate with examples in the wild (that would be result in better parsed results with those additions)

  • time.entry-date[datetime] - parse as dt-published
  • rel=author - parse as u-author

Examples welcome of common / plain / modern WordPress home pages that currently fail to produce good hentry backcompat parsing results.

cc: Labels: help wanted, question

(Originally published at:


This comment has been minimized.

Copy link

commented Aug 22, 2018

How does time.entry-date[datetime] differ in usage from time.published[datetime]? The couple wordpress sites I looked at had both entry-date and published on the time element.

I'll have to think through how rel=author would work with the authorship algorithm to make sure that would help in this case.


This comment has been minimized.

Copy link

commented Aug 24, 2018

@aaronpk it might have been in chat, but if I recall, there is already entry-* backcompat classes, so adding entry-date would stay in line with those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.