Portfolio

Some Projects I’m Proud Of

A gallery of my prior entrepreneurial, software, design, and data work.

Research tooling

Grammar Atlas

A prototype workspace for annotating syntactic alternations, feature bundles, and field notes across small corpora.

Role: Product architecture, annotation model, and interface prototype.
Methods: Corpus notes, feature taxonomies, search filters, and exportable research records.
Use: Replace this with screenshots, links, collaborators, dates, outcomes, and supporting documents.

This modal is meant to feel like a compact case-study card: enough context for a visitor to understand the project without leaving the portfolio page.

Data product

Civic Metrics Studio

Data pipelines, reporting surfaces, and editorial dashboards designed for clarity rather than performative complexity.

Role: Data modeling, interface design, stakeholder translation, and reporting workflow.
Stack: SQL, Python, JavaScript, scheduled imports, and lightweight analytics surfaces.
Outcome: Swap in measurable outcomes, screenshots, testimonials, or links to public artifacts.

The project detail view gives technical work a narrative rhythm without turning each portfolio card into a separate page.

Product system sketch with release ledger

Entrepreneurship

Product Foundry

Early company work spanning prototypes, brand systems, fundraising artifacts, hiring loops, and launch operations.

Role: Founder, product lead, technical translator, and operator.
Scope: Discovery, prototypes, launch planning, brand systems, process design, and hiring loops.
Artifacts: Add decks, screenshots, investor materials, press, product demos, or archive links.

Use this space to describe what was difficult, what was built, and what the work taught you.

Interface design

Archive Interface

A catalog and note-taking interface for textual collections, inspired by index cards, marginalia, and critical apparatus.

Role: Information architecture, interaction design, and editorial workflow planning.
Materials: Textual collections, notes, metadata, tags, annotations, and reference trails.
Next edit: Replace this with real project context, collaborator notes, and final screenshots.

This is designed for the sort of work that benefits from careful explanation rather than a loud case-study page.

Shan Singh Tinna

Writing on language and computing, with a continuing practice in software, design, and data systems.