payload-plugins
A monorepo of open-source Payload CMS plugins, each published independently to npm.
A monorepo of open-source Payload CMS plugins, each published independently to npm.
payload-plugins is a collection of focused Payload CMS extensions I extracted from production work. Each one began as a recurring need—importing HubSpot forms, choosing icons in the admin, or translating localized content—and became a reusable package instead of another project-specific implementation.
The plugins share one repository and development environment, but each remains independently versioned and published. This keeps the contributor workflow consistent without forcing users to install more than they need.
Plugins
payload-hubspot
Imports HubSpot forms into Payload’s Form Builder collection. Editors can fetch forms from a connected HubSpot account, choose one, and turn its fields into a native Payload document from the admin.
The imported document retains its HubSpot portalId and formId, preserving the relationship to the source while allowing the form to be rendered through the site’s own components and design system rather than a generic embed.
payload-iconify
Adds a searchable Iconify picker to the Payload admin. Editors can browse and select icons for navigation items, feature cards, callouts, and other structured fields without hardcoding SVG markup or asking a developer to add every asset.
payload-translator
Drafts translations for localized documents and globals through pluggable resolvers. Adapters for copy, Google, OpenAI, LibreTranslate, and the Vercel AI SDK let teams choose the translation workflow that fits their stack.
The plugin treats machine output as a draft: editors can translate the active document into another locale, review the result, and refine it before publishing. That reduces repetitive entry while keeping editorial control inside Payload.
The monorepo
- pnpm workspaces keep every plugin in its own package while a shared Payload app loads source changes directly during development.
- Changesets handles independent versions, changelogs, and releases for each package.
- SWC and a shared TypeScript configuration provide one consistent build pipeline across the repository.
- Vitest and Playwright cover integration and end-to-end behaviour against the shared development app.