Should You Invest in a Custom-Coded Website? Weighing the Pros and Cons.
While a custom-coded website seems like the ultimate solution, it’s not necessarily the right solution for every business or organization. Understanding what “custom code” really means will reduce unpleasant surprises so you can make the right decision.
A custom-coded website is like owning a two-million-dollar house – they’re both very nice, but neither is cheap nor easy to maintain. Before investing in your new website, weigh the pros and cons.
A custom-coded website will give you the exact look and functionality you want, but some website template tools might mean settling for something less-than-perfect. Businesses that want that custom experience expect to pay more and they plan ahead for the specialized maintenance required.
You’d be surprised, however, to know how many folks in the moderately-priced website range have sites with custom code and don’t even realize it. Until there’s a problem.
In the earliest days of the internet, all websites were custom-coded. If you were around then, you might remember how it was a big deal to get your webmaster to change a typo for you. Then, Content Management Systems (CMS) were introduced, and everybody in the organization could post and update their own content.
Sprocket Websites has worked with many CMS platforms through the years, with a specific focus on two: DNN and WordPress. Because WordPress is Linux-based and DNN is Windows-based, we can help a wide range of clients. Each has advantages and disadvantages, and both can fall prey to the “secret” custom code problem.
CMS platforms let your developer build a website out of pre-coded modules or plug-ins. Think of it as building with Lego bricks. You have a choice of styles, sizes, and colors and they all fit together nicely. Let’s say, however, the client wants a “brick” that doesn’t exist. Some developers will secretly write custom code to create that specific “brick” before fitting it in with the rest of the “bricks” and handing the whole thing over to the client. As long as the client is happy, where’s the harm?
Here’s where: Software updates happen regularly and one day, some part of the website stops working and the client has no idea why. If it’s not a browser update, it could be an Operating System (OS) update on a server or a version update of the CMS platform.
If you still have a relationship with your developer, they can fix that custom “brick” so it will fit again. If you don’t, it becomes very expensive to reverse-engineer what’s happened. “Brick” developers for the most commonly used CMS will prepare for OS and platform updates. Plus, there is a community of folks to help who know those “bricks” inside and out. Sprocket Websites is active in both the WordPress and DNN community.
Building a custom-coded website could be the perfect choice for your project. Or you may need a custom module or plug-in. Just be sure the customization is your choice and not a “secret brick” you didn’t even know you had. If your current WordPress or DNN site isn’t working the way it used to, give us a call. We’d be happy to help you fix it.
Photo by Kevin Bidwell
This article is an update to “Is a Custom Coded Website Wrong for You” dated 5/23/2016.
Kate Gingold
I have been writing a blog with web marketing tips and techniques every other week since 2003. In addition to blogging and client content writing, I write books and a blog on local history.
Other posts by Kate Gingold
Contact author
Full biography
Full biography
I have been writing a blog with web marketing tips and techniques every other week since 2003. In addition to blogging and client content writing, I write books and a blog on local history.
x
Linked In
Google Plus