Release Log

A round of copy and search fixes across the site, a rebuilt admin screen for page titles and descriptions, and new checks that tell us when the published site has fallen behind what editors have written.

• FixedA closing link on the blog post about preparing to hire a software development firm sent readers to our Clutch review profile instead of the contact page, at the moment they were ready to get in touch. It now goes to contact.
• FixedAn old share button on a 2015 post about agile and contracts had been broken by the original site import and ran into the surrounding sentences. It has been removed and the paragraph reads normally again.
• ImprovedThe What We Do page no longer repeats itself. A second summary paragraph sat directly beneath the page introduction, and the heading has been reworded.
• AddedOur LinkedIn, Facebook, Instagram and YouTube profiles are now published in the site's structured data, so search engines can connect the site to our official accounts.
• ImprovedThe admin screen for page titles and search descriptions has been rebuilt as a single table, one row per page, with subpages indented under their parent. Titles and descriptions are readable on the row and edited in a pop up, and each row says clearly whether the page's content is locked.
• AddedA new report tells us when the published site is serving older copy than editors have written, and says which pages and which way round. Before this, the only way to find out was to check by hand.
• FixedA safety check that was meant to watch the live site's configuration was reading the staging site's instead, and had been doing so on every run. It now reads the one it names.

The industries pages get a clearer Business Strategy section, read as a single sheet rather than a stack of accordions, with the healthcare risks laid out as a ruled table. Search titles and descriptions are rewritten across the blog, portraits on testimonials and case studies are larger, and a round of link text mangled by the old WordPress import is repaired. Behind the scenes, copy changes now show up in review before they ship.

• ImprovedSearch titles and descriptions across the blog have been rewritten, so posts read better in search results and fewer titles get cut off. Five titles that ran past the limit once the site adds "| Chromedia" have been shortened.
• ImprovedCase study pages now carry their own search description. They used to reuse the card teaser, which meant editing one silently changed the other.
• ImprovedPortraits on testimonials and case studies are larger, and no longer sit smaller than the quote they belong to.
• ImprovedSmall images such as portraits and client logos no longer request a full-size version from the image service. The page asks for the size it actually shows.
• FixedLink text on older blog posts that the WordPress import had run together, for example a case study name repeated inside its own link. Eighteen were found across the posts and twelve repaired; the link destinations were left untouched.
• FixedA contact link on one blog post that rendered as nothing at all, so there was no way to click it.
• FixedFull stops that sat inside a link rather than after it, so a sentence ended in the middle of the link.
• FixedThe dark previous and next arrows on the logo strip render as circles again.
• AddedChanges to page copy are now shown for review before they ship. Every page's wording is recorded, and an edit that was not intended shows up as a difference rather than going unnoticed.

A new Channel Partnership Program page, Microsoft sign-in for editors alongside Google, and a new Pages screen in the admin console for editing the titles and descriptions that appear in search results. Also a design pass across the industries pages, and a fix for the release log describing a version as unreleased after it had already shipped.

• AddedA Channel Partnership Program page, linked from the footer.
• AddedA Pages screen in the admin console for editing the title and description each page shows in search results. Those two fields were stored but had no way to be changed, so editing them used to need a developer and a deploy.
• AddedMicrosoft sign-in for editors and admins, alongside the existing Google sign-in.
• AddedPer-page edit locks, so a page that is a record rather than marketing copy can be protected from editing. The release log ships locked.
• AddedAn llms.txt file, so AI crawlers can find a description of the site and its main pages.
• ImprovedCopy across the industries, services and homepage sections is up to date with the wording approved in the editor. Those pages had been running behind.
• ImprovedThe industries pages: the architecture and MVP sections are laid out as ruled tables, and the icon card grids are now accordions.
• ImprovedTestimonials now carry a clearer attribution column, with the call to action under the quote rather than beside it.
• ImprovedWhy Work with Chromedia is one shared record, so editing it once updates every page that shows it.
• ImprovedThe admin page list is grouped the way the site navigation is, instead of alphabetically, so a page is where you would look for it.
• ImprovedClient logos are now named for screen readers instead of being announced as unlabelled images.
• ImprovedLinks from the blog to the main site go straight to their destination instead of passing through a redirect.
• ImprovedLayout and spacing corrections across the feature grids, cards and tables.
• FixedThe release log no longer describes a version as unreleased once it has shipped. Release dates are taken from the deploy that delivered each version, rather than being written by hand afterwards.
• FixedThe build stamp in the footer links to the matching entry in this log.
• FixedA retired industries address now redirects permanently rather than temporarily, so search engines follow it to the current page instead of holding on to the old one.
• FixedThis release log is no longer offered to search engines.
• FixedSearch engines can now read the company location from the site's business information. A street address, phone number and social profiles are still to come.
• FixedSaving an edit can no longer be blocked or reported as failed because of a problem writing the edit history.
• FixedImages on the Channel Partnership page now reach the live site.

This release log can now be corrected the same way any other page is edited, so a wrong entry no longer needs a full release to put right. Two problems in the page editor are fixed, and the automatic checks that run after every deploy can see the staging site again.

• ImprovedThis release log is now ordinary page content. A wrong or unclear entry can be corrected in the editor, instead of costing a code change and a full release to fix a few words.
• FixedOpening the editor no longer flashes a “What is your name?” box across the page. Your name comes from the Google account you signed in with, so the page no longer asks for something it already knows.
• FixedOn the rare occasion that box does appear, its Continue button now works. It had been doing nothing at all, which left anyone who reached it stuck on a screen with no way out.
• FixedThe checks that run after every deploy can sign in to the staging site again. Since staging started asking visitors to sign in, they had been looking at the sign-in screen instead of the pages, so the staging site that stakeholders review was going out unverified.
• ImprovedReleases are quicker to go out: the steps of a deploy now run alongside each other rather than queuing up one at a time.
• ImprovedThe parts of the sign-in and editing code that must not be changed casually are now written down, with a note of which ones a test actually protects.

A fix to this page itself: it was showing the version the site is running as “not yet released”, which was never true once you could read it here.

• FixedThis release log no longer describes the version the site is running as unreleased. It works out what has shipped from the running site rather than waiting for someone to fill in a date by hand.
• ImprovedA check now confirms after every deploy that this page agrees with the version the site reports, so the two cannot drift apart unnoticed again.
• ImprovedA site-content check was quietly examining the previous version of the site rather than the one just published, so it could pass while the newly published pages went unexamined.

Mostly work on the admin console and the release pipeline: a lower-access role for people who only need visibility, tighter limits on who can grant administrative access, and a few checks that now catch mistakes before they reach the site.

• AddedA read-only viewer role for the admin console, for people who need visibility without full administrative access.
• AddedAn automatic check that catches a missing release note before a deploy ships.
• FixedA site-content health check that had silently never worked, now catching real problems instead of nothing.
• AddedGoogle Search Console verification for the site.
• FixedTwo ways an administrator could end up holding more access than intended have been closed.
• ImprovedThe admin activity log opens faster: the details of a change are now loaded only when you open that change, rather than all of them up front.
• ImprovedInvitation emails now describe the access the person is actually being given, rather than assuming everyone is a full administrator.

Mostly behind-the-scenes work on how the site is deployed, after two releases in a row failed to go out. One visible improvement came with it: pages are now prepared as soon as a deploy finishes, so the first person to open one is no longer the one who waits.

• FixedImages on a freshly deployed page are now prepared ahead of time, instead of the first visitor waiting for them to be generated.
• FixedThis release log listed a version that never actually reached the live site. It now shows the version that did.
• ImprovedDeploys are more reliable: the release process was doing the same heavy step twice and running out of memory, which is why the two previous attempts failed.

Version tracking

The site now tells you which version it is running. The footer shows the environment and the release, and every version has a permanent entry here.

• AddedA version stamp in the footer, showing the environment and the release it is running.
• AddedThis release log, with a permanent entry for every version.
• AddedAutomatic version numbering in the deploy pipeline, so a routine deploy needs no manual step.

Copy across the site was reconciled against the approved 2026 source documents, and several readability problems in the card and accordion styles were cleared up.

• AddedNew mission-control hero artwork on the Technologies page.
• ImprovedClient quotes on case studies now read as pull-quotes rather than body copy.
• ImprovedPage copy reconciled against the approved 2026 source documents, including a section that had been cut and a segment that had been dropped in error.
• FixedOutcome bullets and body type were hard to read on the teal accent cards.
• FixedHollow black buttons now hover the same way every other hollow button does.
• FixedRemoved placeholder testimonial quotes, which carried invented attribution, from two Industries pages.

A new Contact page, comparison cards across the decision-making pages, and the first full pass restoring page copy word-for-word from the client source documents.

• ImprovedThe Contact page is now a split-screen hero, with the form sitting alongside the copy rather than below it.
• Improved“Who should you hire?” and Flutter vs. Native now use comparison cards, with the decision markers drawn as icons instead of emoji.
• ImprovedThe hiring process page moved to two-column phase sections with cleaner cards.
• ImprovedQuieter form field borders that darken on focus.
• FixedThe message field and the password-manager icon no longer shift the form layout.
• FixedPage copy restored word-for-word from the client source documents, with each section rendering exactly once.

Page copy moved out of the code and into the content system, so it can be edited without a code change.

• ImprovedTestimonials became a single-client slider, with aligned calls to action and case study covers.
• ImprovedComparison cards on the custom software page sit under their heading, and the three-way comparison is back.
• ImprovedPage copy now lives in the content system rather than in the code.
• FixedThe MVP page carried a duplicated section, and the Industries call-to-action labels ran too long.

A significant speed-up: pages had been arriving as an empty shell and assembling themselves in the browser. They now come down fully rendered.

• ImprovedPages arrive fully rendered, so text and images appear straight away instead of after the page finishes loading its code.
• ImprovedHero images are prepared ahead of time on every page, not just the homepage.
• FixedContent no longer jumps around while the page loads.
• FixedCard action buttons line up along the bottom, cards without an image no longer look empty, and hover contrast on the info state is readable.
• FixedThe custom software page opened with intro paragraphs that repeated its own heading.
• ImprovedStricter automated checks before a release can go out, including per-page assertions and a guard against changes slipping in during a merge.