345
results for "microformats hard"
-
Maybe if you squint hard enough.
[jgarber]
at
2025-05-26 04:47
-
It's been four years, so hard to say with any precision, but what he asked about there also vaguely looks like a feature that landed in Eleventy where the tool may be configured to infer output URLs based on input file paths.
[jgarber]
at
2025-05-26 03:00
-
There are so many templating systems, hard to say anything. Basically all of them can generate HTML with classes, so all of them would be able to add microformats.
Zegnat
at
2025-05-10 17:33
-
It’s hard to tell but I’d agree with gRegor and use p-locality. The parsed JSON output from the example of a parsed h-adr seems to imply you can have multiple of them, so if you needed to you could put e.g. “Southside” and “Fort Worth” as localities for somewhere in Southside.
[dave]
at
2025-04-10 23:18
-
Yes. Bandwagon will *be* a consumer of this data, too, as a search engine that scans many indie sites (like Faircamp and others) . ActivityPub is hard, MicroFormats are easy, so if all those DIY sites can present their data in MF2, then I can add them to the search index.
benpate
at
2024-12-17 22:55
-
yeah lang "inheritance" is very hard to get right, and predict as an author. it's one of the "not great" mechanisms in HTML 😕
[tantek]
at
2024-09-03 22:50
-
specs are hard
[tantek]
at
2024-05-23 19:31
-
I'd also imagine that would help adoption if there's a tool to help nudge towards valid mf2 (linters have helped me with this in general and good compiler errors - which are hard)
jacky
at
2024-03-11 16:07
-
the parser has a hard failure when it comes across a property declaration when no item has been declared yet. going to flip this to a warning (one of the first lints I can make with this!)
jacky
at
2024-03-11 15:11
-
this distinction was hard for me to grok (and has been probably why the rust parser has been so out of whack)
jacky
at
2024-03-08 18:50