This is a good start. As a foodie who loves to cook and software engineer, I strongly dislike the bloated recipe sites and I have my own mini-site where I share

This is a good start. As a foodie who loves to cook and software engineer, I strongly dislike the bloated recipe sites and I have my own mini-site where I share my recipes with friends. Some ideas to consider, based on my experience building my own Hugo-based static recipe site: - Search: I decided to use Azure Search because of the flexibility it provides (cost is minimal and covered by my free Visual Studio subscription credits) - Images: I use Cloudinary's free plan to upload and deliver images -- very important if you want to deliver performance-optimized experience on multiple devices - Full-screen touch mode: directions only, with easy access to ingredients list. Extremely useful, especially when you have your hands covered in flour and are following directions on a tablet. - "Tips" section: when technique is important, or flexibility is allowed the directions-only may be insufficient - SEO: use standard micro-formats for ingredients, steps and time so the recipes can be easily shared, searched, indexed, etc. - add yield, prep time and total time required - add ingredient and steps sections: some non-basic recipes benefit tremendously from the added organization (e.g. "dry ingredients", "wet ingredients" - usability: UI should be usable and text should be readable from 24-inch distance