Gorka Molero

Creative technologist / AI engineer
Remote, location-independent Email GitHub EngineeringAgentsDesign SystemsCreative WorkBefore AIMusic

Live · data product

Datomania

A public-data product around information that should be easier to access: provenance modeling, Representantes records, API/export routes, and methodology.

Public on gorkamolero · 1,257 records · API / export surfaces

Problem

Public-interest data often technically exists, but is hard to browse, verify, export, or use in software. A useful civic-data product needs more than a table: it needs provenance, methodology, API access, and a product surface that makes the data understandable.

What I Built

Datomania is documented as a public-data project around information that should exist in Spain. The rewritten README frames it around the Representantes dataset, 1,257 parliamentarians, provenance modeling, public API/export routes, architecture, methodology, status, and portfolio context.

  • Data productPublic-interest dataset, browsing surface, methodology, and usability framing.
  • ProvenanceSource-aware modeling so records can be inspected rather than blindly trusted.
  • Developer surfaceAPI/export routes make the data useful beyond the UI.

System Architecture

Datomania civic data product diagram with public sources, provenance model, Representantes records, product surface, API routes, methodology, verification, and evidence needs.
Public-safe product diagram. It captures the data-product shape: public sources, provenance modeling, records, UI, API routes, methodology, and verification.
Datomania Representantes dashboard showing 642 parliamentarians, chamber counts, education summary, and a hemicycle visualization.
Local product screenshot from the Representantes dashboard. It shows the civic-data surface, metrics, legislature switcher, and visualization layer.
Datomania API documentation showing public endpoints, available datasets, base URL, and query parameters.
API documentation screenshot. Datomania exposes the dataset through public endpoints and export routes rather than keeping the data trapped in the UI.
Live Datomania homepage showing the DATOMANIA title, open-source status, auditable code, JSON CSV API data, MIT license, and GitHub link.
Live-site screenshot from https://datomania.info. It proves the public product is reachable, open-source positioned, and linked to inspectable code and data surfaces.

Technical Decisions

  • Frame the project around public usefulness instead of only data collection.
  • Make provenance and methodology part of the product surface.
  • Expose API/export routes so the dataset can support downstream workflows.
  • Keep the README explicit about architecture and verification, not just a product description.

What This Proves

Datomania shows product judgment in a less glamorous but highly practical domain: turning messy public information into a browsable, inspectable, reusable data product with clear provenance and engineering discipline.

Public Evidence

  • Public repo: gorkamolero/datomania.
  • Live public site: https://datomania.info.
  • README rewritten and pushed.
  • pnpm lint, pnpm test:run, and pnpm build passed.
  • Product, table, API-doc, and live public-site screenshots captured.
  • Stats/export proof — available on request.

Review Boundary

Confirm source terms, methodology notes, and exported fields before using live-site screenshots in public application materials.

Open live site Open repo