The brief

Build a credible niche publication that can earn trust before it earns scale. The product needed to make cross-border financial and relocation topics understandable, while keeping the underlying publishing process repeatable enough to operate week after week.

The hard part was not putting a logo on a homepage. It was creating the connective tissue: a content model, an editorial voice, a research workflow, reusable page surfaces, image coverage, and verification checks that expose gaps instead of hiding them.

What shipped

  • Structured content in Strapi rather than a pile of hand-edited pages
  • A Next.js frontend with category, article, author, policy, and sitemap surfaces
  • Editorial and affiliate-disclosure boundaries visible to the reader
  • Repeatable research, drafting, asset, and freshness checks instead of one-off publishing
  • A public proof surface that can be inspected by a reader or hiring team

The operating loop

  1. Research: turn a reader problem into a bounded, evidence-led brief.
  2. Structure: store the brief and article in the CMS so the content is queryable and reusable.
  3. Publish: render the article, category, author, and discovery surfaces through the frontend.
  4. Audit: check links, metadata, image coverage, sourcing, and reader-facing policy disclosures.
  5. Refresh: treat freshness as an operating task, not a vague promise in the footer.

What the audit changed

The October snapshot found strong technical coverage: all 47 article-like URLs had card and Open Graph assets. It also exposed content-system debt: 44 of 47 pages repeated the same “Picture this” opening pattern, and only 17 of 47 pages surfaced a visible sources section. That distinction is the point of the audit — a product can be operational while still showing exactly where the next quality pass belongs.

Why this is an employer-facing project

Nomadomics demonstrates product thinking across the full loop: I translated an audience problem into an information architecture, connected structured data to a public interface, designed a repeatable editorial workflow, and used an audit to prioritize the next improvements. The result is both a visible product and a maintainable system behind it.