Hyland is consolidating product documentation into a single platform as part of a 2026 Customer Success initiative. As a result, the Alfresco Docs Site will be deprecated on May 22, 2026, and its content will move to docs.hyland.com.
Why This Is Happening
This change is driven primarily by organizational and operational needs, not by a redesign of the developer experience.
Key factors include:
- centralizing all Hyland product documentation in a single platform
- ensuring infrastructure ownership and security compliance, the current docs.alfresco.com site no longer has internal DevOps support, which creates operational and security risk
- reducing the operational burden of maintaining a separate documentation site
A Note on the URL
You may have seen references to support.hyland.com as the new home for Alfresco documentation. That is partially correct, but there is an important update: on May 22, 2026 (the same date docs.alfresco.com is deprecated) the documentation at support.hyland.com will also move to docs.hyland.com.
This second URL change is necessary because the Hyland Community team will be using support.hyland.com for Community and Technical Support resources. URL redirects will be in place for both transitions, so existing links and bookmarks will continue to route users to the correct content.
What Will Happen to the Content
- All relevant documentation has been migrated to docs.hyland.com
- Existing URLs (both docs.alfresco.com and support.hyland.com) will redirect to docs.hyland.com
- Older versions of documentation will remain accessible
In parallel, content that does not belong in product documentation will be reviewed and relocated where appropriate.
Open Source Documentation Remains Available
The GitHub repository Alfresco Documentation Repository will continue to exist.
What This Means for You
- Update bookmarks and references to docs.hyland.com (this is the final destination)
- Expect differences in navigation, search, and contribution workflows
- If you rely on GitHub-based documentation flows, plan for some adaptation
Final Thoughts
This is a business-driven consolidation, not a developer-led evolution of the documentation experience.
That does not automatically make it a bad decision, but it does mean expectations should be set correctly.
From a community perspective, the most important thing now is:
- ensuring content quality remains high
- keeping documentation accessible
- preserving as much openness as possible through GitHub
