Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Github for recipes

forkingrecipes.com

Post reply on HN
Print view View original

71–80 of 103 posts

Re: Show HN: Github for recipes

#71

Post by chewxy »

ChuckMcM wrote: post #65

I like it, although I think there are other organizing principles to explore. Seconded on all the 'fork' comments its not at all intuitive to a chef what you mean here. At present the top level abstraction is the recipe which you've sort of equated to 'source code' but when you look at something like Github or Sourceforge the high level abstraction is the 'project' and in the food world the closest I could come up wi…

Hey, at Fork the Cookbook, we're doing just that right now! It's one of the primary reasons why we said Search is Hard [0]. And we're working hard on search.

We've also put a lot of time and effort into researching the licensing issues, as well as design issues: how to present certain things like diffs, and stuff. So if you like, you should check out Fork the Cookbook: http://forkthecookbook.com

[0] http://theforkingchef.com/post/40890655560/search-is-hard-pa...

Re: Show HN: Github for recipes

#72

Post by BHSPitMonkey »

chewxy wrote: post #70

We launched Fork the Cookbook about the same time as Forking Recipes too. You might want to check it out: http://forkthecookbook.com We try not to call it Github for Recipes because that's not our target market (although other people have called us Github for Recipes) We blog over at http://theforkingchef.com so you might also want to check that out. OK, self promotion over

I like your site's presentation quite a bit more (ForkingRecipes just comes across as data carelessly tossed into Bootstrap), though I don't quite like how the food images are mostly obscured until you hover over them individually.

Re: Show HN: Github for recipes

#73

Post by chewxy »

BHSPitMonkey wrote: post #72
chewxy wrote: post #70

We launched Fork the Cookbook about the same time as Forking Recipes too. You might want to check it out: http://forkthecookbook.com We try not to call it Github for Recipes because that's not our target market (although other people have called us Github for Recipes) We blog over at http://theforkingchef.com so you might also want to check that out. OK, self promotion over

I like your site's presentation quite a bit more (ForkingRecipes just comes across as data carelessly tossed into Bootstrap), though I don't quite like how the food images are mostly obscured until you hover over them individually.

Understandable. We're working on a variation that doesn't do that. UX is hard yo.

Fork the Cookbook has existed longer than Forking Recipes, and we've done hundreds of user tests. It turns out users really like certain things, and so the current darkened background is a compromise on that solution.

We found out that users liked pictures, and also liked text (surprise?). In the next test we're doing, we're going to be swapping the order of appearance to see if the CTRs increase

Re: Show HN: Github for recipes

#74

Post by chewxy »

cheald wrote: post #29
orangethirty wrote: post #9

You need to hire a designer for this. Cooking/recipes/food markets are really visually driven. You also need to define what a fork is right on the landing page. A fork for a cook is not the same as a fork for a programmer. What you should have is a good header area that has the application work flow explained in graphics. Example: Alice liked Juan's recide for thai rice. She wanted to create her own version. Alice fo…

I'd like to second this, and also say that you should really work hard to establish "fork" and "forking" in contexts that make sense to non-developers. They're second nature for us, but non-technical cooks will probably either read it as "fucking recipes", or conflate fork (to diverge) with fork (eating utensil). That said, awesome idea.

Hi, I am part of ForkTheCookbook [0]. We actually actively face this problem, which is why in our FAQ, the 2nd question tries to answer that: http://forkthecookbook.com/faq

[0]http://forkthecookbook.com

Re: Show HN: Github for recipes

#76

Post by eam »

chewxy wrote: post #74
cheald wrote: post #29

Earlier quoted context omitted.

I'd like to second this, and also say that you should really work hard to establish "fork" and "forking" in contexts that make sense to non-developers. They're second nature for us, but non-technical cooks will probably either read it as "fucking recipes", or conflate fork (to diverge) with fork (eating utensil). That said, awesome idea.

Hi, I am part of ForkTheCookbook [0]. We actually actively face this problem, which is why in our FAQ, the 2nd question tries to answer that: http://forkthecookbook.com/faq [0] http://forkthecookbook.com

Tried going to the links and for some reason they are triggering my McAfee Site Advisor with "Warning: Suspicious Site".

Re: Show HN: Github for recipes

#77

Post by chewxy »

eam wrote: post #76
chewxy wrote: post #74

Earlier quoted context omitted.

Hi, I am part of ForkTheCookbook [0]. We actually actively face this problem, which is why in our FAQ, the 2nd question tries to answer that: http://forkthecookbook.com/faq [0] http://forkthecookbook.com

Tried going to the links and for some reason they are triggering my McAfee Site Advisor with "Warning: Suspicious Site".

Hmm, I wonder why. Is there any way to check why?

EDIT: According to Site Advisor (http://www.siteadvisor.com/sites/forkthecookbook.com), here are their criteria:

Country indicates where a domain is registered | US/AUS

Popularity indicates how many visitors a website gets | Not very popular

E-mail indicates our overall opinion of a website's e-mail practices | We don't spam

Downloads indicates our overall opinion of a website's downloadable files | No file downloads

Online Affiliations indicates our overall opinion of a website's linking practices | We vet every link. Every write up. It could be one of our authors are having a malware issue. Not sure about that.

Annoyances indicates our overall opinion of a website's pop-up practices. | No popup.

Exploits are rare but extremely dangerous security threats caused by a website "exploiting" a security vulnerability in the browser. | Don't think we have exploits. Something to check

Web reputation McAfee tests websites for web reputation using the TrustedSource™ system. | Totally not helpful

Reviewer and Site Owner Comments | I see no reviews

Re: Show HN: Github for recipes

#78

Post by [deleted] »

chewxy wrote: post #69
Swizec wrote: post #24

\o/ I asked for this 16 days ago ( http://news.ycombinator.com/item?id=5033978 ) and now it exists. God I love HackerNews :D Probably not related, though still cool. What I'd like to see though, is for all the pictures to be of food. There's a lot of happy faces, but the point of a cook book is to make me feel hungry when looking at the pictures. Not sure how to achieve that though.

Hey you may want to check out Fork the Cookbook [0]. It was there long before you asked the question. http://forkthecookbook.com

[deleted]

Re: Show HN: Github for recipes

#79

Post by papa_bear »

I've thought a lot about this idea as something to add to my site Eat This Much (http://www.eatthismuch.com)

I have a pretty basic implementation of it right now - you can click a "personalize recipe" button on recipe pages to make modifications to it, and watch the nutrition change as you make changes. As a premium member, you can then have the meal plan generator suggest your modified version of the recipe in place of the original. When I have the time, I'm hoping to make all the existing branches and variations browsable.

There are some pretty great suggestions here I think. It would be really cool if you could build out an API similar to yummly's for serving up recipes. With different branches for each recipe, you could easily search through the variations to satisfy filters based on a user's tastes.

Re: Show HN: Github for recipes

#80

Post by 18pfsmt »

orangethirty wrote: post #9

You need to hire a designer for this. Cooking/recipes/food markets are really visually driven. You also need to define what a fork is right on the landing page. A fork for a cook is not the same as a fork for a programmer. What you should have is a good header area that has the application work flow explained in graphics. Example: Alice liked Juan's recide for thai rice. She wanted to create her own version. Alice fo…

Perhaps showing a fork as an icon, and then a simple recipe of a different variation along each prong might help visually?
Post reply on HN