Key facts
| Sector | Media / publishing |
|---|---|
| Type | WordPress media property |
| Market | International, English-language |
| What ruxox delivered | Information architecture, theme and templates, editorial workflow, performance and hosting setup, launch |
| Status | Live in production |
The brief
A media property lives or dies on its publishing rhythm. The brief for Dweetle was a platform that could publish curated news and trends across several sections every day without the site slowing down, the layout breaking, or an editor needing a developer to post. It needed to look like a publication, not a blog, and it needed to be operable by non-technical staff from day one.
What we built
| Element | Detail |
|---|---|
| Sections | Top stories, technology, sports and jobs as organised categories with their own landing pages |
| Editorial layout | Reader-first article pages: clear hierarchy, source attribution, related stories, no clutter |
| Curation model | Stories curated from and attributed to their original outlets, presented in a consistent house format |
| Publishing workflow | Editors post from the WordPress admin with templates that enforce the layout |
The visible result is a clean, fast-scanning front page and section pages that behave like a newspaper's, with article templates that keep every story consistent regardless of who published it.
How it is built
WordPress was the right choice here, and it is worth saying why, because we build custom platforms far more often. A media site's core requirements — a mature editorial admin, categories and taxonomies, scheduling, user roles, and a plugin ecosystem for the unglamorous parts — are exactly what WordPress has spent two decades getting right. Building those from scratch would have cost more and delivered less. Our work was the theme, the templates, the information architecture and the performance and hosting setup that keep a content-heavy site fast.
That decision is the same build-versus-buy judgement we apply to every project: use the platform where the platform is genuinely better, and build custom only where it differentiates.
What this shows
Dweetle shows that choosing the right foundation is part of the engineering. A custom-built CMS would have been a worse product for this brief; a well-built WordPress property with a disciplined information architecture was the better answer, and it runs in production today.
Where this fits
This is a custom software development engagement, and a build of this scope sits in our Product Build tier — see straightforward pricing for what each tier includes and the fixed-price bands. Every engagement starts with a written scope that names the riskiest part of the build, delivered within 48 hours of your brief.