About
About Restato Labs
Restato Labs is the publisher of this engineering blog. This page states who publishes it, what its editorial scope is, and how to reach us.
Who publishes this blog
This site is published by Restato Labs, an independent software engineering practice. Articles are published under the Restato Labs name rather than under individual bylines, and Restato Labs is responsible for everything on this site.
The only address this blog is published at is https://blog.restatolabs.com/, and the only contact address is [email protected].
Editorial scope
The scope of this blog is deliberately narrow:
- Build, deployment and hosting pipelines for static and content-driven sites.
- Content modelling, routing and internationalisation in real projects.
- Developer tooling, command-line workflows and automation we run day to day.
- Working practices for AI-assisted development, including where they fail.
- Migration and incident write-ups, with what we measured and what we changed.
An article rests on one of two kinds of evidence, and says which. Either it reports first-party work — a build we ran, a deployment we made, an incident we handled — or it is a careful synthesis of current primary sources such as official documentation, a specification, a changelog or source code, read and checked by us rather than summarised from someone else's summary.
Articles are published in English and, where a translation is warranted, in Korean. Each language is reviewed on its own.
What we do not publish
- Sponsored articles, paid placements and paid links.
- Vendor press material reprinted as editorial content.
- Articles generated by a language model and published without human review.
- Repetitive variations of an article we have already published.
How we work
Some drafting, translation and code scaffolding is done with AI assistance. A person verifies the facts, commands and code before anything is published, and Restato Labs remains responsible for the result. Our editorial policy describes the review, the corrections process and how we handle sources.
Every article shows its publication date and a maintenance status, so you can tell whether it is still being kept current or kept as a historical record.
Contact
Corrections, reuse requests and privacy questions all go to [email protected]. See the contact page for what to include.