As a person with better visual memory for certain kinds of data, having the original page content may have as much meaning as the recipe, for entirely different reasons. Food can be very personal, and recipe books doubly so. A recipe archive can be as personal as we like, or all of that can abstracted away when we don’t need it.
I remember first seeing it on Slashdot way back in the day, before they had user moderation or user meta-moderation.
https://blogs.loc.gov/thesignal/2012/04/a-library-of-congres...
If you save the source document, the code needed to parse your recipe archive is likely to be pretty short. Then you have a corpus to do A/B testing of your recipe parsing code against.
Side note: I feel that moderation and later meta-moderation system on Slashdot was the most transparent, fun, positive moderation system I’ve ever been part of. I wish HN had more than just up and downvotes, for instance. User meta-moderation would help reduce flamewars immensely IMO.
One major flaw: it seems like the calories and macros aren’t captured. For bodybuilding and powerlifting types, and other athletics, these are the most important part of a meal.
What would make this a “killer app”, in my view, is if I could request a recipe in JSON instead of just formatted plain text as you do. Then I could use the recipe (and recipe search) in my own home-brewed meal planning program.