A data layer turns raw, sourced data into pages that change daily and that nothing else on the web has.

Two data layers are documented here: buydubai.io and benidorm.co.uk. Each case is written at three levels: for someone who does not work with data, for a businessman, and for an engineer.

The two cases

buydubai.io

5.6 / 10 overall, scorecard

buydubai.io is a website about buying property in Dubai. Its pages are built from Dubai Land Department records: who sold what, where, for how much, and when.

benidorm.co.uk

6.6 / 10 overall, scorecard

A website for people from the UK planning a holiday in Benidorm, Spain. It has 752 pages: hotels, bars, restaurants, shows, flights, weather, what a holiday really costs. [V]

Scorecard headline

buydubai.io
5.6 / 10

Best data design we have, with the worst gap between design and what is live.

benidorm.co.uk
6.6 / 10

Better build discipline and clearer pages, but thinner proof of outcomes and no validation gate I could find.

Shared stack and process
6 / 10

The method is real and repeatable. The measurement is not yet there.

Scores judge the system, not the traffic. Scale: 0 = absent, 5 = works but with known holes, 8 = good and proven, 10 = best practice and proven over time. Full scorecard, ten dimensions and the top ten fixes.

Read next