D 2021-03-22T06:16:02.586
L improve
N text/x-markdown
U mario
W 1782
### Improve your cookiecutters.json
cookiedough accepts some additional fields from `cookiecutters.json`. This
helps both the parameter input, as well as grouping, search and scoring/sosrting
of entries.
Currently following options are recognized:
| Where | Name | Usage |
|-------|------|-------|
| `cookiecutters.json` | `_api` | Override the category/language (could be an app name, e.g. `flask`) |
| `cookiecutters.json` | `_keywords` | Add extra search keywords/tags (comma/space-separated string) |
| `cookiecutters.json` | `_requirements` | Build dependencies (JSON list) |
| `README.*` | markdown | Describe template variables, using a "❙`varname`❙Explanation...❙" table |
For example:
{
"project_slug": "base-name",
"_api": "django",
"_keywords": "make-whl, xdg, pytest, mkdocs",
"_requirements": ["poetry", "pep517"]
}
Whereas your README should contain explanations for template vars:
| Variable | Explanation ... |
|----------------|----------------------------------------|
| `project_slug` | basename for created project directory |
| `proj_license` | ... |
### Why "scoring"?
Ordering just alphabetically or by github stars isn't all that useful. Stars
are simply accrued for older projects. It's often just bandwagon voting even.
Instead cookiedough takes multiple properties into account, and somewhat
weighs them against each other. Average projects are favoured, and some
contents rewarded. It's not a huge influence, but hopefully brings more
contemporary templates to the top.
See [cookiedough/update.py](file/cookiedough/update.py)
on how the default scoring works.
Z 26785fba40b814cfe0c184382752455f