When a website requires a feature that isn’t already available, both WordPress and SiteAdmin offer the option to develop it yourself.
While the differences between the platforms are actually quite minimal in this area, both can be extended with custom code, functions, and integrations.
WordPress – Custom Plugins Offer Maximum Flexibility
In WordPress, plugins are the natural way to extend the platform. A custom plugin can include everything from a simple specialized feature to a comprehensive system with its own settings, databases, and integrations.
For example, a custom plugin can:
- Add custom functions to the WordPress admin panel
- Create custom settings pages
- Manage custom data
- Include shortcodes and frontend features
- Create custom API endpoints
- Integrate external services and APIs
- Modify or extend existing WordPress functionality
This is one of WordPress’s major strengths. The platform is highly favored among developers, offering extensive freedom to build exactly the feature needed.
SiteAdmin – Custom Modules
SiteAdmin provides similar capabilities through custom modules.
A custom SiteAdmin module can have its own settings pages, data, and databases. It can also create frontend components, use SiteAdmin’s existing functions and APIs, and communicate with external services.
SiteAdmin also already supports shortcodes, making it possible to build custom features that can then be placed on the website just like other SiteAdmin components.
Technically, the possibilities are quite similar. Advanced custom features can be built in both platforms.
The Difference Lies in Organization
In WordPress, a large number of plugins can quickly make the administration overwhelming. Plugins can add their own menus, settings, and features across different parts of the admin interface.
This is part of WordPress’s flexibility, but when many add-ons are used, the administration can also become more complex.
SiteAdmin has chosen a more cohesive structure. Custom modules are placed under My Modules and can have their own settings there.
The goal is for features to be easily accessible within SiteAdmin without cluttering the admin interface with separate menus and buttons from each individual feature.
This isn’t a technical limitation. Custom menus and features can be built, but SiteAdmin aims to keep the administration more unified.
Custom Databases and Functions
A custom solution may require more than just simple settings.
Both WordPress plugins and SiteAdmin modules can handle custom data and databases when needed, enabling the creation of significantly larger features than standard content blocks or forms.
This could involve an internal system, a customer portal, a catalog, an integration, or any function requiring custom logic and data storage.
A SiteAdmin module can also use existing SiteAdmin functions instead of building from scratch.
Integrations with External Services
Custom plugins and modules can also communicate with external APIs.
SiteAdmin focuses on how external data is retrieved. When an integration, for example, fetches information from an external service, SiteAdmin first tries to make the request from the server, cache the result locally, and then display the information from the website.
This reduces the need for each visitor’s browser to make direct external calls.
This is especially important when external services are used across multiple websites and you want to control how data flows.
Who Develops the Custom Function?
This is where SiteAdmin differs from WordPress today.
In WordPress, the customer can hire any developer or agency to build a custom plugin. This offers great freedom and allows choosing among many different developers.
Currently, custom SiteAdmin modules are developed by SiteAdmin and are offered as specialized development on a quote basis.
This means the developer also understands the platform’s structure and existing functions.
Maintenance of Custom Code
Custom-developed code needs maintenance regardless of the platform used.
A custom WordPress plugin must continue to function when WordPress, the theme, or other plugins are updated. The person responsible for the plugin must also take responsibility for future compatibility and security updates.
Similarly, a custom SiteAdmin module must be maintained when it becomes more extensive or uses functions that change.
The difference is that SiteAdmin can handle updates as part of the same platform. A custom module can therefore be updated alongside SiteAdmin, and maintenance can be offered as part of the development solution.
For smaller, specialized features that can be reused for multiple customers, the model can be different. If a module can be generalized and offered to more customers, the customer typically does not need to bear an ongoing maintenance cost in the same way. Larger, customer-specific solutions, such as an extensive e-commerce system, may, however, require ongoing maintenance.
From Customer-Specific Development to Reusable Module
A promising possibility with SiteAdmin is that a feature initially developed for a customer can later become more general.
A custom module can transition from being a completely customer-specific solution to a reusable part of the platform.
SiteAdmin is also looking into the possibility of letting partners develop their own modules via API. After review and approval by SiteAdmin, such modules could become available through the module marketplace.
This is not yet an open developer platform, but the possibility exists and SiteAdmin is exploring it if there is interest from partners.
WordPress or SiteAdmin?
If we only look at the possibility of developing custom functionality, the difference is actually quite small.
WordPress gives you the freedom to develop custom plugins. There is a vast ecosystem of developers, and you can choose who builds and maintains the solution yourself.
SiteAdmin also offers the possibility to build advanced specialized features, but development occurs within SiteAdmin’s platform and is currently handled by SiteAdmin.
| WordPress | SiteAdmin | |
|---|---|---|
| Custom Code | Custom plugins | Custom modules |
| Custom Settings Pages | Yes | Yes |
| Custom Databases | Yes | Yes |
| Frontend Features | Yes | Yes |
| Shortcodes | Yes | Yes |
| External APIs | Yes | Yes |
| Use Platform Functions | Yes | Yes |
| Who Develops Today? | Any developer/agency | SiteAdmin |
| Maintenance | Customer/agency or plugin developer | Can be handled by SiteAdmin |
| Partner Development | Open ecosystem | Planned via API and review |
It’s Not About What Can Be Built
The idea that WordPress automatically offers more flexibility because there are thousands of plugins is misleading. When we talk about pure development, the picture is more nuanced.
Both WordPress and SiteAdmin can be extended with advanced custom code. The difference lies primarily in how the surrounding ecosystem for the custom code functions.
WordPress gives you an open and vast developer ecosystem where you can choose who builds and maintains your plugin.
SiteAdmin has a more controlled model where custom development is currently done within the platform. This offers less freedom to choose developers but ensures that the custom function can be developed with direct access to SiteAdmin’s structure and existing functions.
No, SiteAdmin does not aim to prove that custom development is something WordPress cannot handle. Instead, WordPress is very powerful when it comes to custom development.
SiteAdmin chooses a different path: open enough to build what is needed, but controlled enough for the platform to develop as a whole.