Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
Halo 是一个活跃的开源建站工具项目，面向博客、知识库、企业官网和在线商城等场景。仓库很大，Fork 量和 Star 数都很高，最近仍在频繁提交，说明社区和维护都很活跃。
Choose this fork if you want Halo as a customizable base with extra editor, localization, and extension work, and you can tolerate substantial upstream drift. Prefer upstream if you want the safest path for long-term upgrades, documentation, and compatibility.
Choose this fork only if you need its legacy blog-centric customizations and are willing to maintain a heavily outdated codebase. If you want current Halo features, active support, or lower maintenance risk, upstream is the better choice.
Adopt this fork only if you specifically need its legacy blog/comment/export tweaks and are comfortable staying on an old, heavily diverged branch. For most new users, active upstream Halo is the better choice because this fork is stale and materially behind current features and maintenance.
Prefer upstream unless you specifically need the fork's small set of custom runtime/admin behaviors and are prepared to maintain a legacy codebase yourself.
Choose this fork only if you need a legacy Maven-based Halo variant and can tolerate heavy drift from upstream. For new installs, upstream is the safer choice because this fork is far behind and likely missing current capabilities and fixes.
Choose this fork only if you need the legacy codebase and its existing customizations. For new installs or long-term maintenance, upstream is the better choice because this fork is stale and materially behind.
Choose this fork if you need Halo plus custom release and deployment automation and are willing to absorb upstream merge work. Choose upstream if you want the newest Halo runtime, UI, and ecosystem changes with less maintenance burden.
Choose this fork only if its custom editor, plugin, or attachment workflows match a real need and you can absorb ongoing merge work. If you want the most stable, current Halo experience, upstream is the safer default.
Prefer the upstream project if you want a current, broadly supported Halo deployment. Prefer this fork only if its attachment and extension workflow changes are specifically valuable and you are willing to own the upgrade burden.