Flagship portfolio project

MediaScape case study

MediaScape is a computational discourse-analysis platform that explores how media organizations frame the same issue differently.

RoleResearch, product design, frontend prototype
StatusFrontend prototype with mock data
FocusNLP, discourse analysis, data visualization
Topic demoClimate-change media coverage

Research origin

From qualitative linguistics research to a product concept.

The project originated from a linguistics research paper comparing climate-change discourse on Fox News and MSNBC. The paper manually examined conflict framing, thematic framing, episodic framing, attribution framing, lexical choices, rhetorical questions, declarative speech acts, indexicality, audience positioning, and scientific and economic framing.

That manual work produced rich interpretive insights, but it also exposed a scale problem: discourse analysis is slow to apply consistently across large article collections.

Problem and opportunity

Problem

Manual discourse analysis can produce rich insights but is difficult to apply consistently across large collections of media content.

Product opportunity

MediaScape translates a qualitative research framework into an interactive computational workflow that can support larger-scale comparison while preserving transparency and room for human interpretation.

Product strategy

Make comparison legible without pretending the model is neutral truth.

Information architecture

The product separates topic selection, framing scores, lexical evidence, semantic clustering, and methodology notes so users can inspect each layer of analysis.

Design system

The interface uses a calm navy-and-blue palette, thin borders, restrained shadows, editorial headings, and dashboard cards inspired by research tools rather than generic SaaS pages.

Prototype features

The current demo includes topic chips, a static dashboard preview, outlet comparison scores, keyword panels, framing-type bars, a generated SVG narrative map, and methodology disclosures.

Technical architecture

Current prototype and planned system.

Implemented now

  • Existing static portfolio framework
  • HTML, CSS, and JavaScript frontend prototype
  • Reusable section patterns and visualization primitives
  • Local mock data for demonstration topics

Planned backend

  • Python analysis services
  • FastAPI application layer
  • PostgreSQL storage
  • pgvector for semantic search and clustering

Planned analysis pipeline

  • Article collection and source documentation
  • Text cleaning and linguistic feature extraction
  • Frame classification and sentiment analysis
  • Embedding generation, topic modeling, and visualization

Ethical limitations

Framing analysis requires humility.

Framing classification is interpretive, and political framing cannot be reduced to a single objective score.

Sentiment models may misread sarcasm, humor, coded language, or contextual shifts.

Media-source comparisons can reinforce simplistic left-versus-right assumptions if the evidence and sampling methods are hidden.

Search rankings, date ranges, article-selection criteria, and source availability all affect results.

LLM-generated or model-generated analysis requires human validation and transparent confidence reporting.

A framing score is not a factuality score, and neutrality should not be treated as the absence of framing.

Outlets should not be assigned permanent ideological qualities based on a small dataset.

Results should show evidence, uncertainty, source context, and methodology wherever possible.

Current status and next steps

This version is a frontend prototype.

The current page does not analyze thousands of real articles, does not update daily, does not include operational AI classification, and has not been scientifically validated. It is a polished product and visualization prototype designed to communicate the research direction.

Next engineering milestone

Replace mock data with a small documented corpus, build a reproducible annotation schema, and validate the first framing classifier against human-coded samples.

Next design milestone

Design evidence drill-downs so every score can be inspected through representative passages, source metadata, and confidence notes.