Templates
A template is what a project’s new devlogs start from: the sections written every time, a heading, a sign-off. Each project can have one.
Making one
Right-click a project and choose New template. It appears as Template, pinned near the top of the project, and opens, write it like any devlog. To stop using it, right-click it and move it to the trash. Devlogs already made from it keep their text.
Naming new devlogs
A template can begin with a name pattern, between two --- lines, with {n} where each number goes:
---
name: Week {n}
---
With a pattern, the + beside the project (or Ctrl+N) fills in the next name, already selected: Enter takes it, typing replaces it. The next number follows the highest one so far, wherever it sits in the library, and never repeats a name you already have.
| Pattern | Devlogs so far | Next |
|---|---|---|
Week {n} | Week 06, Week 07 | Week 08 |
0.{n} | 0.3, 0.9, 0.10 | 0.11 |
Update v0.2.{n} | Update v0.2.3 | Update v0.2.4 |
Devlog #{n} | none yet | Devlog #1 |
Leading zeros are kept (Week 07, then Week 08) until the number needs another digit (Week 09, then Week 10). Devlogs whose names don’t fit the pattern are left out of the count.
Several numbers
A pattern can have as many numbers as your names do, which suits version numbers:
---
name: Update v{n}.{n}.{n}
---
Then there’s a next name for each number. The + fills in the one with the last number counted on, and lists the others under it: click one, or press Up and Down to go through them. When a number goes up, the ones after it start over: at 0, or at 1 if your names never use a 0, as episodes don’t. So versions go from v1.1.0 to v1.2.0 and seasons start again at Episode 1, without telling it which.
| Pattern | Devlogs so far | Next names |
|---|---|---|
Update v{n}.{n}.{n} | Update v1.0.1, Update v1.1.0 | Update v1.1.1, Update v1.2.0, Update v2.0.0 |
Season {n} Episode {n} | Season 2 Episode 1 to Episode 5 | Season 2 Episode 6, Season 3 Episode 1 |
Numbers compare one at a time, so v1.10.0 comes after v1.9.3, and the newest is the one the next names count on from.
A new template guesses its pattern from the project’s last devlog, every number of a version included: after “Update v1.1.0” it’s Update v{n}.{n}.{n}. Change it as you like, or delete the --- lines, and the pattern with them, to type every name yourself.
What gets filled in
When a devlog is made from the template, these are replaced in its text:
| Write | Becomes |
|---|---|
{name} | the new devlog’s name, like Week 08 |
{project} | the project’s name, like Rocket Rovers |
{date} | the day it’s made, like 2026-10-18 |
{previous} | the devlog before it, like Week 07 |
With a pattern, {previous} is the devlog with the highest number; without one, it’s the last in the library. Anything else in braces is left as it is, and the pattern lines never reach the devlog.
An example
---
name: Week {n}
---
# {project}: {name}
*{date}*
## What's new since {previous}
-
## Next week
-
The template’s own preview shows it as its devlogs will start, without the pattern, braces and all.
Good to know
Changing the template only affects devlogs made afterwards. The template isn’t a devlog itself: it can’t be copied to itch, renamed or dragged. A devlog imported from itch brings its own text, so the template isn’t used for it. And it’s a file like the others, _template.md in the project’s folder.