About Nuriforge
Nuriforge is where I write about building and automating real systems with AI — content platforms, infrastructure, and small apps — and what actually works when you have to run them yourself. It’s a practitioner blog, not a news site: everything here comes from projects I’ve built, broken, and fixed.
Who writes this
I write under the pen name Nuri. I’ve spent 20+ years in IT, mostly as an infrastructure engineer — Linux and containers, private and public cloud, CI/CD, observability, and the kind of Python and shell automation that keeps operations boring in a good way. I’m based in Sydney.
Alongside the day job, I design and ship my own things with AI in the loop: Next.js and Supabase apps on Vercel, a Slack-and-Gemini receipt pipeline, an AI-assisted WordPress content system, and a few smaller tools. Those side projects are where most of the hands-on stories on this site come from.
Why a pen name
I keep my legal name and face off the site on purpose. It isn’t a gimmick — it lets me separate my professional work from what I write here, and keeps the focus on the systems rather than on me. Where a story comes from work I do for an employer, I describe the technique in general terms and reconstruct any examples on throwaway setups, never using real company data, names, or dashboards.
What you’ll find here
- WordPress content operations — running a content site on an AI-assisted pipeline: schema, live editing via the REST API, indexing, and the SEO maintenance loop.
- Infrastructure & automation — turning manual ops into scripts: health checks, CI stages, Slack alerting, and the gotchas that don’t make it into the docs.
- Building apps with AI — shipping real Next.js and Supabase apps solo, from lead-capture widgets to booking systems.
- Running a content business — the build-in-public side: pacing, evidence, and keeping AI-assisted writing honest.
How this content is made
The writing here is AI-assisted and human-reviewed: I research and draft with AI, then I review, correct, and stand behind every published piece. The evidence — screenshots, logs, code, before-and-after numbers — is real. When I don’t have first-hand proof of something, I say so plainly instead of inventing it. If I ever get something wrong, tell me and I’ll fix it.
Get in touch
Questions, corrections, or ideas are welcome — see the Contact page. If a post helped, the best thing you can do is try the thing yourself and let me know what broke.