This is a simple cooking website where users can submit recipes here for credit. There are no ads, trackers, cookies (unless recipes thereof) or javascript.
- By adding a recipe.
- Make a recipe and take a nice picture of it if no nice picture already
exists. Submitted images should be small
.webp
files ideally less than 100K or so. - Fix errors in recipes or add minor improvements.
- Model submission files after example.md. Put them in
src/
. - Recipes should start with a title, the first
h1
header (line starting with a single#
) of the document becomes the title. The file should to be\n
terminated in linux-fashion (if you're on linux you don't need to care, it should be automatic). - File names should be the name of the dish with words separated by hyphens
(
-
). Not underscores, and definitely not spaces. - Recipe must be based, i.e. good traditional and substantial food. Nothing ironic, meme-tier hyper-sugary, meat-substitute, etc.
- Don't include salt and pepper and other ubiquitous things in the ingredients list.
If you fail to do these things, I will close your submission and you will have to resubmit. I am tired of having to fix more than 50% of submissions.
If your recipe requires use of specific units, ideally you should provide
both imperial (US customary) and metric units. This may be accomplished
with a syntax facility, where the quantity is first written in metric, then
in imperial units: {metric,imperial}
.
Example: src/apple-pie.md (based.cooking/apple-pie.html).
Units for quantities in each system should be chosen thoughtfully. Imperial units favour volume measurements, whereas metric favours the measure of mass for solid ingredients. 50 grams of sugar is most appropriately converted to 1/4 cup of sugar. However, such a conversion is non-trivial, as it requires knowledge of the average density of sugar. There are myriad online tools for aid in the conversion between the mass and volume of common ingredients.
A rule of thumb is: grams for solids, and deciliters for liquids in metric; cups, tablespoons, teaspoons and sometimes pounds and ounces (where appropriate) in imperial measurements.
If the recipe does not convert nicely, try scaling the recipe up or down
for nicer quantities. Make sure to indicate this, e.g.: Produces {8,12} cookies.
Favour less text and avoid duplicating text when specifying quantities for each
system. A contrived example of this would be:
{180°C,350°F}
, is the same as {180,350}°{C,F}
.
You can (and should) add tags at the end of your recipe. The syntax is:
;tags: tag1 tag2 tag3
The tag line should be a single line, anywhere in the markdown file. It
must start with exactly ";tags:
", including the Space after the colon.
Add between 1 and 4 tags, prioritize existing tags. As a general guideline, add the country from which the recipe originates if the recipe is representative of said country, using the adjective form (eg. mexican, italian, etc). Tag the main ingredient if it's something slightly special.
List of special, categorical tags to use if relevant:
basic
: for basic recipes that aren't meant to be stand alone but are supposed to be incorporated in another recipe.breakfast
dessert
quick
: for recipes that can be cooked in under ~20 minutes.side
: side dishes such as mash, fries, etc.snack
spread
If your recipe contains no meat or dairy, include the fasting
tag.
If it includes dairy but no milk, incude the cheesefare
tag.
Images are stored in data/pix
.
Each recipe can have a title image at the top and perhaps several instructional images as absolutely necessary.
Do not add stock images you found on the internet. Take a good picture yourself of the actual dish created. If you see a bad or substandard image, you may submit a better one.
Images should be in .webp
format and with as small file size as possible.
If you submit an image for say, chicken-parmesan.md
, it should be added as pix/chicken-parmesan.webp
.
If you would like to add additional directional images,
they should be numbered with two digits like: pix/chicken-parmesan-01.webp
, etc.
The front page, for now, will just be a list of recipes automatically generated
from the content of src
.
As more articles are added, the site will be reorganized, categorized
or will implement server-side scripting or searches.
This is not necessary yet though.
I don't really want images of recipes on the mainpage yet. I'll think about how best to do it to minimize bandwidth if possible.
This website and all its content is in the public domain. By submitting text or images or anything else to this repository, you waive any pretense of ownership to it, although you are welcome and recommended to give yourself credit at the bottom of a submitted page for you adding it (including personal or donation links).