The Miraheze Cookbook:Policy

From The Miraheze Cookbook


The Miraheze Cookbook:Policy

This is a policy that contributors are encouraged to follow the policy.

In a nutshell

  1. Don't vandalise, spam or blank articles.
  2. Don't create off-topic content.
  3. Don't harass or troll other users.
  4. Follow the naming standards.
  5. Follow the Manual of Style.
  6. Use the appopriate namespaces.


The articles must be in the appopriate namespaces.



The de-facto naming convention for all recipe pages is title case.


Recipes should be named according to their traditional name, their origin, or their ingredients. Avoid naming recipes for people, unless it is a well-known recipe by that name.

Recipes with a non-English name that have a common English name should be named with their common English name. For example, the primary name for Khaeng Keaw Wan should be Thai Green Curry. If necessary or desired a redirect from the name in the original language can be created. In cases where the non-English name is the common name, that name should be used, as in Huevos Rancheros.

Recipes names with special characters (diacritics, etc) should be primarily spelled with simple ASCII characters and a redirect should be created with the special characters included.

Special Diets

Recipes for a special diet which are substantially adjusted variations of a normal recipe should be denoted by the diet name in parentheses after the name of the recipe. A vegan variation of Chili would be Chili (Vegan); a gluten-free variation of Brownie would be Brownies (Gluten-Free); a lactose-free variation of Milkshake would be Milkshake (Lactose-Free). Recipes that adhere to a special diet, but are not variations for that specific diet should not be named in this fashion; instead only the appropriate category should be added. Trivial variations should be listed on the recipe page itself.

Duplicate Recipes and Disambiguation Pages

When there is more than one recipe for a single type of food, there are several ways to resolve the situation:

  1. If one recipe is of poor quality, delete it.
  2. If one recipe can be expressed as a variation upon the other, include it in the variations section and delete the original.
  3. If the recipes can be merged into a single recipe, merge them and delete the originals.
  4. Create a disambiguation page for the 'abstract' type of food (using the {{cookdp}} template as a header) and give each recipe a unique name.

In the last case, the distinguishing name should be as descriptive of the unique qualities of the recipe as possible. This may be accomplished in the following ways:

  1. Variations: for example, a disambiguation page is Lasagne which links to Traditional Lasagne, Ricotta Lasagne, and Lasagne with Bean Sauce.
  2. Roman numerals: If there is not an appropriately descriptive way to distinguish the recipes, roman numerals should be used, as in Hummus I.
  3. Diet: if a recipe difference is noted by diet, include these in parenthesis e.g. Chocolate Mousse Cake (Vegan)
  4. Author: if a recipe is from a specific author (e.g. from a book in the public domain), include their surname e.g. Common Sauce (Hartshorne).

Additionally, a disambiguation page may be created with more information about a type of food, and this page should link to the various recipes for that dish. See, for example, Chocolate Chip Cookies.


Categories are not entirely standardized, but these generally seem to be in the "normal" wikipedia form of capitalized first letter, lowercased first letter elsewhere (except with proper nouns).

For recipe categorization by ingredient, origin, diet, meal type, and recipe type classifications there is a tendency to use the "___ recipes" format e.g.:

For ingredient categorization, a plural form is generally used, e.g.:

Categories are added automatically via uaerboxes.


You can only copy recipes from public domain or content licensed under CC BY-SA license. If copying from content licensed under CC BY-SA, provide a link to the source. Wikibooks, and Recipes Wiki on Fandom, are CC BY-SA wikis. Don't confuse CC BY-SA with CC BY-NC-SA (used in wikiHow): content licensed under the latter license are not to be used commerically and therefore cannot be copied to The Miraheze Cookbook.

You cannot copy copyrighted or AI-generated content directly without permission. However, you can always use the same ingredients and procedure (but in your own words!) from copyrighted or AI-generated sources; remember to source them.

All cookbooks from March 1929 or earlier are in public domain under the US copyright law.


You can upload images of recipes or step-by-step images through either Miraheze Commons or Wikimedia Commons. You can then add to description or the steps.

Manual of Style

The following structure of the recipe should be as follows below. See also: The Miraheze Cookbook:Sample Recipe.

{{Recipe template
|description= <Enter a description here>
|ingredients= <Enter ingredients>
* 1 cup (250 g; 8.8 oz) ingredient 1
* 1 tablespoon ingredient 2
* etc.
|equipment= <Enter equipment here>
* Equipment 1
* Equipment 2
* etc.
|procedure= <Enter a list of steps>
# Step 1
# Step 2
#* Substep 1
# Step 3
# etc.
|notes= <Enter notes, tips and variations here>
* Note 1
* Tip 1
* Variation 1
* etc.
|warnings= <Enter warnings here>
* Warning 1
* Warning 2
* etc.
|nutrition= <(optional) Enter the nutrition facts label here. The calories and daily value percentages are calculated automatically. Here below is a sample nutrition label.>
|servings      =4
|servingsize   =1/4 of recipe (425g)
|fat           =29  <in grams (g)>
|saturatedfat  =5   <in grams (g)>
|cholesterol   =120 <in milligrams (mg)>
|sodium        =780 <in milligrams (mg)>
|carbohydrate  =98  <in grams (g)>
|fiber         =11  <in grams (g)>
|sugars        =8   <in grams (g)>
|addedsugars   =3   <in grams (g)>
|protein       =29  <in grams (g)>
|vitanimd      =30  <in % daily value>
|calcium       =10  <in % daily value>
|iron          =10  <in % daily value>
|potassium     =10  <in % daily value>
|ref=yes <yes or no for references>


Users are encouraged to post appopriate feedback to the recipes. Recipes can be improved with feedback.

Dos and don'ts

  • Do post appopriate content.
  • Don't post gibberish, spam, promotional or disruptive content.