#microformats 2025-04-03

2025-04-03 UTC
sebbu, GandalfDG, [schmarty], adam1, ancarda, hedy, greenfork, capjamesg, mebious, [qubyte], Tiffnya, milkii_, barnaby, [dave] and gRegor joined the channel
#
thepaperpilot Howdy! I'd take a break from working on my website for awhile, but I'm still working on adding all of my posts from various social media as well as commits and stuff. I'm using nuxt, but I've decided to move away from nuxt content, the file based CMS they use. Instead I'd like to use a bit of a young project I'm excited about called leaf, which basically stores data in entities which are just lists of components. The main i
btrem and duanin2 joined the channel
#
thepaperpilot [edit] Howdy! I'd taken a break from working on my website for awhile, but I'm still working on adding all of my posts from various social media as well as commits and stuff. I'm using nuxt, but I've decided to move away from nuxt content, the file based CMS they use. Instead I'd like to use a bit of a young project I'm excited about called leaf, which basically stores data in entities which are just lists of components. Th
#
gRegor Your message is getting truncated when bridged to IRC
#
gRegor Not sure if there's a microformats question that got lost
#
[artlung] (copying over from Discord in smaller chunks)
#
[artlung] [thepaperpilot]: he main idea is that those entities can be passed around and viewed by different applications, and even if a software doesn't understand all the components, it can still display something based on the components it does understand. With that in mind, I was thinking of making a
#
[artlung] [thepaperpilot]: component and some utility functions for a microformats2 component, which in theory would be enough to turn any leaf entity into an h-entry. I was wondering if people here had opinions on how this component should look? E.g. should it just contain a json string of mf2 properties and their values?
#
gRegor thx!
#
gRegor I'm not familiar with nuxt/leaf, though if you're generating HTML from it, JSON seems like a fine method. That's the format microformats parsers return.
[capjamesg] and [tw2113] joined the channel
#
[KevinMarks]1 Storing the parsed microformats structure could make sense, or maybe jf2 if you want something a bit simpler.
barnaby joined the channel
#
thepaperpilot The entities would basically just be how the data is stored in the backend; they'd still get rendered on the page like any site
#
thepaperpilot So the mf2 component is just so others who want to work with mf2 data could potentially work with the entities directly
#
thepaperpilot In which case, having the same format parsers output would be ideal 👍