41–50 of 63 posts
What I would love to find is a database of recipes so that I could build my own front end.
I think there's tons of recipe api's out there. Check out RapidAPI: https://rapidapi.com/hub
Looks clean and objective. Congrats! Quick question. What do you use Stripe for? And if I may, I would move this stripe tag to the bottom of . Should speed up DOM loading: https://i.imgur.com/0X93EHy.png
Thanks for the tip! Wasn't sure where the DOM was lagging. For your question, if you register an account, you can't post a recipe unless you upgrade to a premium account. I'm not expecting anyone to actually pay for this feature, I just put it up to prevent anyone from spamming images. Every user is able to comment on recipe pages though.
Earlier quoted context omitted.
I think there's tons of recipe api's out there. Check out RapidAPI: https://rapidapi.com/hub
Thanks, but I'm not looking for an API, I'm looking for a database. Something I can query with simple command line tools.
I'd be interested in hearing more about how you built the search. I keep my own personal cookbook online with a search and I'm curious how others implement theirs. For me, after getting tired of the slow SQL text search queries, I made a search index of 3-grams using the title and ingredients text and that's worked great for ~100 recipes, and also has the benefit of being fuzzy. But I don't know much about alternativ…
Hi there - unfortunately, I use a slow SQL text query + ajax to display results below search bar. I have a small database so it's fine for now, but expect I'll need an alternative method as it grows.
Earlier quoted context omitted.
Thanks for the tip! Wasn't sure where the DOM was lagging. For your question, if you register an account, you can't post a recipe unless you upgrade to a premium account. I'm not expecting anyone to actually pay for this feature, I just put it up to prevent anyone from spamming images. Every user is able to comment on recipe pages though.
You can also use the `defer` attribute on script and put it in inside ` `.
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 distancehttps://www.justtherecipe.com
https://www.justtherecipe.com
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 subscri…
* Make sure your navigation is consistent. The left filter links and the about/contact links are missing on many pages. A breadcrumb would help as well.
* The horizontal tabs on the recipe pages aren't really useful, I'd display all content at once. No need to force the users to click several times. Even on smaller viewports it's easier to just scroll.