Projects & Research

A collection of research documents, data visualizations, and software systems.

advaitachandra.in

Status: in-progress | Categories: technology

The website you are looking at right now. Built as a learning project to understand modern front-end development: component architecture, responsive design, data persistence with Supabase, and deployment via GitHub Pages. It is also the container for everything else on this site — the research, the photography, and the writing.

Role: Design, development, and content — everything on this site is my own work.

Tools: React, Vite, Tailwind CSS, Framer Motion, Supabase, GitHub Pages

Methodology

  • Built incrementally: Started with static pages and layered in interactivity, animation, and data persistence as I learned each piece.
  • Content-first approach: The design serves the content — editorial typography, clear hierarchy, and honest labelling of what each piece of work actually is.

Stated Limitations

  • This is a student project, not a professional web application. The code reflects learning in progress.
  • The Supabase integration is still being refined — some admin panel features may not yet reliably round-trip to the public site.
  • The site is a living document and will change as I learn more.

Terrorism in India: Data Visualization, 1947–2026

Status: completed | Categories: data, research

A data-visualisation project examining terrorism in India across 1947–2026. The bulk of the work was not plotting but reconciliation: available records for this subject are uneven across decades, and different organisations define and count incidents differently. Rather than flattening that into one authoritative series, the project treats the gaps and the disagreements as findings in their own right.

Role: Sole researcher — question framing, source comparison, data preparation and visualisation.

Tools: Python, matplotlib

Methodology

  • Framed the question narrowly: Decided in advance what the visualisation would and would not attempt to show, so that gaps in the data would be visible rather than smoothed over.
  • Compared sources instead of choosing one: Where figures conflicted, both were kept and the conflict noted, rather than adopting whichever series was most complete or most convenient.
  • Documented coverage gaps explicitly: Periods with sparse or inconsistent records were marked as such, so that an absence of recorded incidents is not read as an absence of incidents.
  • Visualised with matplotlib: Built the charts in Python so that every transformation between source data and final figure stayed inspectable.

Stated Limitations

  • Records of this kind are incomplete and inconsistent, particularly for the earlier decades of the period.
  • Organisations define and count incidents differently, so figures drawn from different sources are not directly comparable.
  • The project maps what the available data shows. It does not establish causes, and no causal claim should be read into it.
  • No conclusions are published here. The visualisations are exploratory, not an argument.

Osho: A Research Document

Status: completed | Categories: research, writing

A comprehensive research and writing project about Osho, written in a documentary register. The subject is unusually contested — accounts of his life, teaching and organisations differ sharply depending on who is telling the story. The document is organised around that problem: it records competing accounts side by side and marks where the record is disputed, rather than presenting a single settled narrative.

Role: Researcher and writer — source reading, structuring and drafting.

Tools: Source reading and note-taking, Long-form drafting

Methodology

  • Compiled from available published sources: Worked from material that is publicly available, keeping a note of where each account originates.
  • Structured it as documentary narrative: Used a chronological documentary form because it makes the sequence of events, and the points where accounts diverge, easier to follow.
  • Separated record from interpretation: Kept documented events distinct from reading and interpretation, and flagged claims that are contested between sources.

Stated Limitations

  • Accounts of Osho's life and organisations are genuinely contested. This document records the competing versions; it does not adjudicate between them.
  • It is a research and writing exercise. It is not peer-reviewed, and it is not published scholarship.
  • No public version exists yet, so the document cannot currently be linked or cited.
  • Working from published secondary material means inheriting whatever biases those sources carry.

Worksheet Generator

Status: concept | Categories: concepts, education, technology

A product design for generating school worksheets and related documents. The central idea is a strict separation of concerns across four layers, so that what a worksheet says, how it is arranged, and how it is styled can each change without disturbing the others — and so that automated generation remains genuinely optional rather than load-bearing. This is a design document and architecture, not software.

Role: Product design and system architecture — concept only.

Tools: System design, Written specification

Methodology

  • Content layer: Holds the actual subject matter — questions, prompts, answers and metadata — as structured data, with no assumptions about how it will look on a page.
  • Layout Engine: Decides how content is arranged into a printable page: ordering, spacing, pagination and how items flow when they do not fit.
  • Template Engine: Supplies reusable presentation formats — worksheet styles, headers, question patterns — so a new document is a template choice rather than a rebuild.
  • Optional AI layer: An assistive layer that could draft or vary content. Deliberately optional: the design requires the other three layers to work completely without it.

Stated Limitations

  • This is a design, not a product. There is no prototype, no application and no code.
  • The four-layer separation is untested. Whether the boundaries survive contact with real requirements is exactly what a prototype would reveal.
  • The layout problem is the hardest part and the least specified — real pagination and overflow behaviour are where designs like this usually break.
  • No claim is made about usefulness in a classroom, since it has never been used in one.