Loading...
 
Skip to main content

Why WikiSuite Avoids Third-Party Plugins


Most web platforms grow through plugins: independently developed add-ons that bolt extra features onto a core system. It feels flexible at first. Over time, it becomes the platform's biggest liability.

Maison-croche

Where plugin architectures break down

Fragmentation


Every plugin author solves overlapping problems their own way, so a site ends up with five different plugins doing similar things, none of them aware of the others.

Independent release cycles


Core and plugins are maintained by different teams on different schedules. A core upgrade can silently break a plugin; a plugin upgrade can silently break the page it's used on.

Uneven security review


Core software from major open source projects gets sustained scrutiny. Individual plugins, especially free ones from small or single-maintainer teams, often don't, and a large share of real-world WordPress, Drupal, and Joomla security incidents trace back to plugins rather than core.

Abandonment risk


A plugin a site depends on can simply stop being maintained, leaving known vulnerabilities unpatched indefinitely.

The WikiSuite / Tiki approach

Tiki, the content-and-collaboration engine behind WikiSuite, takes the opposite approach: features like forums, file galleries, calendars, wiki pages, and structured data trackers are built into the core and maintained by the same team, under the same release and security process, rather than bolted on as separate plugins.

That means:

One upgrade path, not a dozen independently-versioned dependencies to track and test.

One security review process instead of trusting the weakest plugin on the site.

Features that are designed to work together from the start, not patched to tolerate each other.

The trade-off, honestly


This approach means fewer niche, single-purpose add-ons than a plugin marketplace offers. In exchange, what ships is tested against the same codebase it runs in, and upgrades don't come with the risk of an abandoned dependency quietly becoming a security hole.

Learn more


See Tiki for the full list of built-in features, or WikiSuite's component criteria for how release schedules are kept predictable.

You like the way we think?

Tell us about your project.