See the curriculum. Follow the connections.
An interactive explorer for courses, prerequisites and the paths between them.
Explore the live app · Run locally · Architecture · Changelog
50 demo courses. 10 academic cycles. One connected view. Select a course to see what comes before it, what it unlocks and how far its influence reaches. Switch between a curriculum grid, a directed graph and analysis without losing the underlying scenario.
Trama is a demonstration tool, not an official academic plan. Initial relationships are generated randomly; an explicit seed makes a scenario reproducible. Screenshots use seed
2025and show the real application, not design mockups.
| View | What it helps you answer |
|---|---|
| Malla · curriculum grid | Where does a course belong, what does it require, and what can follow it? |
| Grafo · dependency graph | How do prerequisites connect, directly and indirectly? Explore the full plan or a selected course's reach. |
| Análisis · validation and ordering | Does the demo satisfy its rules? Which prerequisites does each course have? What is a valid course order? |
Search by course name or code, inspect dependency paths, reproduce a scenario with its seed, and share a link to a selected course. The interface and course catalogue are in Spanish; search also works without accents.
- Reproducible links: a shared URL keeps the active seed and selected course. Open an example.
- Useful exports: JSON and CSV from the current plan or analysis; PNG for the graph. Exports reflect regenerated data, not an old snapshot.
- Clear relationship states: selected, required, directly unlocked and indirectly reachable courses have distinct treatments.
- Keyboard-aware controls: native dialogs, focus restoration, live status announcements and a text alternative to the graph.
No install step, bundler, backend or account. Clone the repository and serve its files:
git clone https://github.com/trinity-bytes/trama.git
cd trama
python3 -m http.server 8000Open localhost:8000. Use an HTTP server rather than opening index.html directly: the application uses native JavaScript modules.
For a repeatable scenario, open:
http://localhost:8000/?seed=2025&course=6
A fresh visit without a seed generates a new scenario. Reloading a URL that already contains a seed reproduces it. Use the seed control to apply a specific seed or generate new relationships at random.
Trama uses HTML, CSS and native JavaScript modules, with local Cytoscape.js and Dagre for the graph. The active interface does not depend on Bootstrap.
js/
├── domain/ Course catalogue, generation, validation and graph algorithms
├── application/ Explicit state, actions and search selectors
├── ui/ App shell, views and presentation helpers
└── adapters/ Cytoscape integration
css/trama.css Loom tokens, components and responsive layouts
tests/ Domain, state, presentation and browser regression checks
Relationships have a single canonical representation: directed edges from a prerequisite to the course that requires it. Views, analysis and exports derive from that data. Regeneration updates the shared state instead of leaving each screen to manage its own copy.
The Loom interface uses forest-green surfaces, bone for selection and prerequisites, and terracotta for downstream relationships. Schibsted Grotesk headings, quieter course tiles and compact inline stats follow the approved Figma de-slop. Fonts and visual assets are self-hosted.
The website's Open Graph and Twitter large-image cards use the exact 1200×630 export from the Figma Cover page, stored in assets/trama/social-preview.png. Social metadata points to the canonical production URL; no temporary Figma URLs are used at runtime.
Design references and legacy source
PRODUCT.md records product constraints; DESIGN.md records the approved visual system. The Figma examples guided the interface, not the generator's output.
The former MVC source and Bootstrap vendor files remain as inactive historical references. They are not loaded by index.html. Domain regression tests compare seeded output against the original model implementation.
Run the deterministic regression tests with a current Node.js release:
node --test tests/domain/*.test.mjs tests/application/*.test.mjs tests/ui/*.test.mjsThe suite covers seeded generation, validation, graph relationships, state transitions, search and active-view exports.
Browser checks
With the local server running and Playwright available:
TRAMA_BASE_URL=http://localhost:8000 node tests/browser/flows.mjs
TRAMA_BASE_URL=http://localhost:8000 node tests/browser/mobile-accessibility.mjs
TRAMA_BASE_URL=http://localhost:8000 node tests/browser/loom-design.mjs
TRAMA_BASE_URL=http://localhost:8000 node tests/browser/layout-regressions.mjsSet PLAYWRIGHT_MODULE to an existing Playwright module path when it is not resolvable as playwright. Set CHROMIUM_PATH when Chromium is not at /usr/bin/chromium.
The browser checks exercise desktop, tablet and mobile layouts, downloads, graph controls, dialog focus restoration and minimum mobile touch targets. The Loom check also verifies approved colors, loaded display font, asset geometry, borderless tiles and compact stats at 1440, 768 and 390px. Chromium and Playwright are development tools, not application dependencies.
Automated checks do not replace real screen-reader or physical-device testing. Implementation evidence and limitations are recorded in the v3 work log.
Features branch from develop and integrate through Git Flow AVH. Releases merge into main and back into develop. Commit messages follow Conventional Commits in lowercase English.
GitHub Pages publishes the repository root from main to trama.jahattrinidad.com with HTTPS enforced. The root CNAME retains the hostname; its DNS CNAME points to trinity-bytes.github.io, without a repository path. A tag alone does not deploy the site.
Built by Trinity Bytes. Released under the MIT license.
Graph rendering: Cytoscape.js and Dagre. Typefaces: Geist, Geist Mono and Schibsted Grotesk; their licenses are included in assets/trama/.

