Typically called a CMS platform, the website’s backend is the frame that supports the functionality, content creation and file library.
In redeveloping or upgrading this, you should take this time to implement new functionality into its system. Things like a Geo-redirect, Open Graph and Yahoo – supported widgets can all bring sophistication to the website, and the user’s journey.
Sometimes platforms need to be upgraded, they can no longer support the level of flexibility required by adding new content and features.
Optimising the website’s backend doesn’t necessarily mean changing the vendor, it could mean upgrading the current vendors existing product.
It’s also a good time to put in staging, development and production environments so that you can always have a testing environment.
It’s also a good time to look at the API’s connected with other systems like Salesforce Engage, Google and more.
- Adding new API support for other tools
- Creating new possibilities for future content
- A better ranking with search engines
- Less security vulnerabilities.
- Current server architecture
- Current vendors product
- API support with other Alcentra tools
- Testing environments
- IT security requirements
The updated backend will provide options for adding search engine optimisation enhancements like meta tagging, better script management and an intuitive content creator.
It should be fast, easy to use and flexible enough to customise.
Better script management
This effects everything from page loading times to search engine ranking. A modern solution will be able to put most of the “heavy” scripts at the bottom of the page.
It will also allow easy access to for custom CSS and JQuery options for future front end developers to add new plugins and layout tweaks.
An easy to use CMS
It shouldn’t take staff long to be trained, and use the CMS’ creation tools to update and content.
Most modern solutions utilise drag-and-drop mechanics to add various page parts, images and documents.
Better search engine optimisation
An updated backend end should provide native support for the Google suite of products, including the Universal Tracking code, Tag Manager and more. It should also have the option of adding tools for properly labelling documents and files – which can create a better ranking.
Scope and vendor assessment
In the first month I will look to examine the current infrastructure, plan and look at what the vendor has to offer.
We may need to go out to tender, or see if another exisiting vendor can deliver a better solution.
At the same time, we will need to be clear about how “open” or customisable we want the solution to be. Without the proper resourcing, maintaining the CMS will become a burden for the business.
- Vendor assessment
- Level of customisation in the product
- Level of support offered by vendor
- The architecture of the system and its code
Install on development servers
Once a vendor has been chosen, work can start planning the build and integration of the new CMS into the technology ecosystem.
The new CMS should be installed in a development environment and work to move existing content over can begin.
At this stage you may want to decide to run the frontend redesign work in tandem.
- Take this time to add frontend redesign?
- Development environment built
Move into production environment
With testing complete we should look to integrate some of the APIs from the data centralisation and stoneshot.
Now that the CMS has been fully upgraded we can start work to redesign the front end.
- Start work on frontend
- integrate critical APIs with Salesforce