This package provides templates which render variants of the FT.com header and navigation.

Usage no npm install needed!

<script type="module">
  import financialTimesDotcomUiHeader from 'https://cdn.skypack.dev/@financial-times/dotcom-ui-header';



This package provides templates which render variants of the FT.com header and navigation.

Getting started

This package is compatible with Node 12+ and is distributed on npm.

npm install --save @financial-times/dotcom-ui-header

After installing the package you will need to configure your application to fetch data from the Next Navigation API required to render these UI components. Page Kit provides two packages for this:

  1. dotcom-middleware-navigation (if you are using Express)
  2. dotcom-server-navigation (if you are not using Express)


This package provides several UI components to render different parts and styles of the FT.com header:

  • <Header /> the full header with navigation with lots of options. See header elements for a breakdown of its parts.
  • <Drawer /> the navigation drawer which should be rendered separately from the header, preferably near the bottom of the document.
  • <LogoOnly /> a simple masthead displaying the logo image which doesn't require any configuration. Doesn't link to the homepage by default, pass in a showLogoLink={true} prop to make it link through.
  • <NoOutboundLinksHeader /> a stripped back masthead displaying the logo image, user actions and optional sub-navigation. Aimed at reducing the possibility of a user clicking through to content related pages.
import { Header, Drawer } from '@financial-times/dotcom-ui-header'

const SiteHeader = (props) => (
  <Header data={props.navigationData} userIsLoggedIn={props.userIsLoggedIn} />
  <Drawer data={props.navigationData} userIsLoggedIn={props.userIsLoggedIn} />

Please note that the header components are designed to be used on the server-side and should not be rendered on the client-side. Although it is possible to render them on the client-side there is usually no reason to do so and is not supported.


Once you are rendering the header components in your page you will need to initialise the client-side code to add styles and interactive behaviour.

To initialise the client-side JavaScript import the package and call the .init() method:

import * as header from '@financial-times/dotcom-ui-header'


This component includes styles written in Sass which can be imported into your application's main Sass stylesheet.

@import '@financial-times/dotcom-ui-header/styles';

Please note that the exact usage of styles will depend on how you configure your Sass compiler and whether or not you are using Bower to install dependencies.


All header components with the exception of <LogoOnly /> require the following options:

variant 'simple' | 'large-logo' | string true 'simple' Adds a class name to the header element
userIsAnonymous boolean true true Marks a user as anonymous - can be set by middleware included with n-express
userIsLoggedIn boolean true false Marks a user as logged in - can be set by middleware included with n-express
showUserNavigation boolean true true Show user navigation options such as Sign out or Subscribe
showSubNavigation boolean true true Show the sub-navigation component which may include the crumbtrail
showStickyHeader boolean true true Enable rendering of the sticky header component
showMegaNav boolean true true Enable rendering of the drop-down "mega-nav"
data object false Navigation data for rendering the header links fetched from the navigation API

Header Elements


The topmost element - or masthead - contains the logo, toggle buttons for the drawer and search bar, and the MyFT indicator if logged in.

By default the logo serves as a home page link, which can be deactivated by providing prop showLogoLink: false.

Example header top element

Please note that the myFT unread articles indicator code lives outside this package in n-myft-ui.


The navigation element contains links for navigating the top-level sections of FT.com. Some of the sections may include subsections which are presented in "mega-nav" dropdown elements.

Example header navigation element

Please note that the data for this menu is regionally-specific and changes depending on the selected FT edition.


If enabled the sub-navigation element will be rendered if either crumbtrail or subsection navigation data is provided. This is usually page specific and will be automatically set when using thedotcom-middleware-navigation package.

Example header subNavigation element


The drawer menu is a separate component and is not included within the header. It is the primary navigation on small screens and supplementary on large screens. It mostly re-uses the data from the navigation element but can also have extra groups of links.

To support a non-JS, or core experience, the drawer component should be rendered near the bottom of the document.

Sticky header

If enabled the sticky header is shown when users scroll down on both small and large screens. It combines similar components to the top and navigation elements.

SVG logos

These are SVG logos as React components, which can be imported for inclusion by other components.

Rendering logos as SVGs allows them to be visible faster than as external images, so is an approach best applied to logos that need to be displayed as quickly as possible upon visiting a page.

The React components are auto-generated using a script - npm run build:svg-to-react - which converts the source SVG file acquired from dev dependency @financial-times/logo-images.