I love the idea. But its so difficult to know if its worth investing in using the format or if it will end up languishing.
Cooklang – Managing Recipes in Git
31–40 of 49 posts
Re: Cooklang – Managing Recipes in Git
#32An alternative to this is Chowdown and YAML: https://github.com/clarklab/chowdown
Or GoChowdown and YAML: https://github.com/seanlane/gochowdown
Re: Cooklang – Managing Recipes in Git
#33Remember when we shared recipes on the Usenet with the Meal-Master format?
Re: Cooklang – Managing Recipes in Git
#34Shameless plug for my recipes side project I re-released a few days ago https://www.recilution.com on fly.io. Still lots to do.
I actually looked at this along with git backed recipes as repositories. I can see it useful for personal sites or exchanging with people if there is client involved as it's quite portable. You could do versions, diffs, timelines all sorts.
However it's rather esoteric (I guess everything on Hacker News is!?) and don't think it applies to the masses.
Despite recipes being very simple as a list of ingredients and things to do there is actually lot things you can slice things to try to make things easier whether thats viewing the recipe or editing.
For me the challenge I find is finding recipes and then refining them in such a way they are turn out the way I want them without having to read pages of introductory text you find in most recipe blog sites
Re: Cooklang – Managing Recipes in Git
#35Seems to me that it's about Cooklang, not about git. Nevertheless it looks neat!
For bread and baking in general, it might be useful to have it support Baker Percentage[1], either explicitly or by using specific tags for scaling dry and wet ingredients.
Re: Cooklang – Managing Recipes in Git
#36I just wanted to shout out Cooking For Engineers even though it’s only moderately related. Its format for recipes is so quick to read. I would love to see CookLang integrate this style of recipe viewing. http://www.cookingforengineers.com/recipe/108/Banana-Nut-Bre...
This project generates recipes in this format from a custom language:
https://github.com/mossblaser/recipe_grid
I use it regularly and it works well!
Re: Cooklang – Managing Recipes in Git
#37Sorry if this comes off as a noob question, I'm not a technical person but came from a marketing background. Generally what is the monetisation model for founders developing languages like Cooklang? Would they sell support for the language, or create an ecosystem around it?
LOL. Simple projects like this are a dime a dozen. There's no money to be made here.
Re: Cooklang – Managing Recipes in Git
#38I'd remove the % sign from the syntax for ingredients.
And how does the ingredients scale? Surely cooking for 1 person vs 4 person requires different amount of ingredients.
The % in this syntax is not to indicate information about scaling, it is just a meaningless separator: "3%tsp". I'd say both "3tsp" or "3 tsp" look better.
Re: Cooklang – Managing Recipes in Git
#39I just wanted to shout out Cooking For Engineers even though it’s only moderately related. Its format for recipes is so quick to read. I would love to see CookLang integrate this style of recipe viewing. http://www.cookingforengineers.com/recipe/108/Banana-Nut-Bre...
This project generates recipes in this format from a custom language: https://github.com/mossblaser/recipe_grid I use it regularly and it works well!
This looks amazing, thanks for sharing!
Re: Cooklang – Managing Recipes in Git
#40Earlier quoted context omitted.
And how does the ingredients scale? Surely cooking for 1 person vs 4 person requires different amount of ingredients.
The % in this syntax is not to indicate information about scaling, it is just a meaningless separator: "3%tsp". I'd say both "3tsp" or "3 tsp" look better.
The author didn't go with a space because[0] some things have spaces in them, which would be harder to figure out.