Developer workflow
A presentation you can version, inspect, and keep building.
Slaidev turns a source-grounded brief into a Slidev deck without turning the result into a black box. Keep each generated version, inspect its workspace, and download the files you want to keep editing locally.
Keep the source in reach
AI can start the deck. Your team can still own the project.
Version history for the presentation work itself.
Slaidev keeps generated presentation versions in the project, so a revision starts from an earlier deck instead of replacing the only copy. It is presentation version history—not a substitute for your team's Git workflow.
Download the files you want to keep editing.
In a committed version's workspace, you can inspect and download individual source files, authored slides, public assets, and build output. That makes it practical to takeslides.md and the assets you need into a local project.
Put the source under your own version control.
Slidev decks are Markdown-based source. After downloading the deck and its assets, developers can commit them to Git, use their usual review process, and make focused changes without rebuilding the presentation in a visual editor.
Self-host the deck on your terms
A Slidev build is a static web application.
Slaidev publishes a static deck for sharing. If you take the downloaded Slidev source into your own project, you can self-host the static SPA with the hosting provider or internal infrastructure you choose.
$ slidev build slides.md --out dist
# Deploy the generated dist directory to a static hostSlidev features for technical presentations
Make the live explanation easier to follow.
A Slaidev deck is Slidev source, so you can add the features that fit the talk instead of being limited to a fixed slide editor.
Presenter notes that keep pace
Write presenter notes in the slide source and use click markers to keep the right section highlighted as the presentation advances.
Code that can teach
Use line highlighting, Monaco-powered code editors, and Magic Move transitions to make an implementation change easier to follow.
Diagrams and math in the source
Add Mermaid or PlantUML diagrams and KaTeX math directly in the deck instead of exporting images every time the model changes.
Static hosting when you need it
Build the deck as a static single-page app, then deploy the output to the hosting setup your team already uses.
Learn the format
Go deeper with the official Slidev documentation.
Keep the momentum