#microformats 2026-08-14

2026-08-14 UTC
Zuka, [social]3, IWSlackGateway2, christof, [jeremycherfas], [tantek]4, ZodiacalComet, plantroon, [KevinMarks], [aciccarello] and [artlung] joined the channel
#
[tantek] christof do you have any h-resume test cases that you'd be willing to contribute to an h-resume test suite?
#
[aciccarello] I'd be curious to know how an h-resume is consumed. I have my resume marked up but have no idea if it's formatted in a way that is usable.
#
jkingweb More test cases! Can never have too many!
barnaby joined the channel
#
christof @[tantek] The page I use to test the profile importer, might be an option there. It also contains my extensions: https://www.okunah.de/profed_profile/ This is not styled at all. It is only about the HTML content.
#
christof The profile importer code is here: https://codeberg.org/ProFed/ProFed/src/commit/55c34a811a6c1d6d56fc9273cc2a27c3bb56cf76/src/profed/components/profile_importer
Colbur joined the channel
#
gRegor Nice! parsed results: https://php.microformats.io/?url=https%3A%2F%2Fwww.okunah.de%2Fprofed_profile%2F
Colbur joined the channel
#
gRegor Not sure you need the `e-x-summary`. `summary` is a common property in other microformats so re-using that makes sense. `p-summary` if you want the parsed result to be plaintext, `e-summary` if you want the parsed result to be HTML + plaintext. Don't need both on the same element.
#
gRegor I'd lean towards `p-summary`
#
gRegor An `-x-` or other vendor prefix mostly makes sense if you're trying out an entirely new property, like with read posts we've experimented with a `read-status` property for things like "currently reading" "finished reading" etc.
#
gRegor Compare p-summary: http://php.microformats.io/?id=20260814194628301 with e-summary: http://php.microformats.io/?id=20260814194815953
#
gRegor exciting project, yay more tests!
[jeremycherfas], [jeremycherfas]1, boramalper3, sknebel and Zegnat joined the channel