@paprikaapp Just found out about this, looks really neat! Would you consider adding microformats2 to the HTML output? microformats.org/wiki/h-reci…
1
1
@aaronpk Sorry to have missed this! Checking it out now, will of course add support this is pretty neat.
1
@paprikaapp Cool! This would be a great way to turn the app export into an API! Happy to answer questions too.
1
@aaronpk Right now we use schema for most of the app exports (or hrecipe, need to standardize it), you may already know that?
1
@paprikaapp hm I didn't see anything other than plain HTML in the export. Luckily microformats2 can co-exist with other markup as well!
1
@aaronpk Which version/platform of the app are you exporting with? I can double check the nature of the markup for that version.
1
@paprikaapp OSX, and presumably a recent version. It was actually @jerrysievert exporting so he knows which version
3
@aaronpk @jerrysievert In our latest Mac code as it is in Xcode every file's body should have an hrecipe class, and all h1's have fn, etc.
1
1
Replying to @paprikaapp
@paprikaapp Cool! It would still be great to get the Microformats 2 classes in there since it's actually a lot easier to deal with now.

Aug 6, 2015 · 4:02 AM UTC

2
Replying to @aaronpk
@aaronpk Yeah I think we're still good...
Replying to @aaronpk
@aaronpk ...but that's a good idea, we should really export with all forms of metadata included, hrecipe 1&2/schema.