At a glance

Year
  • 2026
Status
  • Ongoing
Services
Technologies

Why the content model is hard to see: hundreds of files, 1 screen at a time

A content model is the set of building blocks a site's content is made from: the content types you publish, the fields each one holds, the vocabularies and media they use, and the references between them.

Most Drupal work starts from that model:

  • a migration estimate depends on knowing everything that has to move
  • a redesign depends on knowing which fields each template can draw on
  • a developer joining the project needs the map before opening the code
  • a workshop with editors goes better when everyone looks at the same picture

On a built site, the model is spread across a few hundred configuration files, and the admin screens show 1 content type at a time.

See the whole model, then narrow it to the question you have

Nexus(Opens in a new tab/window) reads the same configuration files Drupal(Opens in a new tab/window) does, so the diagram it draws matches the site. Drop a site's exported configuration folder onto the page, and Nexus rebuilds its content types, vocabularies, media, paragraphs and blocks, with their fields, help text, allowed values and every reference between them.

The Umami content model in Nexus: 3 content types, 2 vocabularies, 5 media types, 4 block types and the user, each with its fields and machine names

4 detail levels take the diagram from entities only to every field. Rest the pointer on an entity to light up its connections, or pick Explore from here to keep only the entities within 1 to 5 references of it, which answers "what points at this media type?" in a click.

Exploring from the Recipe content type: only Recipe and the entities it references stay on the canvas

For a project team, that means the conversation about content starts from what the site actually holds.

Catch problems early and see what changed: checks and comparisons

The Checks panel lists what Drupal would reject, such as a reference to a missing entity or 1 field name with 2 types, and what just looks off. It re-checks after every edit, so it works as a running review while a model takes shape.

The Checks panel in Nexus listing warnings in the Umami model, beside the diagram

Compare with sets the open diagram against a saved diagram or another config folder and marks every bundle, field and reference that was added, removed or changed. Compare a branch's config export with the one on main, or a planning diagram with the site built from it.

Plan in a spreadsheet, document where your team works

A model written in a spreadsheet opens as a diagram, and Edit mode adds entities, fields, references and Markdown notes, with full undo.

When the model is ready, Save as covers the places it needs to live:

  • Markdown and a standalone HTML report, with a section for each bundle and its fields
  • Mermaid and Graphviz DOT, for a README, a pull request or a wiki
  • CSV files of fields, bundles and references, ready as a migration checklist
  • PNG and SVG images, and a link that carries the whole diagram
The Save as menu in Nexus, offering CSV, Graphviz DOT, HTML, JSON, Markdown, Mermaid, PNG and SVG, and Copy link

Safe to open client work: privacy and security you can verify

Site configuration describes how an organisation's website is put together, and client work often comes with a confidentiality agreement. Nexus has no backend: it reads the files, builds the model and draws the diagram on your own machine, and the configuration leaves the browser only when you save, export or share it yourself.

The Nexus 1.0 landing screen, with a drop zone for a Drupal configuration folder, the line 'Your files never leave this page' and 5 ready-made templates

Every file, link and AI-written document is read as data:

  • a Content Security Policy lets the page run only its own scripts
  • markup in labels and help text is shown as text or stripped to basic formatting
  • exported spreadsheets can't run a cell as a formula

Releases carry checksums and a signed provenance attestation, so anyone can confirm that the files they run were built from the repository. Nexus holds the passing OpenSSF Best Practices(Opens in a new tab/window) badge, and its security policy(Opens in a new tab/window) explains how to report a vulnerability privately.

Free, open source and at 1.0

Nexus went live in October 2026 and reached 1.0 in November, after a round of feedback from the Drupal community. It's free to use in any modern browser, open source under GPL-2.0-or-later, the same licence as Drupal, and developed in public on GitHub(Opens in a new tab/window).

5 templates open in 1 click, each drawn from an exact public release: Drupal CMS(Opens in a new tab/window), CivicTheme(Opens in a new tab/window), Drupal core's Umami demo, Thunder(Opens in a new tab/window) and Open Social(Opens in a new tab/window).

Open Social's 8 content types, 20 paragraph types and 11 vocabularies, drawn on 1 canvas in your browser.

Our 1.0 post walks through everything new.

For teams planning a migration, a rebuild or a new content model

Nexus draws the picture our Drupal migration work starts from: the content model a site holds today, and the one it needs next.

If you're planning a migration or a rebuild, this is the shape the engagement takes: we map the content model you have, agree the one you need, and plan what moves where before anything is built.

If your next project starts with a content model nobody has drawn yet, tell us what you're planning.