Show HN: Recipe search engine, built in vanilla PHP

1) Summary = RecipeHunt(http://recipehunt.app) is a Recipe Search Engine that gives you the only 3 things that matter in my opinion: (a) Picture, (b) Ingredients, (c) Directions

2) Problem = Every recipe site is bloated(e.g. full of ads, long backstory). I just want to see 3 things: Picture, Ingredients, Directions.

3) Solution = Built a simple Recipe Search Engine that gives you only those 3 things.

4) Tech Stack = Vanilla HTML, CSS, Javascript, PHP, SQL (some JQuery). Frameworks are too complicated for me, so I just wanted to build with what I know.

5) Design

-Main Feed = Similar to Instagram Explore (Square Shaped Thumbnails).

-Categories = Filter by "Country" or "Dish Type".

-Search Bar = Quickly go directly to a Recipe or Category.

-Recipe Page = Gives you only 1 Picture + Ingredients + Directions + Comments. Separated by tabs (I don't like scrolling).

-Paywall(for Spam) = I put up a paywall to prevent spamming (Stripe).

6) Content(Recipes) = I manually put in some initial recipes (posted a few for each Country/Dish Type). Challenge is to fill the site with enough recipes to make it useful. May look into Recipe API's and make sure I'm not violating any terms (give source credit in recipe page).

7) Conclusion = Just wanted to share this because I think it will solve my own problem (making it less painful to search recipes). Still a work in progress, but hopefully it may be useful to someone else as well.

Will happily welcome any feedback! Thanks!

-nsemikey

Show HN: Recipe search engine, built in vanilla PHP
recipehunt.app

Recipe search engines are fast becoming the new todo list. And each one seems to forget that the recipe wiki is right there with an API and four to five figures of structured data content, and so it becomes this futile exercise in CRUD and UI.

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.

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 alternative methods that are still simple to implement from scratch.

you have two forgot password pages?

https://recipehunt.app/forgotpw and https://recipehunt.app/forgotpw2