💬 RFC: consistent format for recipes

andrewduckett / recipes

Do What The F*ck You Want To Public License

1 stars 1 forks source link

💬 RFC: consistent format for recipes #3

Open andrewduckett opened 2 years ago

andrewduckett commented 2 years ago

🔖 Need, Context, and Problem Statement

I would like to choose a format for recipes so we can edit, lint, and view them consistently.

Some requirements from me (open to more)

template must render the ingredient list first, this will make it easier when shopping.
template must render into GItHub Pages

🎉 Proposal

Choose one of the following (see below). I'm sure more options exist

My current preference is Cooklang, this just seems cool/fun to try. Rendering seems pretty straight forward in a GitHub Action.

Cooklang – Recipe Markup Language

〽️ Alternatives

cmeinco commented 1 year ago

Need a domain to host it also. Hungrynerds?

cmeinco commented 1 year ago

Cooklang looks the most maintained. i vote for that.

wsguede commented 1 year ago

i assume

T = table t = tea ???????? Is that a common format idea?

andrewduckett commented 1 year ago

i assume

T = table t = tea ???????? Is that a common format idea?

That's one way. I've also seen tbsp and tsp

from wikipedia

In recipes, an abbreviation like tbsp. is usually used to refer to a tablespoon, to differentiate it from the smaller teaspoon (tsp.). Some authors additionally capitalize the abbreviation, as Tbsp., while leaving tsp. in lower case, to emphasize that the larger tablespoon, rather than the smaller teaspoon, is wanted. The tablespoon abbreviation is sometimes further abbreviated to Tb. or T.

Cooklang doesn't seem to have a strong opinion so I don't think it really matters as long as it's consistent?