Alfresco Addons Catalog

The community-driven directory of add-ons, extensions, and plugins for Alfresco Content Services

Live Site: alfrescolabs.github.io/alfresco-addons-catalog

Browse 70+ Alfresco add-ons including:

• Repository extensions and modules
• Third-party integrations (Office, OnlyOffice, DocuSign, etc.)
• Developer tools and utilities
• Workflow and business process solutions

Compatible with: ACS 5.x, 6.x, 7.x, 23.x, and 25.x (Community & Enterprise)

Why Use This Catalog?

Since the original addons.alfresco.com was discontinued, this catalog serves as the official community-maintained directory for discovering Alfresco extensions. All submissions are reviewed by the Hyland team before publication.

Browse the Catalog →

Project in Beta — Now in AlfrescoLabs The Alfresco Add-ons Catalog is now available in the AlfrescoLabs organization. The project is currently in Beta status and open to community contributions. We welcome feedback, ideas, and pull requests as we continue shaping the catalog together.

Overview

The Alfresco Addons Catalog is a community-driven showcase of add-ons, integrations, and tools built for the Alfresco ecosystem. It’s entirely static, runs on Hugo + GitHub Pages, and enables zero-infrastructure publishing of third-party solutions.

Live site (development): https://alfrescolabs.github.io/alfresco-addons-catalog/

Key features:

• Community-contributed extensions and solutions
• Instant client-side search (Fuse.js)
• Automated validation through JSON Schema (AJV)
• Zero server infrastructure — built and deployed from GitHub Actions
• Optional analytics and weekly traffic reports

Project Structure

.
├─ .github/
│  ├─ ISSUE_TEMPLATE/            # Catalog submission form
│  ├─ workflows/                 # CI/CD workflows
│  │  ├─ validate-and-build.yml  # Validate entries + build Hugo site
│  │  ├─ pr-from-issue.yml       # Convert issues into PRs automatically
│  │  └─ collect-stats.yml       # Collect weekly traffic analytics
│  └─ CODEOWNERS
├─ archetypes/entry.md           # Template for new catalog entries
├─ content/entries/              # Markdown entries for each add-on
├─ data/licenses.yaml            # Reference list of accepted licenses
├─ layouts/partials/             # Hugo partials (cards, search, facets)
├─ schema/entry.schema.json      # JSON Schema used for validation
├─ scripts/                      # Node.js utilities for CI validation
│  ├─ validate-frontmatter.mjs
│  └─ make-entry-from-issue.mjs
├─ reports/                      # Generated weekly traffic stats
├─ static/uploads/               # Logos and screenshots
├─ hugo.toml                     # Hugo site configuration
├─ run.sh                        # Docker helper for local builds
└─ LICENSE                       # Apache 2.0 License

Local Development

You can preview and test the catalog locally using Hugo.

Option 1: Native Hugo

# Install Hugo (extended version)
hugo server -D

Then open http://localhost:1313.

Option 2: Docker (Recommended)

./run.sh

This uses the official klakegg/hugo:ext container to run a consistent environment.

Adding New Entries

The catalog is now hosted in AlfrescoLabs and is in Beta status. You can submit new entries and propose improvements through Issues and Pull Requests. Community contributions are encouraged as we refine and expand the Alfresco Add-ons Catalog.

For reference, the normal submission flow is:

1. Submit an Issue using the “Submit a catalog entry” template
2. A GitHub Action automatically generates a Pull Request
3. Schema validation ensures metadata compliance
4. Approved entries are automatically published

Validation Rules

All entries are validated against schema/entry.schema.json using AJV. You can test locally (optional):

npm install
node scripts/validate-frontmatter.mjs

Traffic & Analytics

The repository includes a GitHub Action that collects traffic data via the GitHub REST API:

• Runs every Sunday at midnight (UTC)
• Stores data as JSON and CSV in /reports/
• Requires a fine-grained PAT with traffic:read permission
• Token name: TRAFFIC_STATS_TOKEN

To set it up:

Settings → Secrets → Actions → New repository secret
Name: TRAFFIC_STATS_TOKEN
Value: <your fine-grained token>

License

Licensed under the Apache License 2.0. See the LICENSE file for details.

Contributing

• Follow CONTENT_POLICY.md and TAKEDOWN.md
• Each PR undergoes automatic schema validation and manual review
• Accepted submissions appear in the public catalog automatically