4 ms·
The landing page needs a rationale. Why does this product exist? i.e. what problem(s) does it try to solve? For me, I internalize all my recipes after I've mad
by jiggunjer 5y ago
The landing page needs a rationale. Why does this product exist? i.e. what problem(s) does it try to solve?
For me, I internalize all my recipes after I've made them a few times. The main problems I face are related to scaling and unit conversions.
So ideally I'd like to publish an interactive web recipe that lets me input the amount of ingredient X I have (or amount of servings I want) and match the ingredient stochiometry in whatever units I choose.
- XCSme 5y agoI think the problem it solves is pretty clear: provide a standardized way to easily describe and share cooking recipes, which can further help with building apps or communities around this format.
- jiggunjer 5y agoYou don't mention any problem. You just restated what it does, not why.
- XCSme 5y agoIt's a tool, not a solution, you can use it for whatever you need that includes storing, filtering or displaying cooking recipes.
- jiggunjer 5y agoso if I created tool that could be used to drive nails into wood, wouldn't you ask why I created it? i.e. what's wrong with the hammers we've been using so far? I'm not saying it's not a useful development, but a good product description helps adoption.
- XCSme 5y agoI think when it comes to CookLang, most users don't know of another similar tool, this is why it is attractive. If you said "I created a tool that can be used to drive nails into wood" and people had no idea hammers were thing, they would probably not ask "why you created it". Personally I never thought about this (Recipe Markup language) and was surprised to see in other comments that a Schema already exists for recipes, even though the Markup syntax looks a lot cleaner and easier to use.