Blue Core CMS(TM) vs. WordPress Illustration

Blue Core CMS™ vs. WordPress

The table below presents important features that differentiate Blue Core CMS™ websites from websites built on WordPress. The differences and limitations described for WordPress are also true for the other free open-source content management systems (such as Joomla, Drupal, etc.).

Feature

Description

Blue Core CMS™

WordPress

Two complete and independent copies of the website

Blue Core CMS™ delivers two complete and independent copies of every website it hosts. These are referred to as the “preview site” and the “live site.”

Having two copies of your website enables a large number of important features and safety nets simply not possible with WordPress or any other system that delivers only one copy of your website (the live site).

For example, when you update your Blue Core CMS™ website, only the preview site is modified. The live site remains unmodified until you publish the updates. This means you can take your time making updates (hours, days or weeks . . . it doesn’t matter) because nobody will see the work in progress.

*With WordPress, content updates to pages and posts can be previewed before they are published, however, layout and theme updates must be made to the live website in real time. This means people visiting your website while updates are in progress will see modifications in progress. If a page is somehow broken, your site visitors will see the problem in real time; and they will see the problem until it is fixed.

There are many other advantages that come with having two copies of your website online at the same time; more than we will list here.

*

Revert to any previously saved version of page or site component content with just a few mouse clicks

Blue Core CMS™ provides a number of safety nets that enable non-technical users to update their website with confidence, knowing that if something goes wrong, they can quickly and easily restore any previously saved version of a page or website component – usually with two or three mouse clicks.

*WordPress provides safety nets for previously saved versions of pages and post, but does not provide any uniform mechanism for reverting to a previously saved version of a website component or plugin. The ease with which reverting is enabled depends largely on the relevant WordPress plugin and the extent to which it supports versioning. Most plugins support no versioning at all. So, to get back to a previous copy, a technical support request must be made to restore an old version of the website’s database.

*

Root-relative paths

Blue Core CMS™ encourages, but does not require, root-relative paths to all local website resources (URLs to pages, images, documents, etc.). Root-relative paths enable any website to be accessed via any domain name.

WordPress, on the other hand, encourages and, in many places, requires/creates fully-qualified paths that include the website’s domain name. Consequently, it is very time-consuming and tedious to move a WordPress website to another domain (or enable access via another domain).

This issue is most problematic for WordPress websites that are being moved to another hosting provider, or are being significantly redesigned. In these cases, the website will need to be made available at some temporary URL (typically a subdomain of the primary domain). In these scenarios, the temporary URL gets scattered throughout the WordPress database and templates during construction. Then, when it’s time to go live at the correct live URL, all the paths in the database, templates and page content will need to be updated, which will be a time-consuming and error-prone process.

Automatic updating of Site Map

SiteMap.xml is an important component of any website. This optional file is used by Google and other search engines to learn about all the pages in your website and in general how your website hangs together.

Blue Core CMS™ automatically creates and manages SiteMap.xml so no manual intervention is required. But if manual changes are needed, Blue Core CMS™ makes it easy for non-technical admin users to point-n-click to update SiteMap.xml.

*WordPress offers support for automatic and easy management of SiteMap.xml, but unfortunately it requires a plugin (and WordPress plugins have a number of significant issues).

*

Automatic setup of HTTP 301 redirect to new page name when a page name (URL) is changed

Whenever a page name changes or you change a menu containing links to pages in your website, Google will by default not know how to find the updated page name and will instead request the page by its original name. The way to inform Google of the new page name is to set up something called a “301 Redirect.” In a nut shell, this a mechanism your website uses to inform Google and other search engines on what is the new name when the search engine requests the old page name.

Blue Core CMS™ automatically creates a 301 Redirect whenever a page name is changed, or whenever your site’s menus are modified.

*WordPress offers support for 301 redirects, but via plugins.

*

Administrative tools designed specifically for “non-technical” small business owners

Blue Core CMS™’s extensive suite of administrative tools was designed specifically for small business owners who have no knowledge of web technology (JavaScript, CSS, HTML, etc.).

WordPress, on the other hand, was originally designed for website developers who have at least some expertise with web technology. So, the administrative interface is less intuitive and less usable by non-technical admin users than is the Blue Core CMS™ administrative interface.

Moreover, WordPress is built on a plugin architecture whereby most customized WordPress websites include several plugins. The extent to which the admin interface of each plugin is user-friendly for a non-technical audience is inconsistent. Some are really easy to use, while others aren’t easy to use.

Limited and Inconsistent Support

Foundation architecture inherently impervious to many common website attack types

The foundational architecture of Blue Core CMS™ automatically eliminates many of the most common website hacks that to which WordPress is inherently vulnerable.

Form implementation impervious to all types of automated attacks

The data entry form implementation of Blue Core CMS™ is impervious to practically all types of automated attacks.

There are no WordPress form plugins that provide the equivalent level or type of protection against automated attacks.

Form implementation automatically preserves all posts in database; with admin UI for easy viewing and forwarding

All form posts to Blue Core CMS™ websites are automatically saved to a database, complete with post metadata (e.g., sender’s IP address, browser info, etc.)

*WordPress relies on an external plugin for equivalent functionality.

*

Simple yet powerful template management system, with built-in version control history

Blue Core CMS™’s templating system automatically preserves historical copies of each layout template. With just a few mouse clicks, any previously saved version of any layout template can be retrieved.

WordPress, on the other hand, ships with an enormous collection of templates, the vast majority of which are not used by any given website. And there is no version history saved automatically when template changes are saved. Consequently, backup versions of templates must be manually saved and organized, or a backup copy of the website and its database(s) must be restored in order to access earlier versions.

PayPal instant payment notification support

Blue Core CMS™ is automatically integrated with PayPal’s Instant Payment Notification service. And for any given website, integration with PayPal is as easy as point-n-clicking and entering a few pieces of information (your PayPal account ID, for example).

*WordPress offers PayPal integration, but via plugin.

*

Simple yet powerful third-party client library management

Blue Core CMS™ was developed with the recognition that web client libraries are evolving at a rapid pace, and any given website may need different or newer libraries than other Blue Core CMS™ websites. So, Blue Core CMS™ facilitates the quick-and-easy linking of Blue Core CMS™ websites to any arbitrary third-party library, like jQuery, Bootstrap, etc.

WordPress does not support the quick-n-easy comprehensive linking to third-party libraries. To change libraries in a WordPress site requires the modification of layout templates (likely many such templates), and/or updating the WordPress theme used by the website.

Built-in ability to reject requests by IP Address Block (e.g., deny requests from countries or regions)

Through a simple property page, the administrator of a Blue Core CMS™ website can block page requests originating from arbitrary IP address blocks. For example, most of our customers are based in the USA. Yet most attacks originate from eastern European countries. So, Blue Core CMS™ automatically blocks web request from those countries. These blocks can be easily removed; or changed.

*WordPress offers no such support natively, and only via plugin.

*

Admin UI includes MRU (most recently updated) list of pages and site components

The administrative interface of Blue Core CMS™ includes a “most recently used” (MRU) list showing the most recently modified pages and website components. This is a significant convenience, particularly for non-technical business owners.

WordPress offers no such feature. While WordPress does offer the ability to see which pages and posts were most recently modified, WordPress does not have the ability to “know” which plugins were modified. So, no equivalent feature is available for WordPress users.

Site components exposed as web services to facilitate integration with external applications and websites

Most website components that comprise Blue Core CMS™ websites are implemented as web services (not as plugins). This means the website components can easily integrate with external websites built using completely different technology. This component architecture enables powerful unique website solutions simply not possible with any other system, including WordPress, that does not implement website UI components as web services.