Technical accuracy first
Every claim is checked against primary sources — datasheets, RFCs, peer-reviewed papers, or the working engineers who do the job. We publish corrections openly and timestamp them on the page.
Reviewed by SMEs
About Gamelton
A workshop where code meets the factory floor.
We are an independent editorial and engineering team documenting the craft of modern software and modern manufacturing — with the same standard of precision for both.
Our story
Built by engineers who got tired of bad writing about engineering.
Gamelton started in a small co-working space in 2019, between two engineers — one shipping gameplay systems, the other writing SCADA logic for a CNC shop. We kept sharing the same complaint: most online writing about our work was either surface-level marketing or impenetrable jargon. We wanted a single place to read thoughtful, technically accurate pieces about the things we actually built.
Today, Gamelton is a small editorial collective covering game development and discrete manufacturing side by side. We commission original long-form pieces, hands-on technical guides, and on-the-floor reporting from working shops and studios. Every article is reviewed by a subject-matter expert before publication. We do not publish press releases, and we do not run sponsored content disguised as editorial.
"Two workshops, one editorial standard."
Founded by Marcus Halloway & Priya Suresh
Mission & values
Three commitments behind every piece we publish.
Editorial discipline is our operating system. These are the principles we hold ourselves to — for the writers, the editors, and the engineers who review the work.
Editorial independence
No sponsored articles, no paid placements, no affiliate links disguised as recommendations. If a vendor gives us hardware to test, we say so on the page and the review stands regardless.
Reader-fundedClarity over jargon
We write for working professionals, not for SEO. If a term needs explaining, we explain it on the page — and we avoid filler that pads an article to hit a word count. If a piece is 600 words and complete, it ships at 600.
No fluff policy
By the numbers
Five years of slow, careful publishing.
We grow by the depth of our archive, not the volume of our output. The numbers below reflect what the team has shipped since 2019.
312
Original articles published
Long-form guides, field reports, and case studies — every one editor-reviewed.
48
Contributing writers & engineers
Practitioners from studios, fabs, and independent workshops across 11 countries.
96%
Articles with subject-matter review
Every technical piece is signed off by an independent expert before publication.
0
Sponsored editorial pieces
Our editorial calendar is set by the editors, not by partners. We intend to keep it that way.
Contributors
The editors and engineers behind the byline.
A small core team, supported by a rotating bench of working practitioners who write what they know. Here are the people you'll see most often on the masthead.
Marcus Halloway
Co-founder · Editorial director
Former gameplay engineer at a mid-size studio in Stockholm, now full-time editor. Covers engine architecture, real-time rendering, and the messy parts of shipping software to real people.
Priya Suresh
Co-founder · Manufacturing lead
Mechatronics engineer turned shop-floor reporter. Writes about CNC programming, lean process design, and the human side of running a small-batch manufacturing business.
Daniyar Kovács
Senior contributing editor
Twelve years writing technical documentation for AAA studios before joining Gamelton. Specializes in the intersection of developer tooling, CI pipelines, and the people who keep them running.
Elena Okonkwo
Field editor · Manufacturing
Mechanical engineer by training, now embedded with small-batch fabricators across the US and West Africa. Her reporting focuses on tooling selection, shop economics, and apprenticeships.