If this site is even using a database at all, this would be a perfect example to use sqlite. 100% reads, no writes / no administration / no headaches.
Show HN: Recipe search engine, built in vanilla PHP
21–30 of 63 posts
Re: Show HN: Recipe search engine, built in vanilla PHP
#22I'm always slightly surprised at the "engineers mindset" that many people on this site and other seem to approach recipes: the notion that a recipe as a context-free collection of ingredients and steps. Yes, I know "long stories about last year's vacation where we ate such and such" get a lot of universal, justifiable hate. Everyone detests scrolling through "recipes" laden with ads and useless copy and photos. But,…
I've built a few toy apps like everyone else and found the same feeling when it was just a CRUD listing app of recipes that I could search. What I found was an interesting take and one I'm wanting to take further is I want not recommendations on recipes but _almost_ generation of recipes. So when I search "Chile Colorado" it returns a specific recipe that I created but for each "step" it "links" to relations/more info/etc.
Example:
Ingredients:
- 1lb beef
- Ribeye is best
- Sometimes substituting chicken is healthier
- This doesn't double like most things do if you are making more portions
- ....Do you think that caries the context enough? Or do you think that you would just much rather have a list of vetted + manually entered ones?
Re: Show HN: Recipe search engine, built in vanilla PHP
#23I'm always slightly surprised at the "engineers mindset" that many people on this site and other seem to approach recipes: the notion that a recipe as a context-free collection of ingredients and steps. Yes, I know "long stories about last year's vacation where we ate such and such" get a lot of universal, justifiable hate. Everyone detests scrolling through "recipes" laden with ads and useless copy and photos. But,…
Re: Show HN: Recipe search engine, built in vanilla PHP
#24I'm always slightly surprised at the "engineers mindset" that many people on this site and other seem to approach recipes: the notion that a recipe as a context-free collection of ingredients and steps. Yes, I know "long stories about last year's vacation where we ate such and such" get a lot of universal, justifiable hate. Everyone detests scrolling through "recipes" laden with ads and useless copy and photos. But,…
Re: Show HN: Recipe search engine, built in vanilla PHP
#25I'm always slightly surprised at the "engineers mindset" that many people on this site and other seem to approach recipes: the notion that a recipe as a context-free collection of ingredients and steps. Yes, I know "long stories about last year's vacation where we ate such and such" get a lot of universal, justifiable hate. Everyone detests scrolling through "recipes" laden with ads and useless copy and photos. But,…
[deleted]
Re: Show HN: Recipe search engine, built in vanilla PHP
#26Re: Show HN: Recipe search engine, built in vanilla PHP
#27Nice work! I recently built a similar page, https://letscooktime.com , might be good to compare notes. On integrating with recipe APIs, you can scrape recipe structured metadata. Most web sites use the google structured data, you can query for a script tag with type ld+json and find the structured data. See more information here: https://developers.google.com/search/docs/advanced/structure...
Thanks for the advice! Happy to share notes. I really like your site, has better features than mine (adjust Servings, Nutrition Facts by Ingredient). Question, do all the recipe APIs require showing the Source Link to give Credit? Just don't want to violate any terms.
However you should be careful not to copy the blog text or the _images_ from a recipe website, because those require you to get permission from the author for resharing.
Re: Show HN: Recipe search engine, built in vanilla PHP
#28I'm always slightly surprised at the "engineers mindset" that many people on this site and other seem to approach recipes: the notion that a recipe as a context-free collection of ingredients and steps. Yes, I know "long stories about last year's vacation where we ate such and such" get a lot of universal, justifiable hate. Everyone detests scrolling through "recipes" laden with ads and useless copy and photos. But,…
Which means we need a simple database of ingredients/steps and a maybe 300 words introduction. Anyone doing that will crush the market because usability for recipe website went so bad in the past years. And add steps in a visual + text format like KptnCook.
Re: Show HN: Recipe search engine, built in vanilla PHP
#29Earlier quoted context omitted.
Thanks for the advice! Happy to share notes. I really like your site, has better features than mine (adjust Servings, Nutrition Facts by Ingredient). Question, do all the recipe APIs require showing the Source Link to give Credit? Just don't want to violate any terms.
No, you do not have to give attribution to a source if you simply copy the list of ingredients and steps. https://copyrightalliance.org/are-recipes-cookbooks-protecte... . However you should be careful not to copy the blog text or the _images_ from a recipe website, because those require you to get permission from the author for resharing.