lukesmithxyz / based.cooking Goto Github PK

I know this is off topic, but I felt like I should post it here. I would work on it if you guys think it's a good idea. I'll create a github repo for it. What sites should be added first?

Not sure if there are any other relevant ones but there are a lot of recipes which are vegetarian/vegan right now, and it would be nice to filter for them.

For the sake of linking this on more botnet sites it would help if templates/header.html had some opengraph meta tags for clean looking embeds.

I think most sites use this to generate fancy embedded links so these should be all the tags we would need

<meta property="og:title" content="Based Cooking">
<meta property="og:site_name" content="Based Cooking">
<meta property="og:url" content="based.cooking">
<meta property="og:description" content="Only Based cooking. No ads, no tracking, nothing but based cooking.">
<meta property="og:type" content="article">
<meta property="og:image" content="">

The og:image on just needs a full link to an image so no URI's (/path/to/image.png). I usually just use the project logo from my Gitlab repos to not put any undue load on the server.

Reference to available opengraph tags: https://ogp.me/

Expected Behaviour: Open based.cooking, Find the recipe to open, click on it, recipe page appears, cook it.

Bug: Upon clicking the link/name of the recipe, the recipe hyperlink shrinks instead of opening the webpage. Then a reclick on the same link/name is required to open the webpage.

Tested on:
Device- Poco F1
Browser- Brave
Android Version- Android 11

Something I've noticed with most, if not all recipes, is the lack of serving information. Maybe number of servings, and possibly serving suggestions (although if this is applicable I think people already do this), would be a good additional requirement. I understand that different people prefer different portion sizes, but I think we all have a good idea of a general portion size and how many people a dish could serve.

Hi,

This is exactly the kind of cooking website I'm looking for, but as someone who doesn't eat meat it's a bit cumbersome to sort through the recipes looking for the meat-free dishes. There's already a tags system, so I think tags should be added for common dietary restrictions. That way, folks with particular diets can easily find the foods that fit their diet.

Here are my suggestions for dietary restriction tags:

• Vegetarian
• Vegan
• Nut-free
• Gluten free
• Kosher
• Halal

Thanks for making a great website!

https://github.com/poundifdef/plainoldrecipe

I would suggest to create some template for new recipes that conforms to the Schema/Recipe standard. This is a widely used standard for recipe pages which makes it easily machine parseable. It is also what enables the recipe-scraper mentioned in #31 to work quite consistently on most popular pages.

Implementation wise, it's basically just some extra metadata added to the html tags. I would suggest having a look at the examples at the bottom of the page

hey,

on a low resolution monitor it's kind of hard to read the default serif font.
I would suggest to add
font-family: sans-serif;
to the body or html in order to use the system installed sans-serif for better readability.

I think it would be a good idea to have a light mode, mainly for printing recipes. However, this may be considered "bloat" and will probably require Javascript, but I think that the ability to switch between/disable stylesheets without needing to edit the HTML may be helpful.

Consider adding a section to the readme expressing the importance on using a white light if possible for pictures

Use the CC0 1.0 license instead of the current unofficial license.

This makes the site license official and is an extra defense against a malicious contributor wanting to remove one of their submissions. The current unofficial license may not actually enter works into the public domain in some jurisdictions.

It is also worth clarifying this license as a footer on the site, and everything under /src.

See freedomdefined.org for more libre licenses.

People keep coming up with different formatting/content distribution/search system ideas.

Why not simply offer a simple repo of markdown recipes and put all the site-generation tools in a separate repo?

This would allow to integrate the recipes into whatever system they like the most, while keeping the actual valuable data centralised in a single repository.

It would also make it easier to give some people some commit rights to the recipe repository to improve the flow.

Offering recipes as raw text + bash color codes.

Recipes should look nice in the terminal with curl only (without need for lynx or w3m)

If you agree with me, I can implement that myself and open a PR.

Just give me the green light.

Edit:

No need to create a new endpoint, nginx can return different responses based on the user-agent:

• Normal HTML response if the user-agent is a browser.
• Raw text response (+ bash color codes) if the user-agent is curl/7.x.x.

Hi. I had to come to github to find this sentence:

Recipe must be based, i.e. good traditional and substantial food. Nothing ironic, meme-tier hyper-sugary, meat-substitute, etc.

Ok, that is what "Based cooking" means.

I recommend putting that sentence or something like it into index.html.

Maybe it was missed. Just wanted to bring it to your attention

Add the macronutrients for every dish/ingredient.

Looks like it was originally going to hold submission rules but those seem to all be in the top level README.

If it should remain for whatever purpose, it should probably be added to src/.ssgignore to avoid generating https://based.cooking/README.html

Hey Luke,

Big fan of the project, having this would help more people and people who are learning to cook as well

Let's have a search box, in due time.

It'd be nice if measurements and ingredients would be wrapped in <data> tags to make them more machine-readable.

What for?

• Automatically convert measurement units
• Adding custom styles for these elements (like making them bold)
• Wrapping ingredients in links to an amazon search, or the wikipedia page, or whatever.
• Extract the data to automatically feed it into whatever other app.

Or whatever else people might want to do with this data. My point is that it should be available somehow.

The way I would suggest doing this is:

Add <data class="measurement" data="30 g">a fuckton</data>
of <data class="ingredient" data="Himalayan Salt">Salt</data>.

Are seasoning rubs allowed and if so which of the 3 categories (Recipes, Basics, More Info) would they fall under? They're more for preperation and typically require no cooking at all.

As of right now, the RSS feed is invalid. When I click on it, this is what the page says:

XML Parsing Error: not well-formed
Location: https://based.cooking/rss.xml
Line Number 138, Column 89:
- [![](https://img.shields.io/badge/[email protected]?style=social&logo=GNU-Privacy-Guard)](https://keyoxide.org/0A3D7C5B8C2499A8BEBCE72869D2E5C413569DA2)
----------------------------------------------------------------------------------------^

http://microformats.org/wiki/h-recipe

My grandparents love finding new recipes online and this site is perfect for them because of their terrible internet connection. The only thing lacking for them here is an obvious print button (remember we are talking about literal boomers here, they don't realize they can simply press ctrl-p, nor do they realize they can copy and paste everything into a word document or something). An obvious print button would be quite beneficial for them and anyone else who may end up visiting based.cooking who does not enjoy watching Linux videos in their free time.

Sounds better

Is it only me, but the recipe for Yogurt asks for yogurt as an ingredient? Something doesn't add up, why would I create something if I need it in the first place to create it.

I want a little logo, just for the faveicon for now.

If anyone can think up anything creative, tell me. Otherwise I'll make something up. Should be something based.

If it's a simple design, it should be a native svg.

You know it's not ordered properly right now.

I think it might be done by some Makefile rule or ssg modification instead of manually doing that. Some hipster frontend guy might probably come up with client-based sorting, but screw that.

Most likely related to: #153 #150 #20

There is a fairly major issue with the pasta sauce recipe here:
https://github.com/LukeSmithxyz/based.cooking/blob/master/src/pasta-sauce.md

You've specified the exact species of tomato necessary to make the sauce, but declared garlic as optional.
Garlic is never optional. Ever.

Some people don't like using a centralized website, that has the power to take down any repo for any reason. Therefore I suggest that this repo should be moved to self hosted alternative, Gitea is good but it requires a lot of setup and is still quite bloated, we could also do what suckless do.

Every recipe in the site has a different (or no) system of measure, some use metric and others imperial. It'd be a nice feature to have either different pages to see the recipes in metric or imperial, or some other feature like that (obviously without the use of JavaScript). Or maybe just have them all in metric, whichever works.

# This is a basic workflow to help you get started with Actions

name: CI

# Controls when the action will run. 
on:
  # Triggers the workflow on push or pull request events but only for the main branch
  push:
    branches: [ master ]
    
  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - name: Based Cooking
        uses: appleboy/ssh-action@master
        with:
          host: ${{secrets.HOST}}
          username: ${{ secrets.USERNAME }}
          key: ${{ secrets.KEY }}
          script: |
            git pull
            echo "Another Command"

In the actions tab you can allow github to ssh into your machine and run commands. In Settings > Secrets > Repository Secrets you can create the variables for USERNAME, HOST, KEY, etc.

The only thing you would have to change in the code block above is what comes after git pull with the commands needed for ssg5 to reload.

Please, include a Monero address to donate. Currently there is only a BTC address

Make index.html a literal index, with all recipes listed alphabetically.

Then link to individual sections with the recipes within each section listed alphabetically.

If 50 recipes have you boil spaghetti for example, why not just make a spaghetti recipe and import it into all the other recipes that use it? (Spaghetti is an example, but you get the idea.)

With this you can make a lot of other stuff easier too, like adding ingredients and nutrients automatically by just importing a "sub-recipe" for the desired dish.

There are multiple ways to implement this, so suggestions in how this would be done in the best way possible is appreciated!

"make build" fails with error message:

/bin/sh: 9: Syntax error: "(" unexpected
Makefile:65: recipe for target 'blog/index.html' failed

It would have been polite to mention which version of make and which shell are required.
I have GNU make 4.1 and zsh 5.4.2.

There's a checkbox somewhere in the project settings

First I am a big fan of your content. But just saying the following:

chicken breasts 
tomatoes (San Marzano is best) 
mozzarella cheese
parmesan cheese
bread crumbs
eggs
flour
pasta sauce

That gives lots of room for error, perhaps if you could standardise on ingredients for 2 persons as that way if you are cooking solo you can keep leftovers and its easy to multiply by how many people you need to cook for.

Maybe I am just being a smoothbrain but I know 100% if I try to follow this I will get it wrong, while I know it does not require the amount of an ingredient to count as a "recipe" it would be extremely helpful.

I don't think we should adopt every single one of these, it's more or so a list of groups I could see making the recipes easier to find.
Region (Asian, European, Hispanic/Latin, etc.)
Nation (Italian, Chinese, Mexican, etc.)
Food Category (Poultry, Soups, Breads, Meats, Pastries, etc.)
Cooking Style (Boiled, Grilled, Baked, Steamed, etc.)
I'm not sure what these are called (Breakfast, Lunch, Dinner)
(Main Dish, Side Dish, snacks)
Difficulty/Accessability? (Easy, Medium, Hard)
^ to clarify, food like eggs, spaghetti, and chicken soup are much easier to make, obtain, and require less effort and equipment than say shrimp cocktails, pizza (from scratch), or Scandinavian Coffee Cake (self plug 😏).
I do see this one being the weakest of all the groups listed since the levels of difficulty are more blurred than say Food Category or Nation.

And of course feel free to add on.

based?
based on what?

I believe as soon as the interest in contributing will grow, single level recipe list will be impossible to use. Catalog-like structure would for sure help organizing related stuff. It would also be way better than paging the list of recipes. There could be rules like setting a limit of recipes in a catalog etc.

here is an example that works without js.

https://codepen.io/oahehc/pen/OJPjZXB

Generate Latex files and pdf with link to download it from the index, to have it in a nice printable format or just read it offline.

pandoc can do the job pretty well apparently.

I would even be down for groff versions as well, to read the recipes from the terminal.

Somewhat related to #170 and #158.

Would be great to define the format of how units are specified and have simple pre-processor that does the conversion before publishing.
It is already in half of the recipes but people just specify it by hand, so why not automate it?

You submit a recipe by sending it to [email protected] or something along those lines.

It goes through a format check and automatically bounces back if the format is invalid (missing title, tags, etc).

The administrator can collect and go through the pre-filtered submissions easily, modify and commit them using the name and email of the submitter.

Shouldn't be too hard to do a script to automate all that and it would make it a lot easier for normalfriends/oldfriends who don't want to bother creating a github account and go through a merge process.

Hi, just a tiny suggestion. How about making it possible for people to add translations? Maybe for every recipe.md we have a recipe.<language>.md for each language? Or whatever structure that is more suitable.

This can add a lot of noise, of course, for English speaking users. I'm not sure if that would be considered bloated. But it would help much more people and make others contribute more, I guess.

And nice project btw, this is already so cool.

Hi. I was wondering, can people commit recipes in another language (spanish, for example) ? I know that it would be probably require more maintenance by people that are native in that language, but I guess we could do that, we have a pretty big community interested in this project. We could sort the recipes in another languages by tags or just by adding a whole new directory (the last option would be the ideal).
Thanks.

I'm thinking it might be good to have a feed to notify that a new recipe has been added. Not necessarily a really important addition, but if it's not too much work it would be a nice-to-have.