h5bp/html5-boilerplate

Choose this fork only if you specifically need its legacy Apache/build defaults and are comfortable inheriting a very old codebase; otherwise upstream is the safer, more current foundation.

Choose this fork only if you specifically want a minimal, legacy-style starter. For most new projects, upstream is the safer choice because it is actively maintained and much more current.

Prefer upstream unless you specifically want a frozen snapshot; this fork offers no visible extra capability, but it is materially behind on maintenance and likely to cost more to adopt and keep current.

Choose this fork only if you need its legacy Apache/docs customization and are prepared to maintain a 2012 snapshot. For new projects or active maintenance, upstream is the better default.

Prefer this fork only if you need its exact legacy behavior or are maintaining an older codebase built around it. For new projects, upstream is the better choice because this fork is materially stale and far behind current maintenance.

Choose this fork only if the workflow change in `.github/workflows/build-dist.yml` matches your release process. Otherwise, upstream is the better default because it is much more actively maintained and has far more recent fixes.

Choose this fork only if Yii integration is the point. For a general-purpose web starter, upstream is much better maintained and more current; this fork is mainly useful as an old Yii-specific scaffold.

Choose this fork only if you want a legacy WordPress theme starter with its built-in admin and styling tweaks. If you want a current, broadly maintained front-end baseline, upstream HTML5 Boilerplate is the better fit.