Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

The Kitchn #82

Open
shiflett opened this issue Mar 29, 2013 · 2 comments
Open

The Kitchn #82

shiflett opened this issue Mar 29, 2013 · 2 comments

Comments

@shiflett
Copy link
Contributor

http://www.thekitchn.com/

@sstrudeau
Copy link

Hi Guys,

We (the Apartment Therapy & The Kitchn tech team) would love to assist in any way we can. Our recipe data is currently unstructured on our side, but we'd like to work with anyone building recipe-parsing tools (in part to help us clean up & structure our archive) and in the future layer some structure into our CMS for recipe data to make it easier to ingest for tools like this.

@funkatron
Copy link
Collaborator

Hey Scott,

I think the super best thing you could do is implement a semantic microdata
format like http://schema.org/Recipe. That makes things way easier to
identify and parse, and lets us do it with generic parsing tools instead of
site-specific parsers.

At first glance, this may be useful:
http://blog.ziplist.com/schema-recipe-mark-up-for-food-blogs/

On Mon, Apr 1, 2013 at 4:24 PM, Scott Trudeau notifications@github.comwrote:

Hi Guys,

We (the Apartment Therapy & The Kitchn tech team) would love to assist in
any way we can. Our recipe data is currently unstructured on our side, but
we'd like to work with anyone building recipe-parsing tools (in part to
help us clean up & structure our archive) and in the future layer some
structure into our CMS for recipe data to make it easier to ingest for
tools like this.


Reply to this email directly or view it on GitHubhttps://github.com//issues/82#issuecomment-15735087
.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants