Which CMS?

SFSW recommends three:

1) WordPress

Best for simplicity for running the website, to get content refreshed takes a few clicks including sophisticated tagging, comments and best of all – plugins to do all sorts of things. Terrifically well supported.

2) Drupal

Superb for content creation, and often used for large programming projects with the CMS acting as a framework. It features a rich API for managing content in a variety of formats, some of which are customised.

Industrial strength and well featured and supported with a library of themes and plug-ins.

For a website integrated with specialised software we would normally use Drupal.

3) Framework

Modern sites require complex pattern of combined requests that can be responded to activating new instances of replies to requests. For a true session interaction to occur it is best to program using modern design patterns. We are now achieving more with less, and this means rapid functionality and design implementations.

Best for potentially high volume sites. Custom software can fit your business model requirements but with a framework is helpful when you are evolving a service and expand its capability to deliver to many simultaneous users responsively for all of them.

Not all MVC systems will provide high speed sequential integrity for transactions but clear divisions of responsibility provide flexible data interfaces that make advanced database systems to be added when it is required.

We use a variety of frameworks for bespoke client projects.

4) Service orientated architecture SOA is a principal part of resource management from a working model to a high speed transaction integrity independent channelled data pool of results of instantiated process from abstract factories.

SOA used in coordination with other design patterns enable the queuing up and sequential processing of actions can be controlled as input and output queues with a process and session data attached that has a journey that ends up in transactions or other results.

The good thing about an SOA layer is that it provides a common footprint but it does not define yet how the system will react to session data.

5) Templated design and bespoke dynamic responsive or adaptive html/jQuery front-end systems.