About / Open Source
We build on open source. So we help build open source.
The platforms our clients trust are maintained by communities, and we are part of those communities. As a Gold Drupal Certified Partner, we maintain contributed modules, lead initiatives, mentor newcomers, and ship our own open source WebOps product. The improvements we make go back to the projects everyone depends on.
160+
30
9
Why we contribute
Open source is the ground our clients stand on.
Drupal, WordPress, and the tools around them are built and maintained by people, not by a vendor with a roadmap to protect. When you run your platform on open source, the health of the project is the health of your site. We contribute because it keeps the ecosystem strong, and because there is no better way to stay at the front edge of how these platforms actually work.
We use it, we improve it
The fixes we find get shared.
When we solve a problem on a client platform, the patch does not stay private. We push it upstream so the next team never has to solve it twice, and so the project our client depends on gets stronger.
Front-edge knowledge
We know the platform from the inside.
Maintaining modules and contributing to core means we understand these systems at the level of the code, well beyond how features get marketed. That depth is what makes a project that cannot fail safe with us.
A healthier ecosystem
We invest in the community.
Mentoring, speaking, sponsoring events, and leading initiatives all keep the community growing. A bigger, healthier community means better tools and more talent for every organization that builds on open source.
Our open source product
Polymer — the WebOps toolkit we run on, in the open.
Polymer is our open source WebOps product. It packages the deployment, automation, and platform-operations practices we have built across hundreds of client projects, and we maintain it in the open so any team can run their platform the way we run ours. The same tooling that keeps high-stakes sites stable is free to use, inspect, and extend.
Open by default
Released under an open source license, developed in public, and shaped by the teams who use it on real platforms.
Proven in production
Built from the WebOps practices we depend on for projects that cannot fail, not assembled as a side experiment.
Built for WebOps teams
Opinionated where it helps and flexible where it counts, so your team spends less time on plumbing and more on the work that matters.
# Polymer — open source WebOps toolkit
name: polymer
maintainer: Digital Polygon
license: open-source
handles:
- deployments
- automation
- platform-operations
runs_on:
- drupal
- wordpress
- headless
status: productionHow we give back
We maintain, contribute, and support the open source we build on.
Our involvement runs deeper than using the software. We own and maintain projects on Drupal.org, push the fixes we make back upstream, and invest our time and our people in keeping the community healthy.
Maintain
We own projects on Drupal.org.
We maintain a portfolio of contributed Drupal modules, owning their issue queues, releases, and compatibility as Drupal moves forward. When your platform depends on one of them, a named team stands behind it.
9
Contribute
We push our fixes upstream.
The improvements we make on client platforms go back to the projects they came from. Our engineers are credited across Drupal core, contrib, and the developer tooling that WebOps teams rely on every day.
160+
Support
We invest in the community.
We mentor newcomers, speak at DrupalCamps, sponsor events, and hold leadership roles in initiatives like Drupal4Gov and Starshot. A healthy community is the ground every client platform stands on.
30
Beyond the code
Leadership in the communities we depend on.
Contribution is more than commits. Our team sits on boards, shapes initiatives, mentors new contributors, and shows up at the events that hold these communities together.
Board-level leadership in Drupal4Gov
We help steer the community that supports Drupal for government, shaping open source strategy for platforms used by public sector and civic teams.
The Starshot Initiative
We contribute to the initiative behind the next generation of Drupal CMS, helping make the platform easier to adopt for the teams who come after us.
Mentors, speakers, and ambassadors
Our contributors hold roles across the project as mentors, DrupalCamp speakers, content moderators, and ambassadors who bring new people into open source.
Drupal AI initiative
Through Markdownify Content, AI LLM Optimized Content, and /llms.txt, our team helps build the open source AI capabilities modern Drupal platforms run on.
Drupal GovCon 2026
EvolveDigital Montreal 2026
DrupalCon Chicago 2026
Drupal GovCon 2025
Florida DrupalCamp
DrupalCamp NJ 2026
EvolveDigital NYC 2025
DC-MD Area Drupal Meetup
For projects that cannot fail
Build with a team that builds the platform too.
When your platform runs on open source, it helps to work with the people maintaining it. Tell us what you are building, and let’s talk.
Frequently asked questions.
Open source at Digital Polygon, answered.
Is Digital Polygon a certified Drupal partner?
Yes. Digital Polygon is a Gold Drupal Certified Partner with thirty contributors active on Drupal.org. You can review our contribution record, supported projects, and team on our Drupal.org organization profile.
What open source projects does Digital Polygon maintain?
Our team maintains nine contributed Drupal modules, including Markdownify Content, AI LLM Optimized Content, CKEditor 5 Inline Styles, Editor Image Styles, Twig WebP, Magic Authentication, Entity Limit, Front Page Per Language, and WireWheel Connector. We also build Polymer, our open source WebOps product.
What is Polymer?
Polymer is our open source WebOps product. It packages the deployment, automation, and platform-operations practices we use across client projects, maintained in the open so any team can run their platform the way we run ours.
Which platforms and tools do you contribute to?
We contribute to Drupal and WordPress at the CMS level, and to Docksal and DDEV at the developer-tooling level. Our work spans the full stack that modern WebOps teams rely on, from the content platform to the local development environment.
How does open source contribution benefit your clients?
Maintaining modules and contributing to core gives our team a depth of platform knowledge that goes well beyond using the software. Fixes we make get shared upstream, the projects our clients depend on stay healthy, and the work is grounded in how these systems actually behave in production.