wvvvw/reveal.js
stale
significant_divergence
Selected Choose this fork only if webcam gesture recognition is the core requirement. For most adopters, current upstream reveal.js is the safer choice because this fork is extremely stale and likely missing many modern capabilities.
dimroc/reveal.js-threejs
stale
significant_divergence
Prefer this fork only if your goal is a legacy WebGL/Three.js presentation showcase. For general reveal.js adoption, upstream is the better choice because this fork is old, highly divergent, and likely missing modern framework improvements.
nguyenkha/web1-2017
stale
significant_divergence
Adopt this only if you want a course-oriented PHP training site with sample backend workflows. Do not adopt it if you need reveal.js itself or an actively maintained presentation framework.
chubbc/manim_slides
stale
significant_divergence
Choose this fork if you want a manim/talk-specific presentation base with mobile-friendly polish and you do not need current upstream reveal.js features. Avoid it if you want an actively maintained, general-purpose reveal.js foundation.
emmabostian/how-to-become-a-web-developer
stale
significant_divergence
Choose this fork if you want a finished, opinionated web-development presentation. Do not choose it if you need an up-to-date, extensible reveal.js base, because it is heavily customized and far behind upstream.
cloudogu/reveal.js-docker
active
significant_divergence
Prefer this fork if you want reveal.js packaged as a Docker-first, branded, ops-friendly presentation app. Prefer upstream if you need the latest framework features, broad plugin compatibility, or a cleaner base for your own customization.
jlengstorf/reveal.js-jade
stale
significant_divergence
Choose this fork only if Jade/Pug templating is the main requirement. Otherwise upstream is the better default because this fork is materially behind and appears to trade away recent reveal.js work for a specialized authoring pipeline.
peterdoherty01/reveal.js-typed
stale
significant_divergence
Choose this fork only if the typed text effect is the primary requirement and you are comfortable inheriting an old, heavily diverged Reveal.js base. For anything broader, upstream Reveal.js is the safer starting point.
girldevelopit/reveal.js
stale
significant_divergence
Choose this fork if you want a Girl Develop It-specific presentation theme and can tolerate an old codebase; avoid it if you need current Reveal.js capabilities, modern tooling, or an easy upstream sync path.
handsomeyang/reveal.js
stale
significant_divergence
Choose this fork only if logo branding is the core requirement and you are comfortable owning the upstream gap. For most adopters, upstream reveal.js is the safer base because this fork is very old and likely missing many later fixes and features.