What Is Model Publishing?

Turn a model into a navigable website or a PDF report — and how the three pieces fit together.

Metapad can turn your model into something other people read: a navigable website or a polished PDF report, built from the model itself so it never goes stale.

You don't lay out pages by hand. You describe how each kind of thing should look, and Metapad generates a page for every one of them. A model with 200 elements becomes a 200-page site from a handful of instructions.

The three pieces

Renderings — a page template for one type. Write one Service rendering and every Service in your model gets a page in that shape: its description, its properties, a table of the systems it depends on. Change the rendering and all of those pages change at once.

Navigation trees — the reading order and the site's menu. A tree decides which elements become pages and how they are grouped.

A publication — ties it together: which trees form the navigation, which rendering presents each type, what the landing page says, and how the site is branded.

One publication, two outputs

The same publication produces the website and the PDF. There is no separate report to keep in step — you pick a format when you export.

It is also multilingual by default: one publication renders in every language your model has, so German readers get German pages without you building a second site.

What readers get

• A sidebar site map generated from your navigation tree
• Full-text search across every page
• The AI assistant, so they can ask questions about the model
• Working links between pages wherever your text references another element

Before you start

Publishing requires the Team plan. It is checked against the plan of whoever owns the model, so if you have edit access to someone else's Team model you can publish it too.

You will find Renderings and Publications in the Model Navigator, alongside Filters and Trees.