Skip to content

Blacklane Contentful Page Builder

Rebuilt Blacklane’s unmaintained Contentful and Next.js marketing site so marketing could publish pages, including live preview and the sitemap.

Line-art illustration of Contentful page-builder blocks driving a Blacklane webpage with uppercase branding, a black hero section and chauffeur imagery

The brief

Blacklane came to me with a marketing site already built in Next.js and Contentful. It had been left on bug fixes. The content models were too rigid for the marketing team to change a page themselves, so what they wanted meant asking an engineer for a code change. Often there was no engineer free, and the work stopped.

Some problems were too tangled to pick off as another bug fix, and there was never enough time for them. Live preview of draft content did not work properly. The sitemap did not. Existing React components had bugs that stayed open.

From August 2023 to January 2024 I worked as a fractional Contentful specialist. The goal was to fix those issues, and to make page editing flexible enough that marketing could ship a page without an engineer.

The work

I rebuilt the Contentful model the site renders from, and the editing workflow around it. An editor creates a page, previews the draft on the real site, and publishes it.

Publishing a page:

  • The entry holds the URL, the language, the canonical, and the hreflang alternates, and whether the page should be indexed. I built the sitemap from those entries, and a noindex page is left out of the hreflang list.
  • The sitemap walks every Contentful entry, not just the first page of the API, so a page published later is not silently missing.
  • Contentful live preview renders the draft before anyone publishes it. Sections can differ by locale, so a translated page shows the local sections when an editor has written them, and the fallback when they have not.
  • A page with an empty noindex field had been returning a 404. It now stays up until someone decides it should not be indexed. A canonical left blank, or filled with spaces, falls back to the page’s own URL.

The sections on a page:

  • I added an FAQ and an expansion panel, which is how long pages stay readable without a new layout for every campaign.
  • Images were loaded straight from Contentful with no optimisation. I added the mechanism that requests an optimised image for the size it is shown at.
  • Markdown and rich text share one set of styles with the rest of the site, so headings, lists, links, and line breaks in the copy match the designed pages.
  • Salesforce forms take their lead source and their thank-you page from the entry. Marketing can point a form at a campaign, and choose where the visitor lands afterwards, without a code change.

What Blacklane could do afterwards

Marketing could create a page, preview the draft, and publish it, without an engineer for each change. The sitemap and the SEO fields sat on the same entry as the copy.

Technologies

  • Contentful
  • Next.js