Native Modules vs. Plugins: What We’re Building at SGEN

Clark Pesa — Tue, 25 Aug 2026 05:42:49 +0000

Why SGEN Is Taking a Native-Modules Approach to CMS

Hi DEV Community!

I’m Clark, a Growth Marketer at SGEN, and I wanted to share something I’ve been learning while working with the platform: why SGEN is built around native functionality instead of relying heavily on plugins.

What is SGEN?

SGEN is a modern CMS and website builder designed to bring the tools needed to build, manage, host, and grow websites into one platform.

Instead of starting with a core CMS and adding multiple third-party plugins for common website functionality, SGEN includes 23 native modules across 7 categories.

That means features are designed as part of the platform rather than being added later through a collection of separate plugins.

Why take this approach?

One thing I've noticed while learning more about CMS platforms is how quickly a plugin stack can grow.

You might need separate solutions for SEO, forms, analytics, redirects, security, performance, and other functionality.

That flexibility can be useful, especially when a website has very specific requirements.

But it can also mean more dependencies to manage.

SGEN takes a different approach: build commonly needed functionality directly into the CMS.

The idea is to create a more unified environment where the individual pieces are designed to work together.

It's more than just the modules

Another thing that makes SGEN interesting to me is that the CMS isn't treated as the only part of the website stack.

Hosting, security, SEO capabilities, and server-side rendering are part of the platform as well.

From my perspective on the growth side, that matters.

SEO and discoverability aren't only about keywords and content. How a website is built, rendered, structured, and maintained can influence what marketers are able to do after launch.

Working at SGEN has made me pay much more attention to that relationship between development and growth.

Native functionality vs. flexibility

Of course, there is a trade-off.

A large plugin ecosystem gives developers enormous flexibility.

A native-module approach gives up some of that open-ended choice in exchange for a more controlled and integrated environment.

SGEN is betting that for many websites and agencies, reducing the number of separate tools that need to be installed, maintained, and paid for can make website management simpler.

Whether that approach makes sense depends on the project.

And that's actually what I'd like to learn more about from developers here.

When choosing a CMS, do you prefer having more functionality built into the platform, or having a lightweight core and choosing your own plugins?

I'd love to hear how you evaluate that trade-off.

Hi DEV Community! I’m Clark 👋

Clark Pesa — Tue, 25 Aug 2026 05:10:19 +0000

Hi everyone!

I’m Clark, a Growth Marketer at SGEN, and this is my first post here on DEV Community.

My background is more on the marketing and growth side, but my current work has brought me much closer to the technical side of the web — SEO, CMS platforms, website performance, search visibility, structured data, and how developers build websites that are actually discoverable.

One thing I’ve been learning is that growth and development are much more connected than they sometimes seem.

A technically great website still needs to be discovered. At the same time, good marketing can only go so far if the technical foundation of a website creates problems for performance, SEO, or user experience.

That intersection is what I’m hoping to explore here.

I plan to share things I learn from working on SEO and growth for a CMS platform, experiments that work (and sometimes don’t), and observations about how technical decisions affect discoverability.

I’m also here to learn from developers who understand this side of the web much better than I do.

If you work in web development, SEO, CMS, or growth, I’d love to connect.

Looking forward to being part of the DEV Community!