Novemade
Services

The site you are reading is the portfolio piece.

Built on Next.js, served in eight languages, with every claim on it checked against the software it describes, a content-security policy with no wildcard, and no third-party script except opt-in analytics. View the source of this page and the evidence for the sentence you just read is in it.

What people arrive with

The problems that bring somebody here.

The site is slow and nobody knows which part

Usually it is images nobody resized and scripts nobody can remove. Both are fixable, and both get worse every month they are left, because the tags accumulate and the person who added each one has moved on.

Editing the site is worse than building it was

A page that takes a developer to change does not get changed. The answer is not always a content management system - sometimes it is content in typed files with a check that fails when a page is missing a title, which is how this site works.

The second language was bolted on

Translated navigation above an English page, a language switcher that loses your place, metadata that stays English in every language, missing hreflang. Each of those is invisible on screen and perfectly visible to a search engine.

What the work includes

Including the parts nobody puts on a services page.

Scope is where a project is decided, so this list is specific rather than reassuring.

  • Next.js, rendered on the server

    Pages that arrive as HTML, so they are indexable, fast on a phone, and readable without JavaScript. Interactivity is added where it earns its weight rather than applied to the whole page.

  • Performance as a budget

    Images generated at the sizes they are served in, in modern formats, with width and height declared so nothing shifts as it loads. Self-hosted fonts, so there is no render-blocking request to anybody else.

  • Technical SEO, built in rather than audited later

    A unique title, description and canonical on every route, the language set declared in the head and in the sitemap, structured data that matches what the page visibly says, and a build that fails when an internal link is broken. Search-engine-friendly is a property we can hand over; a position in a ranking is not ours to promise.

  • Multiple languages, counted not declared

    This site knows which of its eight languages are complete by counting the translation files, section by section. A page whose language is unfinished renders in English and says so, because translated navigation above English prose is a lie a visitor cannot detect.

  • Accessibility and both themes

    Contrast ratios asserted by a test rather than eyeballed, a skip link, keyboard-reachable dialogs with focus returned, and reduced-motion honoured. Light and dark, because a site that only works in one is half-built.

  • Security headers that are actually strict

    A content-security policy with no wildcard escape hatch, HSTS, nosniff, a referrer policy, and no framing. Adding a third-party script has to be an explicit decision, which is the point.

How it runs

The same loop our own products go round.

Not a process diagram written for this page. It is the production loop the studio already runs, which is why it has a measure step and a human gate in it.

  1. 01ResearchSignals and a per-product idea bank, scored for relevance before anything is made.
  2. 02DesignThe product decides its own voice, claims and boundaries. The system fills them in.
  3. 03BuildAssets, narration and captions assembled from each product’s own material.
  4. 04LocaliseEvery string in every language, with parity between catalogues checked rather than assumed.
  5. 05TestAutomated gates, then a person. Nothing reaches a queue unreviewed.
  6. 06PublishPer-platform packaging, with publishing deliberately held behind human approval.
  7. 07MeasureRelease and performance signals return to where the work was made.
  8. 08LearnWhat worked on one product is readable by the next one that asks.
  9. 09ImproveThe fix lands in the shared system, not in one product’s copy of it.

Evidence

Our own products, not a client list.

Everything shown as evidence on these pages is a NOVEMADE product - our idea, our money, our name on the listing. There is no client logo wall here, no testimonials and no case-study metrics, because there have been no clients to take them from. What there is instead is software you can open.

Pivumo

Learning

LIVE

1002 early-learning activities for two- to six-year-olds, voiced in 29 languages.

iOS · AndroidTry it
Pivumo — animal Forest and its activities (Turkish)

Didi

App

LIVE

A shared household record of what got done, by whom, and when.

iOS · AndroidTry it
Didi — the household timeline — what was done, by whom, and when

Goes further

A browser demo for every product, and a four-rung ladder to keep it honest

Eleven products, eleven demos, and the uncomfortable part: two of them run the product’s own source, and saying which two is the whole point.

Read the case study

Where this stops

What we do not do.

We do not promise a search ranking, buy backlinks, or run a link network - a position in somebody else’s index is not a deliverable. We also do not take on template installs or theme customisation; if a template is the right answer for a project, saying so is free.

Collaborate

We are not for hire. We are open to the right partnership.

Publishing, partnerships, investment, or a technical conversation about how we build. Tell us which one and we will skip the rest of the form.