Hello World
Why We Built Our Blog on Hugo #
We finally launched our blog.
Not because we had to.
Not for SEO.
And definitely not to churn out clickbait.
We launched it because we’ve got things to say — and Hugo felt like the right place to say them.
If you’re curious why we chose Hugo over the dozens of shinier, trendier options out there — here’s the story. It’s not technical. It’s not philosophical. It’s just what made sense for the way we work.
🚀 We Wanted Something Fast — No, Really Fast #
We spend our days designing and shipping products where speed isn’t a “nice to have” — it’s table stakes. If our own blog took ages to load or felt bloated, it would undermine everything we believe about good UX.
Hugo compiles to static HTML. That means:
- No CMS wait times
- No hydration delays
- Just content — instantly available, everywhere
We care a lot about first impressions. Hugo helps us make a good one — fast pages, clean markup, and no performance debt.
✍️ We Don’t Need a CMS to Write #
We don’t think of content as something that needs to be “managed.”
We think of it as an extension of design — another medium we shape.
That means:
- Writing directly in Markdown
- Committing changes via Git
- Reviewing drafts like we do code or design
No dashboard. No login screen. No scheduling tools.
Just one unified workflow. And because everything lives in the same repo, our designers and developers can tweak layouts and styles as they go.
Fewer tools. Fewer moving parts. No overhead.
And no training needed to use our own blog.
🎨 Design Is Part of the Content #
We don’t separate design from writing.
The way something looks, feels, and flows is inseparable from what it says.
With Hugo, we get full control:
- Typography
- Spacing
- Interactivity
- Motion
We can test ideas, embed prototypes, and build new layouts without asking for permission. The blog is a place to try things — some that might never ship, some that might become tools, and some that just help us think.
It’s as much a sketchpad as it is a library.
🧠 We Don’t Do Content Farming #
There’s already enough noise on the internet.
We didn’t want our blog to add to it.
We’re not here to “scale content” or chase keywords.
We’re here to write when we’ve figured something out — or when we’re still figuring it out and want to share what we’ve learned.
Hugo supports that mindset because it gets out of the way.
No pressure to post weekly.
No automated filler.
Just the tools we need to hit publish when it feels right.
This isn’t marketing.
It’s reflection.
Documentation.
Sometimes inspiration.
But always real.
🛠 It’s Overkill for Most — Perfect for Us #
We wouldn’t recommend Hugo to everyone.
Most of our clients would probably hate it.
It’s not made for content teams who want to collaborate in-browser or schedule posts via a UI.
But for us — a design studio that:
- Likes full control
- Builds and prototypes a lot
- Treats writing as part of the build process
…it’s perfect.
Why Hugo Works for Us: #
- ✅ Markdown-native
- ⚡ Lightning fast
- 🔓 No vendor lock-in
- 🎨 100% designable and ownable
That’s more than enough.
🧾 What We’ll Write About Here #
This blog isn’t a marketing tool.
It’s a place for us to think in public.
Sometimes we’ll share:
- Design teardowns
- Behind-the-scenes looks at tools we’ve built
- Weird UI patterns we’ve noticed
- Thoughts we can’t shake
No publishing calendar. No pressure.
Just whatever’s interesting — to us, and maybe to you.
🔗 Stay in the Loop #
If that sounds like your kind of thing, you know where to find us.
DNSK WORK
Design studio for digital products
🌐 dnsk.work