When time and money is spent supporting your corporate website, a proficient process should be put into place. A set process mitigates risk and ensures that all aspects of the website comply with each other. Consistency is also something to strive for when working on multiple support tasks that impact different sections of the website. Simply following a set of golden rules, while performing website maintenance, can keep your efforts process-oriented and consistent while maintaining a high level of quality.

There are six golden rules of supporting a website that can set the foundation of a methodical procedure. They are listed below:

Properly Define Requested Changes. Updates that are requested should be accurately defined and thoroughly documented. There should be no opportunity for miscommunication.

Identify Regression Issues Related to Changes Prior to Starting the Work. All requested updates should be reviewed to ensure that implementation will not affect other aspects of the site.  Understanding the impact changes will have on other areas of a website or other web assets that rely on certain functionality from the supported website is critical.

Ensure Compliance with Technical and Creative Design Standards. Changes that are implemented should comply with the design and technical aspects of the site.  Having a defined style guide and technical architecture greatly improves the consistency of website changes over time.  As time goes by, the risk of inconsistencies greatly increases.  By having formal documents in place that support teams can lean on is extremely beneficial.   

Document Change. Ensure that all updates are documented where appropriate.  Unless your website will always be maintained by the same development company or support staff, keeping up with documentation is critical.  Updating information architecture diagrams, style guides, hosting requirements and technical architecture documents is highly recommended.    

Track Code Updates. Utilize software, such as Subversion Source Control or Microsoft’s Visual Source Safe, which documents and saves the full history of code changes.  Having a safety net to roll back changes and understand what changes took place to particular files is a must.   

Change Log.  All parties involved in the changes should be logging notes related to the update in a central repository.  Anything related to the requested changes including: impact analysis, time requirements, developers involved in the change, deviations from standards and general communications associated with the change should be noted.

Website Support Best Practices

By following these best practices you are sure to execute high-quality website support and maintenance.  A well-defined and executed support and maintenance program can extend the life of your website, greatly reduce cost and accurately represent your organization to the visiting audience.