Editorial Policy
Last updated: 5 August 2026
Why we publish
The articles document recurring operational problems and how to reason about them. The builds exist so the claims can be inspected. We write to help the reader understand a problem, not to occupy search space.
Who writes it
Jonas Andersson is the sole author of the current library. Every article carries his byline and links to his author page. If Johan Vartanian publishes, his own byline and profile will appear on those pieces. We do not publish anonymous or ghost-written content.
How it is produced
Every article is based on first-hand work. It shows its reasoning, names the tools and systems involved rather than gesturing at them, and states the limitations and the cases where an approach does not apply.
AI assistance
Where AI assists with drafting, a person fact-checks and reviews the article before it is published. We disclose AI assistance where a reader would reasonably expect it. The judgement, the verification, and the responsibility stay human.
Dates and freshness
Published and updated dates reflect real changes. We do not change dates to make a page look fresh. An updated date means the substance actually changed: new findings, revised recommendations, or updated examples.
Corrections
If something here is wrong, tell us at [email protected]. We will correct it and note the change where it matters.
Evidence boundary
Concept builds are labelled as concept builds, never as client work. Earlier results from Viking Web Development are described as a shared prior venture, not as Mannvit client outcomes. Private client work stays private.