Live data from Hacker News

Opensource.cooking: A simple, bloat-free cooking site

opensource.cooking

21–30 of 169 posts

Re: Opensource.cooking: A simple, bloat-free cooking site

#21

I’ve always wanted to make a GitHub for recipes. You can fork recipes. Submit pull requests. Public and private repositories. Versioning and commit history. Share with friends, Etc.

I have a little pet project from a long time ago that I tried to start with this, it lets me describe recipes like this:

    Recipe|Turkey Stuffing
    I|4 C==French bread hand torn into small pieces (about 1/4 inch pieces)
    I|3/4 C==Butter
    I|3/4 C==Onion (minced)
    I|1 C==Celery
    I|1 Tbsp==Salt (less if bird is butterball or self basting)
    I|pinch==Pepper
    I|2 Tbsp==Sage, thyme, and marjoram mixture
    D|Melt butter in large skillet over low heat
    D|Add onion and celery & spices, stirring often until it all smells great.
    D|Pour 1/3 of the hot mixture over all the bread, then toss, then 1/3 more, toss, then last 1/3 and toss.
From there it can produce a pretty webpage to view the recipe, or produce an ingredient list for shopping (and it has some basic concept of combining shopping lists sanely), and lets me search by ingredient.

I always debate fleshing it out. 99% of the time spent with something like this is curating the recipes themselves, which I'm far from an expert in, and I don't want it to become a big time waster.

Re: Opensource.cooking: A simple, bloat-free cooking site

#22

Tangentially related, but if I were to run for president I'd run on a single issue platform: Imprison anyone involved with the current state of online recipes. Want to write your 10 page life story for baked mac & cheese? Boom, 5 years in the slammer. Want to put 12 different ads on your recipe for baked Alaska Char? 10 year minimum sentence. Involved in encouraging this behavior from the inside of Google? Sorry bub,…

I'd vote for this, this is truly the most pressing issue of our time.

Re: Opensource.cooking: A simple, bloat-free cooking site

#23
Is is the code, formatting, etc, that we're supposed to be looking at? Or the data itself?

The data catches my eye because there seems to be quite a lot of bad data. Recipes with cooking time of 0, when it's clear that's not true. Typos like "Spahetti Carbonara". "Ham Sandwich" tagged as "Fruit".

If we're supposed to ignore all that and just evaluate the CMS bit, it looks fine. But it doesn't seem very specific to cooking. Just tag organized text.

Re: Opensource.cooking: A simple, bloat-free cooking site

#24
Very neat!

I've recently taken a stab at something like this, too – the result is a Pandoc-and-Bash-script-based static site generator for my personal recipe collection. Recipes are written in a format based on Markdown (with ingredients listed separately for each step, which comes in real handy while cooking), and the end result is a lightweight, responsive, searchable website. I've received very positive feedback when I shared it as a "Show HN" a week and a half ago.

It's available as open source here: https://github.com/doersino/nyum

There's also a demo: https://doersino.github.io/nyum/_site/index.html

Finally, here's what the Markdown source for an example recipe looks like: https://raw.githubusercontent.com/doersino/nyum/main/_recipe...

Re: Opensource.cooking: A simple, bloat-free cooking site

#26

Cool! Looks fun. What exactly is open source on the site? Is it the recipes? If so, then what license do they use? Is there any disclaimer of that on submission? I'm not dissing, just making sure your ducks are in a row. It's a fun idea!

Recipes cannot be copyrighted.

The recipe itself can't be, but you can't just copy and paste recipe text from one website to another.

Re: Opensource.cooking: A simple, bloat-free cooking site

#27

Cool! Looks fun. What exactly is open source on the site? Is it the recipes? If so, then what license do they use? Is there any disclaimer of that on submission? I'm not dissing, just making sure your ducks are in a row. It's a fun idea!

Recipes cannot be copyrighted.

Wrong. Lists of ingredients cannot be copyrighted. But the accompanying explanation can be copyrighted if it is substantial enough:

https://www.copyright.gov/help/faq/faq-protect.html

Beyond the recipes themselves, the collection may be copyrighted.

The photos accompanying the recipes are also copyrighted.

Re: Opensource.cooking: A simple, bloat-free cooking site

#30

Tangentially related, but if I were to run for president I'd run on a single issue platform: Imprison anyone involved with the current state of online recipes. Want to write your 10 page life story for baked mac & cheese? Boom, 5 years in the slammer. Want to put 12 different ads on your recipe for baked Alaska Char? 10 year minimum sentence. Involved in encouraging this behavior from the inside of Google? Sorry bub,…

Weirdly recipes aren’t copyrightable..

But personal stories are, And descriptive text is too. Probably why they’re added.

I’ll agree about the ads. Thus we signed up for platejoy (YC 2017?)

Post reply on HN