Editorial Team
Articles publish under a collective byline — "tinyctl Editorial" — rather than individual author names.
This is the convention used by The Economist, by Wirecutter for category guides, and by trade publications in software, finance, and engineering. A collective byline tells the reader that the publication takes responsibility for the article rather than treating it as one person's opinion piece.
The legally-responsible operator of the site is named in the Impressum, as required by German publication law.
The path from topic to publish
Topics come from a list of search queries where the existing results are weak — either thin, outdated, or written for a use case different from the one the searcher likely has. We don't write into categories that are saturated by Wirecutter, G2, or NerdWallet; we wouldn't add anything.
Drafting works from primary sources. Vendor pricing pages are checked at the time of writing, not paraphrased from a third-party blog. For regulatory content (CSRD, GDPR, EU AI Act, German tax law) the source is the statutory text or the issuing agency's published guidance. For open-source tools the source is the GitHub repository, the license file, and the maintainer list.
Drafts go through review against the standards on the Editorial Standards page. The minimum bar: would we ship this and stand by it if a vendor whose product got a critical paragraph forwarded it to us with a complaint? If the answer involves "well, we could probably defend it," the draft doesn't ship.
After publish, articles get refreshed when something material changes. Pricing changes, product acquisitions, regulatory updates, and significant feature additions are the common triggers. The updatedDate field on the article footer reflects the most recent refresh.
Corrections
Mistakes get fixed. Email hi@tinyctl.dev with the article URL and a description of what's wrong; confirmed corrections on articles getting meaningful traffic are applied within a week. A correction note dated to the day of the change goes at the bottom of the affected article. We don't silently rewrite history — if we change a verdict, the change is acknowledged in the article.
Why a collective byline rather than individual authors
An individual byline implies the named person is the subject-matter authority on the article's topic. For a publication that covers CMMS software in week one, observability in week two, and CSRD compliance in week three, an individual byline would either require fabricating expertise or maintaining a roster of credentialed contributors who actually have it in each area. Neither is what we are.
A collective byline is the more honest representation: the article is the publication's verdict against its documented methodology, not an individual's opinion piece.
Contact
Editorial inquiries, corrections, source pointers, press requests, topic suggestions — all go to hi@tinyctl.dev.
For legal notices see Impressum. Privacy practices are at Datenschutz.