Skip to content
Selected work / 03MOON SHERPA / LABS

Austin Texas Things

Austin stories, with the city’s live data underneath

  • Content · Civic Data
  • Our contribution: City guide, public-data integrations & interactive tools
  • Reviewed September 2026
6Interactive city tools
48ZIP codes in civic comparisons
USGSLive creek gauge source
MDXStories with data components
01 / The brief

Make a growing city easier to understand.

Back to the portfolio

Austin Texas Things pairs local stories with information readers can explore for themselves. A restaurant has an inspection history. A swimming hole has current gauge conditions. A ZIP code has its own mix of civic requests, businesses, and public records. Shared data components turn those sources into charts, maps, and context throughout the guide.

A local guide is more useful when it helps someone make a decision today: whether the creek is flowing, what an inspection score represents, or how one part of the city compares with another.

That information exists across public portals with different publishing schedules and definitions. It needs to be collected, explained, and presented without implying that a delayed source is real-time.

Writers also need a way to include changing data in a story without manually updating every number in every article.

The working model

AN INVITATION TO EXPLORE

How Austin Texas Things works

From the source / Barton Creek

A real place. A current reading.

Austin Texas Things makes public evidence part of the city’s story. Explore the same USGS gauges behind its Greenbelt tools: actual discharge observations, their timestamps, and a sculptural view of the readings.

AN INVITATION TO EXPLORE

A real place. A current reading.

02 / The approach

How the pieces
came together.

From the underlying data to the moment someone uses the product, each decision serves the work.

  1. 01

    Give stories reusable data components

    MDX lets articles include inspection information, conditions, and other data through shared components. The editorial text and the data source can evolve independently.

  2. 02

    Build six useful destinations

    Dedicated tools cover Greenbelt flows, food inspections, bars and venues, neighborhoods, the economy, and Austin-area ZIP codes. Maps and charts make the same data useful outside an article.

  3. 03

    Compare places with clear definitions

    ZIP profiles combine 311 requests, code cases, restaurant inspections, and mixed-beverage receipts. The comparison table explains its time windows and denominators, and distinguishes missing data from zero.

  4. 04

    Preserve each source’s meaning

    A restaurant’s latest inspection counts once in the ZIP-level score comparison. Mixed-beverage receipts are labeled as alcohol sales reported for tax, not total restaurant revenue or a direct measure of foot traffic.

03 / Inside the product

A closer look at everyday Austin.

Detail / 01

A live answer for the Greenbelt

Current USGS gauge readings give a visit to Barton Creek timely context, with the reading’s time and source visible alongside the condition summary.

Detail / 02

One city, several scales

Readers can move from a venue to a neighborhood or ZIP code, then to the wider economy. The data layer supports each view without reducing them to the same generic page.

Detail / 03

Charts that invite inspection

Sortable comparisons, geographic views, and history charts make the supporting evidence something a visitor can use, rather than a number they have to take on trust.

What this makes possible

  • Live at austintexasthings.com with local stories and six prominent city tools.
  • ZIP comparisons bring civic activity, restaurant scores, and beverage receipts into one explorable view.
  • Source labels and dates give changing public data the context a reader needs.
04 / Under the hood

The right tools.
Thoughtfully connected.

A closer look at the technology and integrations behind Austin Texas Things.

SYSTEM ANATOMY 05 LAYERS
0504030201

A conceptual view of the technology groups. Layer positions do not represent deployment boundaries.

EXPLORE THE BUILD / Austin Texas Things

SELECTED LAYER

Framework

  • Next.js
  • React
  • TypeScript
CONNECTED TO

Austin Public Health · Austin 311 · Austin Code · Texas Comptroller · USGS · FRED

Next in the portfolio / 04

TrueLevel