A portable standard for web modules


In short, UI schema is a supplement to schema.org.

Whereas they aim to provide a sensible specification for information architecture, UI schema aims to do the same for presentation and authoring of visual content.


Because websites are still a hot mess, and we want to help fix that.

Realistically speaking, there is no such thing as a de facto CMS or website framework, and there won't be in the foreseeable future.

We believe that CMS'es, and the websites they provide content for, are in need of a sensible standard in order to communicate more seamlessly.

If every CMS and website could be taught the same language, the technical and communicational workload of web solution providers could be reduced, which would free up their time to work on making the best user experiences they can think of.

Provider/client communication

When both parties are familiar with the terms used to describe a website, the communication barrier is significantly reduced.


All software that outputs uischema.org modules also complies with the schema.org specification, so you can render the output as json-ld directly.

CMS agnostic content

By installing a plugin, schemas and authored content can be exported and imported to and from other CMS'es.

Web agnostic templates

Reduce the amount of markup work needed by keeping a handy collection of templates that can be used anywhere.



The following CMS'es are officially supported:


For websites, you need the css and templates of your modules. Then just request the content from your CMS and render it (we suggest using mustache). The only remaining work in most cases will be to set up site navigation.

Check out some examples here

Creating schemas

To create your own schemas, please check out the specification.