Static built websites

If your website will not be updated that frequently and you would rather have the agency make the updates for you, it would be better to build the site in a static site generator. This means that there is no need for any preventative maintenance and hosting fees will be a lot smaller because the website will not use a database and media files will be monitored by the agency.

Some of the static site generators we love to work in are:

Static site generators can have content management systems built in to them, but this usually comes with a third-party licensing cost that is paid on a monthly basis.

The reason why we love static site generators is because when we generate the build of the website, it creates static compressed HTML, CSS and JavaScript files that are extremely fast to load.

There is no database the website is connecting to, as the data all lives within the html pages. This means that we are rendering straight HTML pages, the server does not have to spend time translating other programming languages like PHP or .NET in to HTML (faster load) and with no database connection less time is being spent by the server fetching, retrieving and translating then rendering information as simple as text.

By doing this, you’re automatically complying with Google’s requirement of page speed load time. Then you add our little structural coding tricks in the mix a voila! A lightning fast website that is scoring above 95/100 on the Google page Speed Test.

CMS (Content Management System) built websites

If your website requires a blog or frequent content updates by people within your organisation, then it’s best to build in to a platform that will give you or people in your organisation access to the content of the website through an administration panel. You can also restrict access to certain roles in the organisation so that people only have access to certain sections for updates.

The most popular content management for information website we use is WordPress as it has the cleanest and easiest to use interface for administrators. When we build our WordPress websites, we only use the engine (back end platform) from WordPress for administrators to be able to create bits of content easily, and then tie that in to a completely custom front end website that is driven by the content that the administrator ads in to the Content Management System.

what method is the right one for you?

The above is a very high level overview on the pro’s and cons of each method. To be 100% sure you’re getting the right type of build, consult a professional.

Feel free to contact us directly