Skip to main content
Finder

Case studies finder

A directory of all the case studies that can be found on GOV.UK.

How it works

Case Studies finder lists all case studies that is published on GOV.UK. End-users can use the search component to filter the returned results on the page.

Live example

Case studies: Real-life examples of government activity

How it’s built

These are the underlying technologies that make-up the case studies finder front template.

Content schema

finder

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

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

What is a rendering app?
Rendering apps render content to GOV.UK end-users.

Components

The components used within the case studies finder frontend template
Component Source Publishing app input field(s)
Layout super navigation header Autogenerated in frontend template
Contextual breadcrumbs Autogenerated in frontend template
Heading used to display number of returned search results Autogenerated in frontend template
Feedback Autogenerated in frontend template
Layout footer Autogenerated in frontend template
Page title Autogenerated in frontend template
Search Autogenerated in frontend template
Subscription links - rendered top and bottom of the page, but displayed only at the bottom of the page Autogenerated in frontend template
Document list Autogenerated in frontend template
Previous and next navigation 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 frontend template

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.