Mainstream browse

Level two

Mainstream browse is a topic system that groups together content by popular topics on GOV.UK.

How it works

Level two pages link to mostly mainstream content or they can also include Whitehall content, where there is a user need. Level two pages can be curated or alphabetical.

Live examples

• Curated level two browse page – Vehicle, tax MOT and insurance (opens in a new tab)
• Alphabetical level two browse page – School admissions and transport to school (opens in a new tab)

How it’s built

These are the underlying technologies that make-up the level two front template.

Content schema

mainstream_browse_page (opens in a new tab)

What is a content schema?

A GOV.UK content schema is a JSON schema that defines the data structure of a piece of content. It determines what content and metadata attributes the page has.

Content type

mainstream_browse_page (opens in a new tab)

What is a content type?

Content type describes the types of pages that exist on GOV.UK. It’s stored in the content item (JSON) as document_type. It powers search filters in all finders and changes the content type label users see on GOV.UK pages.

Publishing app

collections-publisher (opens in a new tab)

What is a publishing app?

Publishing apps are used by publishers across government departments to publish content to GOV.UK.

Rendering app

collections (opens in a new tab)

What is a rendering app?

Rendering apps render content to GOV.UK end-users.

Components

The components used within the level two frontend template

Component	Source	Publishing app input field(s)
Layout super navigation header	Autogenerated in frontend template
Breadcrumbs	Autogenerated in frontend template
Feedback	Autogenerated in frontend template
Layout footer	Autogenerated in frontend template
Heading	Customized by publisher	Title (required)
Lead paragraph	Customized by publisher	Description (required)
List component	Customized by publisher	Add link to current list
Heading	Customized by publisher	Subtopic title (required)

How to report an issue

If you happen to come across an issue:

1. Report it on Github (opens in a new tab).
2. Once the issue has been added, update this document by adding the title and Github Issue’s link.
3. Give yourself a high-five.

Help improve this page

To help make sure that this page is useful, relevant and up to date, submit a GitHub issue (opens in a new tab) with your proposed updates.