Some of the best parts of Strapi were not built by Strapi. You built them: the plugins, the providers, the starters, and the agencies that ship projects on it every week.
But that work is hard to find. It lives on npm, on GitHub, in a forum thread, in someone's memory. So you open five tabs, compare stars, and guess which package is still maintained.
The Strapi Community Hub ends the guessing. Packages, templates, the partners who build them and the people behind them are in one place, and each page leads you to the next. The videos in this tour follow one real example: the TipTap Editor Plugin by Notum.
Start with a search
Say your project needs a better rich text editor. The home page of the Hub has one search field, and it covers everything the community has published. Search for what you need and the marketplace opens with the results already filtered. There is no detour through npm and no second tab.
If you would rather browse, the marketplace narrows down as you go. Filter by type when you need a provider and not a plugin. Add a category or an integration. Then sort by popularity, GitHub stars or newest, and a long list becomes a short one.
Decide before you install
Finding a package is the easy part. The harder question is whether you can depend on it.
Open any package page and the answer is in front of you. The publisher is named at the top. The latest version and its release date sit just above the install command, which you copy with one click. Next to them, the page shows GitHub stars, monthly npm downloads and the maintainers, with links to npm and GitHub if you want to dig deeper. The full README follows.
Everything you used to collect from five tabs is now on one page.
See it at work
A README shows how a package behaves alone. What you really want to know is how it behaves inside a project.
Scroll to the end of a package page and you find "Templates using this package". Open one of those templates and you get a preview, a link to the live demo, and the list of every package it includes. In our example, the TipTap Editor Plugin leads to the Strapi v5 & Next.js v16 Monorepo Starter.
The package you came from is in that list, and one click brings you back to where you started. That loop is the idea behind the Hub. A plugin points to the projects that use it, and a project points to the plugins inside it.
Meet the people behind it
Every package and template carries the name of its author. Click it and the Hub introduces them: who they are, where they are based, and when they joined. For a Strapi partner, a badge shows the partner level. Notum, the author in our example, is an Enterprise Partner.
The page goes further than a logo. "Published Content" gathers everything the organization has shared on the Hub, and "People" shows the members of the team. If you are looking for an agency for your next project, this is their Strapi track record, in public.
Add your own
Everything in this tour exists because someone decided to share it. Doing the same takes one form.
Click Submit and choose a package or a template. For a package, you pick the type (plugin, provider, SDK or tool), then add a name, a short description, the registry URL and the repository URL. You can publish under your own name or under an organization you manage.
The form also tells you what happens next. A business review confirms that the repository is public, MIT-licensed, has a README, and lists Strapi as a peer dependency. A security review scans the dependencies for known vulnerabilities.
It stays yours to run
Publishing on the Hub is not a handover. Every contributor gets a public profile, and everything on it stays in your hands.
The profile is your page in the community: a tagline, a bio, your links, your location, and a README where you can say more. Next to it, "Published Content" shows every package and template you have shared. You edit all of it yourself, from your account.
The same is true for your packages. Open Submissions, click Edit, and you can change the name, the description, the logo and the categories. The README can stay in sync with the package registry, or you can write it yourself. When a package reaches the end of its life, you can remove it too.
Teams and partners work the same way
An agency or a product team publishes as an organization, and an organization runs itself too. It has its own public page, its own profile, its members, and its own list of packages and templates. In the settings, you choose the logo, the name and the URL. You also decide who can submit on behalf of the organization: only owners and admins, or every member.
The Partner Portal
For Strapi partners, the organization has one more layer. The Partner Portal opens from the organization settings.
It starts with where you stand: your level among the four in the program (Registered, Community, Business and Enterprise) and the benefits that come with it. From there, the material your team needs is one click away. Sales enablement covers how the program works, pricing and positioning. Tech enablement holds learning paths, architecture guides and demo licenses. Reusable content keeps the Strapi logo pack and the co-marketing program. Two more sections, Submissions and ARR tracker, are marked "Later".
The Partner Portal is open to the owners and admins of a partner organization.
Your turn
The Hub is only as good as what the community puts in it. Thank you to everyone who already publishes there.
Now browse the marketplace and find one package that removes work from your current project. Then submit the plugin, provider or template that you already built. Other teams have the problem that you solved.
