undefined | Better HN

0 pointsmcdonje2y ago0 comments

Thanks. I can't figure out how to look at the markdown. I made an account figuring that'd let me edit (so I can view), but the protections apparently have another level.

So, are the components different files? That'd definitely help if there's a component that applies to several recipes, like a sauce or crust. However, it could make things more complicated than some would like if they're working on a smaller project, like a reference notebook or a family cookbook.

Power vs simplicity is often a balancing act.

0 comments

guhidalg2y ago

> I made an account figuring that'd let me edit (so I can view), but the protections apparently have another level.

Thanks for making an account! You can only edit you own recipes, but I (the admin) can edit any recipe. I guess you tried to edit a recipe you liked, would you like a "Copy and Edit Recipe" feature?

> So, are the components different files?

Components are what CookTime recipes are made of. A recipe has at least one component, and if necessary the author can add additional components to indicate different ingredient quantities for different components. I have thought about having re-usable components across recipes, I just haven't given thought to how to design the UX for it. Glad to hear that someone else would find it useful, I think I'll reprioritize this.

> I can't figure out how to look at the markdown.

In CookTime there isn't a simple textual representation of a recipe (unless you count the big JSON object the browser sends over the wire.). The backend is a relational database of recipes, components, ingredient requirements, nutrition data, etc...

> Power vs simplicity is often a balancing act.

100%, my primary user is my mother-in-law and I have to be extra careful to make everything easy to use for an enthusiastic retiree.

j / k navigate · click thread line to collapse