Working conventions
For anyone working on this repository, human or assistant. Read this before making a commit or editing a post.
Commit messages
Do not append an attribution trailer of any kind. No Co-Authored-By: line naming a model or a tool, no “Generated with” line, no marker of which assistant helped. The message ends at its last paragraph.
Thirty such trailers were removed from the history on 2026-08-31 by rewriting every commit message. Reintroducing them means doing that work again, so do not.
The author is albay <albayrakkazim@gmail.com> and stays that way. Help with a commit does not change who owns it.
Write the subject as a sentence saying what changed, not a category prefix. The existing history is the guide.
A commit-msg hook on the author’s machine strips such trailers and says so on stderr. Hooks are not cloned, so it enforces nothing anywhere else. On any other machine this paragraph is the only thing standing between the rule and a commit.
Language
Everything in this repository is in English: post text, code, code comments, configuration comments, file names, folder names, commit messages. The one exception is the author’s own name, which keeps its Turkish spelling.
Conversation about the work can be in any language. What lands in a file cannot.
Prose in posts
- No em dashes. Rework the sentence or use a comma, a colon or a full stop
- No Oxford comma
- Impersonal register. No first person and no second person, except inside a direct quotation. Imperative is fine in numbered steps
- Full sentences with a subject and a finite verb
- Describe the mechanism in the present tense rather than reporting what was done
A longer set of preferences, with examples, is kept outside git in _notes/reference/writing-preferences.md. That file is on the author’s machine only, so treat the rules above as the portable ones.
Colour and styling
Never write a colour value into a post or a page. The site has a light theme and a dark one, and a fixed colour follows neither. Styling belongs in styles.css or in the theme files, keyed to a variable each theme defines.
Categories
Post categories are two axes in one flat list: exactly one subject, plus any number of tools. No slashes and no parent labels, because the category panel has no hierarchy and prints whatever string it is given. The full scheme is recorded in _notes/reference/category-scheme.md, also outside git.