BBC

One mapping toolkit behind consistent maps across the BBC

Developers working on BBC sites needed a quick way to add high-quality maps to public websites and the internal intranet, each one consistent with the BBC’s brand. Box UK built a modular mapping toolkit on the BBC’s existing maps, and the BBC introduced it across the organisation.

In short

The BBC wanted developers to be able to put high-quality maps on its public sites and its intranet quickly and easily. Every map had to fit with the BBC’s existing mapping work and reflect its brand.

  • A toolkit of separate modules that developers add or remove for each map
  • Built on the BBC’s existing maps and knowledge database
  • Developed by Box UK using an agile approach
  • Introduced across the BBC, so maps made with it follow the BBC’s design guidelines

Client

BBC

Sector

Media & Entertainment

Customer background

The work was for the BBC’s Future Media and Technology division (FM&T), as it was then. FM&T created and developed online services and applications across the BBC, with a focus on new technology formats, on-demand content and two-way communication with audiences across different devices.

Maps were one of the features FM&T wanted teams to be able to add to both the BBC’s public sites and its internal intranet.

Pen lying on road map

The challenge

The BBC wanted developers to be able to place high-quality maps on its public-facing sites and its intranet quickly and easily. Consistency mattered as much as speed: whatever Box UK built had to work with the BBC’s existing mapping development and reinforce the BBC’s brand and values.

That meant the answer had to build on what the BBC already had.

Our approach

Box UK managed the project using an agile approach. Instead of creating new map data, the team worked with the BBC’s existing maps and its knowledge database, so the toolkit drew on content the BBC already maintained.

The design question was then how to make one tool fit many different kinds of map.

What we built

The Mapping Toolkit is made of separate modules. A developer picks the modules a particular map needs and leaves out the rest, so the same toolkit can serve many different kinds of map.

Because every map is built from the same modules on the same BBC data, maps made with the toolkit look and behave consistently wherever they appear. The modular structure also left room to add new modules as the BBC’s needs changed.

Once the toolkit was built, the BBC could make it the standard way to produce maps.

The outcome

The toolkit gave the BBC an easy way to produce interactive online maps. The BBC introduced it throughout the organisation, so all future maps would follow its design guidelines and give users a common, familiar experience wherever they met a BBC map.

The original case study reports that the toolkit was well received by both the people producing maps and the people using them.

Frequently asked questions

Why build a toolkit rather than individual features?

When many teams need the same kind of feature, a shared toolkit saves each team starting from scratch and keeps the results consistent. The BBC used its mapping toolkit across both its public sites and its intranet.

What makes a component library easy for developers to adopt?

Clear modules that can be added or removed independently, so each team takes only what it needs, and defaults that already meet brand and design standards.

Should a toolkit use your existing data or start fresh?

Use the data you already maintain wherever you can, so there’s only one set to keep up to date. The BBC toolkit was built on the BBC’s existing maps and knowledge database.

How do you keep a brand consistent when many teams build features?

Give teams shared building blocks that already meet the design guidelines, then make those blocks the standard way to do the job. The BBC did this by introducing its mapping toolkit across the organisation.

What this means for your organisation

This story is for organisations where several teams build the same kind of feature, whether that’s maps, forms, charts or booking tools, and the results don’t match. If different teams keep building the same kind of feature in different ways, a shared toolkit can save time and make the experience consistent for your users.

If that sounds familiar, send us a few lines about the feature. We’ll tell you whether a toolkit would pay off.

Client

BBC

Sector

Media & Entertainment

Talk to one of our digital experts

Tom Houdmont

Chief Technology Officer

Do you have a great idea for a project you need support with?

Tom is CTO at Box UK, with 12 years’ experience helping clients deliver ambitious digital products. His background spans Solution Architecture, Front End Development and AI adoption, with particular expertise in high-traffic websites that perform reliably at scale and in embedding AI into delivery practice.

Or call us on 020 7439 1900

Have a project you’d like to discuss?

Give us a call on 020 7439 1900 or fill in the form and we will get back to you.