Bárbara M. Peres · Full-Stack Developer & AI Engineer, Portugal
The interactive version of this page did not load. Reloading usually fixes it. Otherwise the links below still reach me.
Interactive Data Visualisation · 2025
Does recipe volume translate into culinary prestige?
An interactive data-visualisation website about one question: does the number of recipes a country produces correlate with its presence in elite world cuisine? Six D3.js views over five stitched datasets, among them a draggable globe shaded by recipe volume, a world map of the top restaurants filtered by year, a circle-packed ingredient hierarchy and a chord diagram of cuisine relationships.
D3.js · HTML/CSS · GitHub Pages · Munzner What/Why/How · Chord Diagram · Circle Packing · Edge Bundling
The brief was open: build an interactive data-visualisation website. We narrowed it to a question that no single dataset answers. Does the volume of recipes a country produces track its standing in elite world cuisine? Recipe counts and fine-dining presence come from different sources at different granularities, and the country names do not match.
Team of four; my part was the D3 implementation and the visual design. We stitched five datasets onto a common country key, then designed the six views against Munzner's What/Why/How framework so each one answers a different question rather than restating the last. Recipe volume went to a draggable orthographic globe shaded by count, fine-dining presence to a world map of the top restaurants with a year slider, ingredient categories to a circle-packed hierarchy, ingredient co-occurrence to a radial edge-bundling diagram, and the relationships between cuisines to a chord diagram. All of it is D3.js on plain HTML and CSS, without a charting library, hosted on GitHub Pages.
The site is live and the six views hold together as a single argument. The answer to the question is no. Volume and prestige pull apart for several countries, and the globe and the restaurant map show it side by side. Each view keeps its own interaction state rather than sharing a selection, which is the first thing I would change.