Show HN: Github for recipes • Hacker News Board

Re: Show HN: Github for recipes

#21

Post by dpick » Sat, Jan 26, 2013, 4:29 PM UTC

dbaupp wrote: post #19

dpick wrote: post #10

Hey Guys, I'm the creator of Forking Recipes, I'll be happy to answer any questions you have and thanks for taking a look!

I really like this! Hopefully it gains momentum because it'd be really neat to have [a tool that can be used as] a crowd-sourced recipe-optimiser. On a different note, I'm on a slow internet connection and it's very noticeable that the page is huge and not optimised for bandwidth (some thumbnailing and gzip-ing would be good to add at some point, to make the site as snappy as possible! :) ). https://developers.google…

Thanks for the feedback! I'm actually working on making the main page use thumbnails right now.

Re: Show HN: Github for recipes

#22

Post by Cacen » Sat, Jan 26, 2013, 4:34 PM UTC

duiker101 wrote: post #17

You missed the opportunity to use the name GitCipes.

that doesn't sound too great; unless I'm missing something, it doesn't involve git.

Re: Show HN: Github for recipes

#23

Post by d0m » Sat, Jan 26, 2013, 4:34 PM UTC

I find it waaaay too geeky for a cooking website. The idea could be useful but as it is right now, it's very hard to understand how it's supposed to work. (Revision 2, what?)

Re: Show HN: Github for recipes

#24

Post by Swizec » Sat, Jan 26, 2013, 4:35 PM UTC

\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.

Re: Show HN: Github for recipes

#25

Post by gurraman » Sat, Jan 26, 2013, 4:37 PM UTC

I started something similar[1] last Christmas (but lost interest as I never documented my own experiments). It's a great idea and there's need for a de facto standard source for recipes and cooking instructions.

My "next step" was to contact sous chefs of famous restaurants.

[1] http://palatelab.com/

Edit: rephrased.

Re: Show HN: Github for recipes

#26

Post by gingerjoos » Sat, Jan 26, 2013, 4:37 PM UTC

Cucumbertown does this very well. They allow you to take a recipe and fork it – called “Write a variation” (on the left) [1]. IIRC quite a few recipes there are created this way.

[1] http://www.cucumbertown.com/recipes/55228/baked-mac-cheese

Re: Show HN: Github for recipes

#27

Post by Thrall » Sat, Jan 26, 2013, 4:39 PM UTC

Having looked at some of the recipes, it might be nice to take the job of layout/formatting away from the recipe submitter and offer some differnt layout options to the person viewing it.

For example, some recipes include the accompanying photos inline, while others collect the photos at the end. If instead, the submitter merely tagged the photos according to what step they accompanied, then the website code can lay them out beatifully in a number of different ways to suit different viewers.

I think I'm thinking something along the lines of LaTeX philosophy: You provide the content and leave the layout to the experts/computer. So you don't write that "Zest of 2 lemons" should be part of a bulleted list, you write that it is an ingredient and leave it to the layout to put it in a suitably formatted ingredient list.

Another advantage is you reduce the ability of less savvy users to make parts of your site look ugly.

Re: Show HN: Github for recipes

#28

Post by tantalor » Sat, Jan 26, 2013, 4:40 PM UTC

siddhant wrote: post #16

trhaynes wrote: post #7

Why not build this right on top of GitHub?

Because most cooks are not developers and don't have Github accounts, I guess.

I think trhaynes meant, Why not build this on the Github API?

Re: Show HN: Github for recipes

#29

Post by cheald » Sat, Jan 26, 2013, 4:41 PM UTC

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.

Re: Show HN: Github for recipes

#30

Post by dpick » Sat, Jan 26, 2013, 4:41 PM UTC

Thrall wrote: post #27

Having looked at some of the recipes, it might be nice to take the job of layout/formatting away from the recipe submitter and offer some differnt layout options to the person viewing it. For example, some recipes include the accompanying photos inline, while others collect the photos at the end. If instead, the submitter merely tagged the photos according to what step they accompanied, then the website code can lay…

That's a great idea, thanks!