api VS sserver

Thank you for the response!

> support splitting ingredients by typing a comma

That sounds sensible, yep; filed as https://github.com/openculinary/frontend/issues/210

> "Are there any ingredients that are not available?" ... I knew what you meant, the search will exclude recipes with those items, but it felt weird to read

That makes sense too. If I remember correctly, that prompt was most-recently rephrased during a pandemic-related lockdown (with subsequent unpredictable ingredient shortages), and so that context may have affected the choice of language; but I agree that it's odd phrasing and should be updated.

Hopefully that'll be a relatively quick correction, although it will require internationalization (currently machine-translated without review by native language speakers, not ideal); it's filed as https://github.com/openculinary/internationalization/issues/...

> box around the search form has a huge gap to the right of the form inputs

> I'd probably expect to see filters for vegan/veggie/pescatarian / low gi etc but then maybe not

Two good points here, and possibly combinable. Perhaps those dietary recipe filters could be placed in the excess space available next to the search controls.

Today the search API does theoretically support filtering[2] on a few dietary properties -- but that functionality isn't yet visible and available to the user.

Feature request filed as https://github.com/openculinary/frontend/issues/211

- Shopping list feature ... your icons seem too small and fiddly, and I'd want a few buttons on screen of common things - so I can tap those instead of typing

That sounds smart. This feature (and the meal planner) are under-attended relative to the recipe search/explore components, in my opinion. Let me think about this for a while, there are a few considerations and I'd like to be concise.

[2] - https://github.com/openculinary/api/blob/72075f66cd6fda5b809...

Thanks for sharing this!

https://www.reciperadar.com/ does (potentially, as per the notes on the page) pass.

To provide further assurances to users, all of the code[1] to run the service is made available to the public, including logging/analytics functionality[2].

It's (currently?) hard to guarantee to end users that there aren't any other tricks going on, and to match the version running in production (on a single computer in my office room) to the relevant git commit, but the goal is to incrementally move in the direction of additional (verifiable) transparency for the service.

[1] - https://github.com/openculinary/

[2] - https://github.com/openculinary/api/blob/24ac611b1c14b754f23...

did not abandoned it since i am using for myself but didn't put any effort into marketing either other than mentioning it on hn few times https://github.com/newbeelearn/sserver . It's hHeadless server for hosting courses and associated blog/static content from private github repository.

I am working on creating a hosting server that can cater to landing page+blog+selling digital content with minimal maintenance overhead.

Beta version is ready here https://github.com/newbeelearn/sserver

I am looking for following

working on adding e-commerce functionality to my simple hosting server https://newbeelearn.github.io/sserver/

if you want to self host, give my product a try https://github.com/newbeelearn/sserver. It will auto-sync your static site from git repo.

I built something that will take care of the publish part but not the static site generation part here https://github.com/newbeelearn/sserver. Right now it only has one user i.e. me :-)

./sserver -token "$GITHUB_AUTH" -repo "https://github.com/newbeelearn/sserver.git?ref=gh-pages"

My plan is to add e-commerce functionality to it so that users can sell digital content i.e. books/videos/courses etc. through single config file in their github repository where the content is stored without needing to change their workflow.

If you would like any specific feature please let me know in the comments or create issue in the repository. Looking forward for your feedback.