/* ---------------------------------------------------------------------------
   Page sections
   The hero, the carousels and the repeating section patterns the homepage,
   the case studies and the service pages all share.

   Typography is deliberately NOT set here. Font family, size, line height and
   weight all come from Blocksy's customiser, so TAP can change them without a
   developer. What this sheet owns is layout, spacing, and the few colours that
   only make sense in context, such as white text over a darkened image.
   --------------------------------------------------------------------------- */

/* --- Video hero ---------------------------------------------------------- */
/* The header overlays this, so the hero's own height is the full height and
   nothing is added for the bar sitting on top of it. */
.tap-hero {
	position: relative;
	height: var(--tap-hero-height, 700px);
	overflow: hidden;
	background: var(--tap-navy);
}

.tap-hero__video {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

.tap-hero__inner {
	position: relative;
	z-index: 1;
	display: flex;
	flex-direction: column;
	align-items: center;
	justify-content: center;
	height: 100%;
	padding: 0 20px;
	text-align: center;
}

.tap-hero__lockup {
	max-width: min(560px, 80vw);
	height: auto;
}

.tap-hero__heading {
	color: #fff;
	margin: 0;
	text-shadow: 0 2px 20px rgba(0, 0, 0, 0.5);
}

@media (max-width: 960px) {
	.tap-hero { height: 300px; }
}

@media (max-width: 640px) {
	.tap-hero { height: 200px; }
}

/* --- Carousels ----------------------------------------------------------- */
/* Scroll-snap rather than a JavaScript carousel. It is a horizontal list of
   equal-width cards with no autoplay, which is exactly what a scroll container
   does natively: it keeps keyboard and touch behaviour for free, and it still
   works if the script fails. The arrows are added by sections.js. */
.tap-carousel {
	position: relative;
}

.tap-carousel__track {
	display: flex;
	gap: 20px;
	margin: 0;
	padding: 0 0 10px;
	list-style: none;
	overflow-x: auto;
	scroll-snap-type: x mandatory;
	scrollbar-width: thin;
}

.tap-carousel__track > li {
	flex: 0 0 auto;
	scroll-snap-align: start;
}

.tap-carousel__btn {
	position: absolute;
	top: 50%;
	transform: translateY(-50%);
	z-index: 2;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 44px;
	height: 44px;
	padding: 0;
	color: var(--tap-ink);
	background: rgba(255, 255, 255, 0.9);
	border: 1px solid rgba(0, 0, 0, 0.1);
	border-radius: 50%;
	cursor: pointer;
}

/* The chevron is drawn as an SVG in sections.js rather than typed as a single
   angle quote, because a glyph's ink is not centred in its em box and sat low
   and left of the middle. The path is centred in its viewBox, so the flex
   centring above is all it takes. */
.tap-carousel__btn svg {
	display: block;
	width: 22px;
	height: 22px;
}

/* display:flex above would otherwise beat the [hidden] attribute the script
   sets on a carousel with nothing to scroll to. */
.tap-carousel__btn[hidden] { display: none; }
.tap-carousel__btn[disabled] { opacity: 0.3; cursor: default; }
.tap-carousel__btn--prev { left: -8px; }
.tap-carousel__btn--next { right: -8px; }

/* --- People -------------------------------------------------------------- */
.tap-people__item {
	width: 220px;
	text-align: center;
}

.tap-people__item a {
	color: inherit;
	text-decoration: none;
}

.tap-people__photo {
	display: block;
	width: 100%;
	height: auto;
	margin-bottom: 12px;
}

.tap-people__name {
	display: block;
	font-family: 'Staatliches', 'Lato', sans-serif;
	font-size: 19px;
	letter-spacing: 0.5px;
	color: var(--tap-navy);
}

.tap-people__role {
	display: block;
	font-size: 14px;
	color: var(--tap-ink);
	opacity: 0.75;
}

/* --- Client logos -------------------------------------------------------- */
.tap-logos__item {
	width: 160px;
	display: flex;
	align-items: center;
	justify-content: center;
}

.tap-logos__img {
	width: 100%;
	height: auto;
}

/* --- Six box services grid ----------------------------------------------- */
/* Six across on desktop, three on tablet, two on a phone. The old build went
   straight from six to three to one, which left a lot of white space on a
   phone for no reason. */
.tap-sixbox {
	display: grid;
	gap: 26px;
	grid-template-columns: repeat(2, 1fr);
}

@media (min-width: 640px) {
	.tap-sixbox { grid-template-columns: repeat(3, 1fr); }
}

@media (min-width: 1200px) {
	.tap-sixbox { grid-template-columns: repeat(6, 1fr); }
}

/* Learning & Engagement's first grid has four boxes, not six, and reads as
   problem statements rather than services. Four across keeps them even
   instead of leaving two empty columns on the right. */
@media (min-width: 1200px) {
	.tap-sixbox--four { grid-template-columns: repeat(4, 1fr); }
}

/* Everything in a box is centred, as it is on the old site and on the eight
   service pages that share this grid: uk-text-center sits on the icon, the
   title and the text panel of every one of them. */
.tap-sixbox__item {
	text-align: center;
}

.tap-sixbox__item img {
	display: block;
	width: 80px;
	height: auto;
	margin: 0 auto 10px;
}

/* The rule under the title is a short centred one, not a full-width underline.
   The old build drew it as its own <hr class="blackhr uk-width-small
   uk-margin-auto">, which is UIkit's 150px, centred. A pseudo-element gets the
   same result without an empty element in the content for Rob to delete by
   accident. */
.tap-sixbox__item h3 {
	position: relative;
	margin: 0 0 14px;
	padding-bottom: 14px;
	border-bottom: 0;
}

.tap-sixbox__item h3::after {
	content: "";
	position: absolute;
	left: 50%;
	bottom: 0;
	width: 150px;
	max-width: 100%;
	transform: translateX(-50%);
	border-top: 2px solid var(--tap-ink);
}

.tap-sixbox__item p {
	margin: 0;
}

/* --- Case study teaser --------------------------------------------------- */
/* The teaser is a core Cover block, so the background image, the dark overlay
   and the minimum height all come from the block itself and are editable in
   the editor. All that is left here is the white-on-image colours and the
   outline button, neither of which Cover provides. */
.tap-teaser-cover .tap-teaser__eyebrow,
.tap-teaser-cover .tap-teaser__headline {
	color: #fff;
}

.tap-teaser-cover .tap-teaser__eyebrow {
	margin: 0 0 14px;
}

.tap-teaser-cover .tap-teaser__headline {
	max-width: 760px;
	margin: 0 auto 26px;
}

.tap-teaser-cover .tap-teaser__cta {
	margin: 0;
}

.tap-btn {
	display: inline-block;
	padding: 12px 28px;
	font-family: 'Staatliches', 'Lato', sans-serif;
	letter-spacing: 1px;
	text-transform: uppercase;
	text-decoration: none;
	color: #fff;
	border: 2px solid #fff;
}

.tap-btn:hover,
.tap-btn:focus-visible {
	color: var(--tap-navy);
	background: #fff;
}

/* --- Generic section rhythm ---------------------------------------------- */
.tap-section {
	padding: 70px 0;
}

.tap-section--wash { background: var(--tap-wash); }
.tap-section--tight { padding: 40px 0; }

.tap-section__inner {
	max-width: 1200px;
	margin: 0 auto;
	padding: 0 20px;
}

.tap-intro {
	max-width: 900px;
	margin: 0 auto;
	text-align: center;
}

.tap-intro h1 {
	margin: 0 0 30px;
}

/* uk-text-lead on the old build: 18px on a 24px line, a step up from body
   copy. Sized here because it belongs to this section rather than to the
   site's type scale, which stays in the customiser. */
.tap-intro p {
	font-size: 18px;
	line-height: 24px;
}

/* The short centred rule the old service pages put under the h1. Core's
   separator is full width by default, so it needs constraining rather than
   restyling. */
.tap-rule {
	width: 180px;
	margin: 0 auto 30px;
	border: 0;
	border-top: 2px solid var(--tap-ink);
	opacity: 1;
}

.tap-quote {
	max-width: 780px;
	margin: 0 auto;
	text-align: center;
}

/* Blocksy draws a rule down the left of every blockquote. The old build's
   testimonials had none: centred Lato italic and nothing else. Reset here
   rather than per page, because every .tap-quote on the site is reproducing
   one of those testimonials. */
.tap-quote {
	border: 0;
	padding: 0;
}

.tap-quote p {
	font-style: italic;
	font-size: 18px;
	line-height: 1.6;
}

.tap-quote cite {
	display: block;
	margin-top: 14px;
	font-style: normal;
	opacity: 0.75;
}

.tap-section__heading {
	margin: 0 0 34px;
	text-align: center;
}

/* --- Header B Corp mark -------------------------------------------------- */
/* Sized here rather than in the customiser because it is an image inside a
   header widget, which Blocksy has no height control for.

   64px to sit just under the old site's 68px, matching the TAP logo's 64. The
   source is 242x400, so at 2x this still has detail to spare; the previous
   blur was an 80px file being stretched into an 80px box on a retina screen,
   not anything CSS was doing. */
.tap-header-bcorp,
.tap-header-bcorp a {
	display: block;
	margin: 0;
	line-height: 0;
}

.tap-header-bcorp img {
	width: auto;
	height: 64px;
	max-width: none;
}

@media (max-width: 999px) {
	.tap-header-bcorp img {
		height: 40px;
	}
}

/* A hero given a still image rather than a video. The old inner pages all
   worked this way: the class said videoheader but there was no video. */
.tap-hero {
	background-position: center;
	background-size: cover;
}


/* --- Footer copyright colour --------------------------------------------- */
/* The one footer rule that cannot live in the customiser. Blocksy scopes a
   row's font colour to `.ct-widget` only (see rowFontColor in
   inc/panel-builder/footer/middle-row/dynamic-styles.php), and the copyright
   item is not a widget, so it keeps the default dark text. On TAP's rust
   footer that is unreadable.

   Everything else about the footer, background, spacing, column count, widget
   colours, now comes from Blocksy's own generated CSS and is editable in
   Customiser > Footer. */
.ct-footer .ct-footer-copyright,
.ct-footer .ct-footer-copyright a {
	color: #fff;
}

.ct-footer .ct-footer-copyright a:hover,
.ct-footer .ct-footer-copyright a:focus-visible {
	color: rgba(255, 255, 255, 0.75);
}

/* --- Page title under the transparent header ----------------------------- */
/* The header is transparent and sits over the top of the page, which is right
   on the homepage and on any page with a tall hero. On a page that has neither,
   Blocksy renders the plain title block (`.hero-section[data-type="type-1"]`)
   at the very top of the content area, so the title ends up behind the nav.

   On mobile that reads as the B Corp badge sitting on top of the title, because
   the badge is the left-hand item in the mobile header row and the title is
   left-aligned underneath it. The badge is not the problem, the missing offset
   is, and it is wrong on desktop too, just less obviously.

   Blocksy's own fix for this is a type-2 hero, which reserves the header height
   itself. These pages are stubs and will each get a proper banner when they are
   built out, at which point this block stops applying on its own, because the
   plain title block is no longer rendered.

   --header-height is Blocksy's, currently 100px, set in Customiser > Header. */
.hero-section[data-type="type-1"] {
	padding-top: calc(var(--header-height, 100px) + 40px);
}

/* --- Video hero as a core Cover block ------------------------------------ */
/* The homepage hero is a core Cover with a video background rather than a
   shortcode, so the video, the height and the overlay are all editable in the
   block itself. Cover has no responsive height control, so the two step-downs
   stay here, matching the 700/300/200 of the old build. The inline min-height
   Cover writes onto the element is why these need !important. */
.tap-hero-cover {
	background: var(--tap-navy);
}

@media (max-width: 960px) {
	.tap-hero-cover { min-height: 300px !important; }
}

@media (max-width: 640px) {
	.tap-hero-cover { min-height: 200px !important; }
}

.tap-hero-cover .tap-hero__lockup {
	margin: 0;
}

.tap-hero-cover .tap-hero__lockup img {
	width: min(560px, 80vw);
	height: auto;
}

/* --- Teaser button as a core Button block -------------------------------- */
/* Was a hand-written anchor inside a paragraph, which is one stray keystroke
   away from losing its class. As a core Button it survives editing. Core gives
   it a filled background and a radius; the old build's was a white outline, so
   both are reset here rather than set as block attributes, which would bake
   the colours into every page's markup. */
.tap-btn-block .wp-block-button__link {
	padding: 12px 28px;
	font-family: 'Staatliches', 'Lato', sans-serif;
	letter-spacing: 1px;
	text-transform: uppercase;
	color: #fff;
	background: transparent;
	border: 2px solid #fff;
	border-radius: 0;
}

.tap-btn-block .wp-block-button__link:hover,
.tap-btn-block .wp-block-button__link:focus-visible {
	color: var(--tap-navy);
	background: #fff;
}

/* --- A heading with the short rule under it ------------------------------ */
/* The old build drew this under section headings and under each of the six
   service box titles. Opt-in rather than applied to every .tap-section__heading
   so the service pages keep whatever they already have. */
.tap-heading-ruled::after {
	content: "";
	display: block;
	width: 120px;
	margin: 16px auto 0;
	border-top: 3px solid var(--tap-ink);
}

/* --- Testimonials -------------------------------------------------------- */
/* One quote at a time, matching the old Widgetkit slider. The track is a core
   Group with a flex layout, so what sits inside it are ordinary core Quote
   blocks: editable, reorderable, and addable from the editor without touching
   code. The carousel behaviour is layered on by sections.js. */
.tap-quotes .tap-carousel__track {
	gap: 0;
	padding-bottom: 0;
	scrollbar-width: none;
}

.tap-quotes .tap-carousel__track::-webkit-scrollbar {
	display: none;
}

.tap-quotes .tap-carousel__track > * {
	flex: 0 0 100%;
	scroll-snap-align: center;
	margin: 0;
}

/* The slide has to be exactly as wide as the track, or scrolling by one
   track width lands between two quotes. The reading width is put back on the
   text inside it rather than on the blockquote, which is the flex item. */
.tap-quotes .tap-quote {
	flex: 0 0 100%;
	max-width: none;
	padding: 0 50px;
	border: 0;
	color: var(--tap-rust);
	font-style: italic;
}

.tap-quotes .tap-quote p,
.tap-quotes .tap-quote cite {
	max-width: 860px;
	margin-left: auto;
	margin-right: auto;
}

.tap-quotes .tap-quote p {
	margin-top: 0;
	margin-bottom: 0;
}

.tap-quotes .tap-quote cite {
	color: var(--tap-ink);
	font-style: normal;
	opacity: 1;
}

/* --- Contact page -------------------------------------------------------- */
/* The address block. On the old site this was marked up as an <h2> with two
   <p> tags inside it, which is not valid HTML and is not a heading either. It
   is an address, so it is paragraphs here, styled to the same Lato 24px/700
   it had before. */
.tap-contact-address {
	font-size: 24px;
	font-weight: 700;
	line-height: 1.4;
	color: var(--tap-ink);
}

.tap-contact-address a {
	color: inherit;
	text-decoration: none;
}

.tap-contact-address a:hover,
.tap-contact-address a:focus-visible {
	text-decoration: underline;
}

.tap-contact-cols {
	gap: 50px;
	align-items: flex-start;
}

/* The gold card the form sits in. #fdb924 is taken off the old build's
   uk-card-secondary, and is not one of the eight Blocksy palette slots, so it
   lives here with the other brand colours that do not map onto one. */
.tap-form-card {
	padding: 34px;
	background: var(--tap-gold);
}

/* Fluent Forms ships its own light theme, which puts rounded grey inputs on
   the gold. The old form was square white fields and a full width dark button,
   so that is what these put back. Scoped to the card so any other form on the
   site keeps the plugin's defaults. */
.tap-form-card .fluentform .ff-el-form-control {
	padding: 11px 12px;
	background: #fff;
	border: 1px solid rgba(0, 0, 0, 0.15);
	border-radius: 0;
	box-shadow: none;
}

.tap-form-card .fluentform .ff-el-form-control:focus {
	border-color: var(--tap-navy);
	outline: 2px solid var(--tap-navy);
	outline-offset: 1px;
}

.tap-form-card .fluentform .ff-el-input--label label {
	font-weight: 700;
	color: var(--tap-ink);
}

/* The submit button is fought over by three stylesheets: Blocksy styles every
   [type="submit"] through its own button variables, Fluent Forms styles
   .ff_btn_style, and this sheet wants the old site's square Staatliches block.
   Specificity alone did not settle it, so the properties that have to win say
   so. Scoped to the card, so no other button on the site is affected. */
.tap-form-card .fluentform .ff-btn-submit {
	width: 100% !important;
	padding: 13px 28px !important;
	font-family: 'Staatliches', 'Lato', sans-serif !important;
	font-size: 18px !important;
	letter-spacing: 1px !important;
	text-transform: uppercase !important;
	color: #fff !important;
	background: var(--tap-navy) !important;
	border: 0 !important;
	border-radius: 0 !important;
}

.tap-form-card .fluentform .ff-btn-submit:hover,
.tap-form-card .fluentform .ff-btn-submit:focus-visible {
	background: var(--tap-rust) !important;
}

/* The plugin's error red is not far off the brand rust, which reads as a
   styled label rather than a problem. This is the one place a louder red is
   the right answer. */
.tap-form-card .fluentform .ff-el-is-error .text-danger,
.tap-form-card .fluentform .error.text-danger {
	color: #8c0000;
	font-weight: 700;
}

@media (max-width: 781px) {
	.tap-contact-cols {
		gap: 34px;
	}
}

/* --- Case study pages ---------------------------------------------------- */
/* Eleven of the twelve share one shape: a 500px still hero, a centred
   proposition, a run of body blocks that alternate text and image, and a
   closing testimonial. Only the number of body blocks changes, so everything
   here is written once and carries all twelve.
   Built 6 November 2026. */

/* The old build stacked these sections with their bottom padding removed, so
   the gap between one block and the next was a single 70px. .tap-section on
   its own would double that. */
.tap-cs-block {
	padding: 35px 0;
}

/* The proposition heading is an h2 here, not the h1 it is on a service page,
   because on a case study the hero carries the h1. */
.tap-intro h1,
.tap-intro h2 {
	margin: 0 0 30px;
}

/* uk-h3 on the old build was Lato 700 at 24px on a 1.3 line. Pinned here
   rather than changed in the customiser, which would move every h3 on the
   site. */
.tap-cs-block h3 {
	font-family: 'Lato', sans-serif;
	font-weight: 700;
	font-size: 24px;
	line-height: 1.3;
	margin: 0 0 14px;
}

/* The short rule under a left-aligned heading. .tap-rule is the centred one
   the proposition uses; this is the same rule pushed to the left, matching the
   old uk-width-small hr. */
.tap-rule--left {
	width: 150px;
	margin: 0 0 24px;
}

/* The old grid gutter was 40px. Core's column gap is narrower. */
.tap-cs-block .wp-block-columns {
	gap: 40px;
	align-items: center;
}

.tap-cs-block figure.wp-block-image {
	margin: 0;
}

.tap-cs-block figure.wp-block-image img {
	display: block;
	width: 100%;
	height: auto;
}

/* A paragraph immediately before an image wants the gap to belong to the
   image, not to sit twice. */
.tap-cs-block p:last-child {
	margin-bottom: 0;
}

/* The closing testimonial. The old page removed the padding above it so the
   quote sits close to the last body block. */
.tap-cs-quote {
	padding-top: 0;
}

/* --- Our People ---------------------------------------------------------- */
/* Four columns on the old build: name and role, portrait, bio, favourites.
   Here the portrait and bio share a column, as they did, so the grid is three.
   Rendered by [tap_people_list] off the person post type, which is also what
   feeds the homepage slider. Built 6 November 2026. */

.tap-person {
	position: relative;
	display: grid;
	grid-template-columns: 1fr 2fr 2fr;
	gap: 40px;
	align-items: start;
	padding: 40px 0;
	border-top: 1px solid rgba(31, 48, 62, 0.12);
}

.tap-person:first-child {
	border-top: 0;
}

.tap-person__name h2 {
	font-family: 'Lato', sans-serif;
	font-weight: 700;
	font-size: 24px;
	line-height: 1.3;
	margin: 0 0 14px;
}

.tap-person__role {
	font-weight: 700;
	font-size: 16px;
	margin: 0;
}

.tap-person__photo {
	display: block;
	width: 100%;
	height: auto;
	margin: 0 0 20px;
}

.tap-person__bio p {
	font-size: 18px;
	line-height: 24px;
}

.tap-person__bio p:last-child,
.tap-person__favlist p:last-child {
	margin-bottom: 0;
}

.tap-person__favourites h3 {
	font-family: 'Lato', sans-serif;
	font-weight: 700;
	font-size: 18px;
	margin: 0 0 16px;
}

/* The old build used a UIkit icon font for the heart. One character costs
   nothing and survives a theme change. */
.tap-person__heart {
	color: var(--tap-rust);
	font-size: 24px;
	float: right;
	line-height: 1;
}

.tap-person__favlist p {
	font-size: 16px;
	line-height: 1.5;
	margin: 0 0 12px;
}

/* An extra, invisible target so links to the old page anchors still land.
   Taken out of the flow: as a grid child it would otherwise claim the first
   cell and push every column along by one. */
.tap-person__legacy {
	position: absolute;
	top: 0;
	left: 0;
	width: 0;
	height: 0;
}

@media (max-width: 960px) {
	.tap-person {
		grid-template-columns: 1fr;
		gap: 20px;
	}
}

/* --- Why We Exist -------------------------------------------------------- */
.tap-whyquote .wp-block-columns {
	align-items: flex-start;
}

.tap-whyquote__role {
	font-weight: 700;
	font-size: 16px;
}

.tap-signature img,
img.tap-signature {
	max-width: 200px;
	height: auto;
}

.tap-intro figure.tap-signature {
	margin: 30px auto 0;
}

/* --- TAP España ---------------------------------------------------------- */
/* The six-box grid here carries titles only, no copy, so the boxes need less
   room than they do on the homepage. */
.tap-sixbox--titles .tap-sixbox__item h3 {
	margin-bottom: 0;
}

.tap-office__flag img,
figure.tap-office__flag {
	margin: 20px 0 0;
}

figure.tap-office__flag img {
	width: 60px;
	height: auto;
}

/* --- Solid button, for buttons on a white section ------------------------ */
/* .tap-btn-block is the white outline the homepage hero needs, which is
   invisible on a white page. The old build used uk-button-danger for the B
   Corp report links: solid rust, white text. */
.tap-btn-block--solid .wp-block-button__link {
	color: #fff;
	background: var(--tap-rust);
	border-color: var(--tap-rust);
}

.tap-btn-block--solid .wp-block-button__link:hover,
.tap-btn-block--solid .wp-block-button__link:focus-visible {
	color: #fff;
	background: var(--tap-link-hover, #f80010);
	border-color: var(--tap-link-hover, #f80010);
}

/* The two office flags on TAP España sit inside a .tap-cs-block, whose images
   are full width by design. These are 200px icons, not photographs. */
.tap-cs-block figure.tap-office__flag {
	margin: 20px 0 0;
}

.tap-cs-block figure.tap-office__flag img {
	width: 90px;
	height: auto;
}

/* --- Blog bylines -------------------------------------------------------- */
/* The old build closed every post with "Name - DD/MM/YYYY" and a sentence
   about the author, both in the lead size. Appended by inc/blog.php because
   the byline is post meta, not a WordPress user. */
.tap-byline {
	margin-top: 40px;
	padding-top: 24px;
	border-top: 1px solid rgba(31, 48, 62, 0.12);
}

.tap-byline__name {
	font-size: 18px;
	line-height: 24px;
	font-weight: 700;
	margin: 0 0 8px;
}

.tap-byline__bio {
	font-size: 18px;
	line-height: 24px;
	font-style: italic;
	margin: 0;
}

/* --- Hero flush with the header ------------------------------------------ */
/* Blocksy puts 60px of top padding on the content container on every page
   except the front page. On an inner page that leaves a white strip between
   the fixed header and the hero, where the old site ran the header straight
   over the top of it. Zeroed only where the page actually opens with a hero,
   so an ordinary page keeps its breathing room. */
.ct-container-full:has(.entry-content > .tap-hero:first-child),
.ct-container-full:has(.entry-content > .tap-hero-cover:first-child) {
	padding-top: 0;
}

/* --- Solid navbar once the mobile header takes over ----------------------- */
/* Blocksy's transparent header is absolutely positioned over the top of the
   page. That is right on desktop, where the hero is 700px or 500px tall and the
   centred heading sits well clear of the bar. It is wrong on a phone: the hero
   steps down to 300px and then 200px, so the centred heading lands exactly
   where the logo tile is and the two overlap.

   The old site solved this by dropping the overlay on small screens: solid dark
   navbar, hero underneath it. This does the same.

   The breakpoint is Blocksy's own 999.98px, not the 960px the hero step-down
   uses, so that the bar turns solid at exactly the width where Blocksy swaps
   the desktop header for the mobile one. Between 960px and 1000px the hero is
   still 500px tall, so nothing collided there, but a transparent mobile header
   for that 40px band would look like a bug.

   Two rules because Blocksy splits the job: the wrapper carries the
   positioning, the row carries the background gradient. */
@media (max-width: 999.98px) {
	#header [data-device="mobile"][data-transparent] {
		position: static;
		background-color: var(--tap-navy-nav);
	}

	[data-header*="type-1"] .ct-header [data-transparent-row="yes"][data-row*="middle"] {
		background-image: none;
		background-color: var(--tap-navy-nav);
	}
}

/* --- Matching the old build's type sizes --------------------------------- */
/* Measured against theadplain.com with getComputedStyle, 10 November 2026.
   The old site drops to 14px/22 for body copy inside a narrow column or box,
   where this build had been using the global 18px everywhere. Three places
   were affected, and all three read as too large beside the old page. */

/* The six service boxes. Old: Lato 14/22, centred, which it already is. */
.tap-sixbox__item p {
	margin: 0;
	font-size: 14px;
	line-height: 22px;
}

/* The closing testimonial on a case study. Old: Lato 300 at 24/36, which is a
   step larger than body copy, not smaller. Scoped to .tap-cs-quote so the
   homepage testimonial carousel keeps its own size. */
.tap-cs-quote .tap-quote p {
	/* size now set globally on .tap-quote p */
}

/* The staff quotes on Why We Exist. Old: centred Lato 14/22 in the third
   column, with the role line at 18/28 rather than 16. */
.tap-whyquote .wp-block-column:last-child p {
	text-align: center;
	font-size: 14px;
	line-height: 22px;
}

.tap-whyquote__role {
	font-weight: 700;
	font-size: 18px;
	line-height: 28px;
}

/* --- Careers ------------------------------------------------------------- */
/* The line under "Start Your Adventure" is a heading on the old page, but at
   uk-h4 in the body font, so it reads as a lead rather than as a second
   display heading. Reproduced here rather than demoting it to a paragraph,
   which would lose the outline. */
.tap-lead {
	font-family: 'Lato', sans-serif;
	font-weight: 700;
	font-size: 24px;
	line-height: 31px;
}

/* The two vacancies sit side by side in bordered boxes. The border on the old
   site is #ff0000, from a class called redboxborder, which is not in the
   palette anywhere; see tap-design-tokens.md. Matched for now, one value away
   from --tap-rust if Josh would rather. */
.tap-jobs {
	gap: 40px;
}

.tap-job {
	height: 100%;
	padding: 30px 30px 30px 20px;
	border: 2px solid #ff0000;
}

.tap-job p {
	font-size: 14px;
	line-height: 22px;
}

/* The salary line: rust, light and italic, as on the old page. */
.tap-job h5 {
	color: var(--tap-rust);
	font-weight: 300;
	font-style: italic;
}

/* The second line in a policy page hero. The old build drew "Updated May 2024"
   under the title at display size in the brand rust, inside the hero itself.
   .tap-hero__inner is a column so the two stack rather than sit side by side;
   with a single child that changes nothing. */
.tap-hero__sub {
	margin: 10px 0 0;
	color: var(--tap-rust);
	text-shadow: 0 2px 20px rgba(0, 0, 0, 0.5);
}

/* Policy pages: the old build centred the section labels and the body copy. */
.tap-policy-label {
	font-family: 'Lato', sans-serif;
	font-weight: 700;
	font-size: 24px;
	line-height: 36px;
}

/* --- Display headings, measured against the old build at desktop width ----
   The old site draws every page's intro heading and every section heading at
   44px. Two UIkit classes do it: uk-heading-small (44/50) for intro headings
   and case study subject lines, uk-heading-medium (44/48.4) for section
   headings and the "Case Study - X" line on a teaser. Both are weight 700.

   .tap-display-small marks all of them in this build, but carried no styles,
   so the size came from Blocksy's own scale: an h1 landed on 44/50 and was
   right by accident, while every h2 and h3 fell to 38.5/42.35 at weight 400.
   Sized here so the mark means the same thing whatever heading level it sits
   on.

   Measure the old site at 1440px or wider. UIkit steps these values down
   below its @m breakpoint (960px), so a narrow window reports 28px and makes
   the two builds look further apart than they are. */
.tap-display-small {
	font-size: 44px;
	line-height: 50px;
	font-weight: 700;
}

.tap-teaser-cover .tap-teaser__eyebrow {
	font-size: 44px;
	line-height: 48.4px;
	font-weight: 700;
}

/* The strapline under it is uk-text-large on the old build: the body font at
   regular weight, not bold. This build had the two the wrong way round, with a
   smaller eyebrow over a bolder strapline. */
.tap-teaser-cover .tap-teaser__headline {
	font-weight: 400;
}

/* Learn More on a teaser is uk-button-danger on the old build: solid rust,
   white, body font, title case. Both teaser button implementations are
   pointed at it here, the core Button the homepage uses and the plain .tap-btn
   link on the service pages. The white outline stays everywhere else. */
.tap-teaser-cover .tap-btn,
.tap-teaser-cover .tap-btn-block .wp-block-button__link {
	padding: 15px 30px;
	font-family: 'Lato', sans-serif;
	font-size: 18px;
	font-weight: 700;
	letter-spacing: normal;
	text-transform: none;
	color: #fff;
	background: var(--tap-rust);
	border-color: var(--tap-rust);
}

.tap-teaser-cover .tap-btn:hover,
.tap-teaser-cover .tap-btn:focus-visible,
.tap-teaser-cover .tap-btn-block .wp-block-button__link:hover,
.tap-teaser-cover .tap-btn-block .wp-block-button__link:focus-visible {
	color: #fff;
	background: var(--tap-link-hover);
	border-color: var(--tap-link-hover);
}

/* --- Testimonials -------------------------------------------------------
   Every testimonial on the old site, on the homepage carousel, on the case
   studies and at the foot of each service page, is the same thing: uk-h5,
   which is the body font at 24/36, weight 300, italic, in the brand rust,
   with the attribution under it at 18/24 in the ink colour. This build had
   them at 18/28.8 weight 400 in ink, with the attribution at 14px and faded,
   which read as a caption rather than as a client speaking.

   .tap-cs-quote is left in place for the margins it carries, but no longer
   needs to restate the size. */
.tap-quote p {
	font-size: 24px;
	line-height: 36px;
	font-weight: 300;
	color: var(--tap-rust);
}

.tap-quote cite {
	font-size: 18px;
	line-height: 24px;
	opacity: 1;
}

/* A statement line under an intro, uk-h3 uk-font-primary on the old build:
   the body font at 24/36, bold. Used on the Corteva case study. */
.tap-statement {
	font-family: 'Lato', sans-serif;
	font-size: 24px;
	line-height: 36px;
	font-weight: 700;
}

/* --- Amends from Rob, 11 November 2026 ----------------------------------- */

/* "Some H2's have --theme-letter-spacing: 1.4px; can they all be 0px."
   The value comes from Blocksy's own heading typography in global.css, which
   is regenerated from the customiser, so it is overridden here rather than
   edited there. H1 carried a stray 0.175px for the same reason. */
h1 { --theme-letter-spacing: 0em; }
h2 { --theme-letter-spacing: 0em; }

/* "Can all the lines under the titles be thicker." 2px to 4px. */
.tap-rule {
	border-top-width: 4px;
}

/* "Lose the scroll bar and arrows on the client logos."
   The strip keeps scrolling by touch and trackpad; it just loses the chrome,
   and gains the autoplay the old Widgetkit slider had so that it still reads
   as something that moves. */
.tap-logos .tap-carousel__track {
	scrollbar-width: none;
	-ms-overflow-style: none;
}

.tap-logos .tap-carousel__track::-webkit-scrollbar {
	display: none;
}

.tap-logos .tap-carousel__btn {
	display: none;
}

/* "There is a big gap at the top of blog pages. Can you half that."
   130px between the Blog heading and the first card, from the title block's
   bottom padding plus the archive container's top padding. Roughly halved. */
.blog .tap-section--tight,
.archive .tap-section--tight {
	padding-bottom: 10px;
}

.blog .ct-container[data-vertical-spacing],
.archive .ct-container[data-vertical-spacing] {
	padding-top: 20px;
}

/* "Contact page title needs moving up." The old build used uk-section-small
   here, which is half the usual section padding. */
/* The hero and the section are both plain divs, so :first-of-type matches the
   hero, not the section. The adjacent sibling selector is the reliable one. */
.page-id-106 .tap-hero-cover + .tap-section {
	padding-top: 35px;
}

/* --- The single post right rail ------------------------------------------ */
/* Photo, name, note, rule, search, categories, top to bottom, as the old build
   had them. Sharing is not here; it sits under the article. */
.ct-sidebar .tap-rail__box,
.ct-sidebar .widget,
.ct-sidebar ul,
.ct-sidebar form {
	text-align: left;
}

.tap-rail__box {
	margin: 0 0 24px;
}

/* The source files are 300px wide and there is no larger one, so the photo is
   capped rather than stretched to the 348px rail. */
.tap-rail__photo {
	display: block;
	width: 100%;
	max-width: 300px;
	height: auto;
	margin: 0 0 16px;
}

.tap-rail__name {
	margin: 0 0 8px;
	font-family: 'Lato', sans-serif;
	font-size: 24px;
	line-height: 36px;
	font-weight: 700;
}

.tap-rail__bio {
	margin: 0;
	font-size: 18px;
	line-height: 24px;
}

/* The old rail closed the author block with a black rule the width of the
   column, the same weight as the rules Rob asked to thicken. */
.tap-rail__rule {
	width: 100%;
	margin: 0 0 24px;
	border: 0;
	border-top: 4px solid var(--tap-ink);
	opacity: 1;
}

.tap-rail__cats {
	margin: 0;
	padding: 0;
	list-style: none;
}

.tap-rail__cats li {
	margin: 0 0 10px;
}

.tap-rail__cats a {
	font-family: 'Lato', sans-serif;
	font-size: 18px;
	line-height: 28px;
	font-weight: 700;
	text-decoration: none;
}

.tap-rail__cats a:hover {
	text-decoration: underline;
}

/* The search box: a plain bordered field, as on the old rail. */
.ct-sidebar .wp-block-search {
	margin: 0 0 28px;
}

.ct-sidebar .wp-block-search__inside-wrapper {
	border: 2px solid var(--tap-ink);
	padding: 0;
}

.ct-sidebar .wp-block-search__input {
	border: 0;
	background: transparent;
	padding: 10px 12px;
	font-size: 18px;
}

.ct-sidebar .wp-block-search__button {
	margin: 0;
	padding: 0 14px;
	background: transparent;
	border: 0;
	color: var(--tap-ink);
}

/* --- Single post: close the gap above the title -------------------------- */
/* Blocksy wraps the post title in .hero-section with 140px of padding above
   it, which left the article beginning 113px BELOW the rail beside it. The old
   build used that space for a small "Blog" label; this build has no label, so
   the space is just a hole. Title and rail now start together. */
.single-post .hero-section {
	padding-top: 25px;
}

/* The old post title is uk-heading-small, 44/50, not Blocksy's 30px. */
.single-post .entry-header .page-title {
	font-size: 44px;
	line-height: 50px;
}

/* The old build drew a rule under the title before the article began. Done as
   a pseudo-element so there is nothing in the markup for an editor to delete. */
.single-post .entry-header::after {
	content: "";
	display: block;
	width: 300px;
	max-width: 100%;
	margin: 22px 0 0;
	border-top: 4px solid var(--tap-ink);
}

/* --- Contact page: air under the separator ------------------------------- */
/* The rule is the last child of .tap-intro, and core's
   ":root :where(.is-layout-constrained) > :last-child { margin-block-end: 0 }"
   beats .tap-rule's own margin, so the columns butted straight up against it. */
.tap-intro > .tap-rule:last-child {
	margin-block-end: 40px;
}

/* Footer social links (Rob's handles, 12 Nov 2026) */
.tap-social {
	margin-top: 14px;
}
.tap-social a {
	display: inline-block;
	margin: 0 18px 4px 0;
	text-decoration: none;
	font-weight: 700;
}
.tap-social a:last-child {
	margin-right: 0;
}
.tap-social a:hover,
.tap-social a:focus-visible {
	text-decoration: underline;
}
