This fork is kept as a reference to an open-slide React/TypeScript framework for 1920x1080 slide decks, static export and presentation workflows.
| Field | Details |
|---|---|
| Repository | open-slide |
| Portfolio category | Forked framework reference |
| Primary stack | React, TypeScript, Vite, slides, static export, presentation framework. |
| Latest release | GitHub Releases |
| Tags | Version tags |
| Owner profile | Luong Hai Long |
| What to Review | Where to Look | Why It Matters |
|---|---|---|
| Technical scope | This README and source tree | Gives a quick, bounded reading path before opening every file |
| Evidence assets | Release page and top-level project files | Shows what can be downloaded or inspected quickly |
| Implementation material | Source folders, scripts, notebooks or design files | Connects the portfolio claim to real project artifacts |
| Version history | Tags and release notes | Makes the repository easier to audit over time |
- React and TypeScript slide-framework reference.
- 1920x1080 deck-oriented workflow.
- Static export and presentation pipeline material.
- Kept as a fork reference rather than original authorship claim.
| Path | Purpose |
|---|---|
.agents/ |
Top-level directory included in the repository |
.changeset/ |
Top-level directory included in the repository |
.claude/ |
Top-level directory included in the repository |
apps/ |
Top-level directory included in the repository |
packages/ |
Top-level directory included in the repository |
AGENTS.md |
Top-level file included in the repository |
biome.json |
Top-level file included in the repository |
CLAUDE.md |
Top-level file included in the repository |
Fork reference. Upstream framework ownership belongs to the original project; this fork is maintained only as study/workspace material.
Luong Hai Long keeps this fork to support slide-workflow experiments and related workspace repositories.
This repository is maintained as part of an English-facing engineering portfolio. Releases and tags are used to preserve reviewable snapshots of the project, including source state, documentation updates and any available visual or report assets.
The README follows an evidence-first style: direct technical nouns, clear project boundaries, release-backed artifacts and no inflated claims beyond what the repository can support.