My unsolicited advice: try to split up basics, common-recipes and specialties.
Basics are "how to bind soup", "choosing and cooking pasta", or "frying onions". Common recipes are then "bound vegetable soup" or "maccharoni with tomatosause (and fried onions)". Specialities would be those recipes you try for christmas, or when the in-laws come over next month.
It's highly frustrating to find a recipe that says "bind the soup with starch" without going into how to do this (or even worse: what ingredients this needs!). But for someone more experienced, it is highly frustrating to have to read through five lines explaining how to fry the onions.
As with most education, cooking is layered: you build on top of existing knowledge, without repeating it each and every time. I presume this is partly a classification issue and organisation challenge. You don't want "how to bind soup without milk or eggs" to turn up when someone is searching "vegan tomato-soup". The web has hyperlinks, which would probably be a very good way to organize recipes.
Basics are "how to bind soup", "choosing and cooking pasta", or "frying onions". Common recipes are then "bound vegetable soup" or "maccharoni with tomatosause (and fried onions)". Specialities would be those recipes you try for christmas, or when the in-laws come over next month.
It's highly frustrating to find a recipe that says "bind the soup with starch" without going into how to do this (or even worse: what ingredients this needs!). But for someone more experienced, it is highly frustrating to have to read through five lines explaining how to fry the onions.
As with most education, cooking is layered: you build on top of existing knowledge, without repeating it each and every time. I presume this is partly a classification issue and organisation challenge. You don't want "how to bind soup without milk or eggs" to turn up when someone is searching "vegan tomato-soup". The web has hyperlinks, which would probably be a very good way to organize recipes.