The WordPress framework does not support the structural hierarchies
needed in writing complex code - a shortcoming that results in numerous
problems for sites built using WordPress. Using a different base for more
complex projects offers greater flexibility, accuracy, and functionality.
Wordpress
Two WP syllables, which when uttered by most customers, are enough to
make our developers groan.
Not to say we don't approve of building websites with WordPress - far
from it - but because the reasons behind requests to use it can usually be
boiled down to: "Because that's what everyone else is using."
The popularity of WordPress has exploded in recent years, to the point
where what was originally a basic blog engine is now a CMS with a plugin
architecture, templates, and themes, loved by mainstream technology users
around the world.
As of January 2015, WordPress was used by over 23.3% of the top 10
million websites.
It gives the impression of being user-friendly and user-friendly, but
based on our experience with customers and their numerous WP support requests,
we would like to contradict this view.
Most of the WordPress developers we know manage to do the basics -
exactly what is already on the shelf -, but when it is necessary to create
something more specific within WordPress, they charge a very high price for not
implementing it or simply say that it is not possible to do it. In short, if
there isn't a free plugin on the internet to do the implementation, it usually
isn't done.
What bothers us about requests from clients to make it the basis of
their projects is that their next demand will usually be for a complex feature
beyond basic WordPress features.
Building something beyond the simple features possible with WordPress
is simply an exercise in masochism, and here's why.
Structural Limitations
The WordPress framework does not support the structural hierarchies
needed in writing complex code - a shortcoming that results in numerous
problems for sites built using WordPress.
Using a different base for more complex projects offers greater
flexibility, more accuracy, and improved functionality.
While it would be silly to try to reinvent the wheel every time you
need a CMS, using WordPress as a building block for something complicated like
an e-commerce website would be like trying to build a rocket ship off the same
wheel.
"If you try to use an incredibly useful tool for the wrong
function, you will quickly turn that valuable tool into worthless junk. Just
try brushing your teeth with a hammer or building a crate out of your
toothbrush," writes Hayden Wreyford in her TodayMade.com blog.
Technical Limitations
WordPress does not follow the MVC (Model, View, Controller) design
pattern by default or conforms to the Single Responsibility Principle and
subsequently encourages poor code standards.
Poor code organization and readability are often the results, which in
turn slows development time on a project - something clients need to be aware
of before pinning their flag too firmly to the WordPress flagpole.
Plugins provide greater technical flexibility for WordPress, but they also
have their downsides - stretching a site's resources, causing conflicts with
each other, and leaving messy footprints behind.
Another technical downside to WordPress is that any code written is
not easily or automatically testable, another factor that makes development
slower and more error-prone.
Security Limitations
Bad security can tarnish WordPress sites, yet another by-product of
the multiple plugins mentioned above. Attempts to hack WordPress are made quite
frequently, as we have seen in a wave of security breaches made over the last
few years.
According to Anthony Wing Kosner, WordPress' ease of use is what makes
it vulnerable to hacker attacks. "WordPress is easy. That's why people
like it. It's quick to set up a simple website.
It's easy to manage large amounts of content. It's easy to add
functionality without having to know how to code php because there's such a
huge developer community that makes tons of free plugins," he wrote in an
article on the subject for Forbes. "It's also very easy to hack.
When things are easy, we are less vigilant and do stupid things like
using obvious passwords. Less obvious is the use of the default
"admin" username and the failure to keep the site's software up to
date."
People are driven to choose WordPress for a variety of reasons, but
many of its perceived advantages are misunderstood.
From our own experience as a digital design and development agency,
we've put together our list of pros and cons of using this beloved but often
misunderstood CMS.
Pros
Open source structure - most code written by other developers can be
recycled in WordPress, saving time and money.
Plugin Availability - A wide range of plugins are available,
meaning that additional features and functionality can be added after a project
is underway, or even once a site is live, without compromising performance.
SEO - The code behind WordPress is clean and
simple while plugins can be used to achieve better SEO results. Simplicity -
WordPress has an intuitive interface and requires minimal formatting.
Quick Build - WordPress can be easily installed on the
host server and there is no need for HTML editing or FTP software as it is a
self-contained system. Ease of management - is browser-based, you can log in
and manage a website from anywhere on the planet. It's also quick and easy to
set up multiple users with different access levels and capabilities.
Customizable Design - WordPress can be completely customized and
integrated with your branding needs.
Price - WordPress' most significant advantage is its low cost, courtesy of some of the above reasons. Though WordPress.org is free of cost, minimal costs incur from the web hosting, themes, plugins etc. WordPress also has a paid version which you shall find on WordPress.com
No comments:
Post a Comment