Finder

Specialist document finder

Specialist Document finders are used to search for Specialist documents

How it works

The returned results in this finder are exclusively specialist documents. Thus, every document on the page will have the specialist_document content schema.

Live examples

• AAIB: Air Accidents Investigation Branch reports (opens in a new tab)
• Competition and Markets Authority cases and projects (opens in a new tab)
• Countryside Stewardship grant finder (opens in a new tab)
• International development funding (opens in a new tab)
• Research for Development Outputs (opens in a new tab)
• European Structural and Investment Funds (ESIF) (opens in a new tab)
• Marine Accident Investigation Branch reports (opens in a new tab)
• Alerts, recalls and safety information: drugs and medical devices (opens in a new tab)
• Drug Safety Update (opens in a new tab)
• Rail Accident Investigation Branch reports (opens in a new tab)
• Service Standard Reports (opens in a new tab)
• Finance and support for your business (opens in a new tab)

How it’s built

These are the underlying technologies that make-up the specialist document finder front template.

Content schema

finder (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

finder (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.

Rendering app

finder-frontend (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 specialist document finder frontend template

Component	Source	Publishing app input field(s)
Layout super navigation header	Autogenerated in frontend template
Contextual breadcrumbs	Autogenerated in frontend template
The Search component is above the filters, which occupies 1/3 of the page	Autogenerated in frontend template
Heading	Autogenerated in frontend template
Option select appears within the search filter	Autogenerated in frontend template
Select appears within the search filter	Autogenerated in frontend template
Form checkboxes appears within the search filter	Autogenerated in frontend template
Form hint text appears within the search filter	Autogenerated in frontend template
Date filter appears within the search filter	Autogenerated in frontend template
All the filters are within the Expander	Autogenerated in frontend template
Previous and next navigation appears if there is more than 20 returned search results	Autogenerated in frontend template
Subscription link	Autogenerated in frontend template
Document list	Autogenerated in frontend template
Feedback	Autogenerated in frontend template
Layout footer	Autogenerated in frontend template
Page title	Autogenerated in frontend template
The Govspeak content is situated above the filter and returned results	Autogenerated in frontend template
Phase banner	Autogenerated in frontend template
Metadata block	Autogenerated in frontend template

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.