We embrace Static Site generators which is an exciting new way of building websites and apps that delivers better performance, higher security, lower cost of scaling, and a better overall experience.
It feels like we’re going back to the 90’s by creating ‘static sites’ but when you look under the hood, modern day technology and tooling has unlocked dynamic ways of creating websites that compiles it into a static resources which provides a host of benefits.
If the benefits below do not convinced you, then consider that the future of the web is moving away from the monolithic backend and rather made up of a collection of microservices that perform one task and one task well. So in separating the concerns (Your backend, content and presentation layer) is your best option to provide the most flexibility in future.
Websites built with static site generators are characterised by insanely fast loading times.
There is no complex code to serve each time a user visits thus scalability is no longer a headache.
Everything is managed through version control so we have a complete history of all changes.
With static assets you gain immunity against malicious attacks, Static Sites are very secure.
With a decoupled backend / front-end we can change the one without affecting the other.
All development is hand written and we’re not tied into anything only a specific platform can or can’t do.
The future of the web is mobile, it needs to be fast and lightweight not costing our users heavy data or loading times.
We are open to use any backend CMS technology to house your content. For most projects we’ve created custom WordPress backend content management systems specific to the clients requirements to ensure they still have the best editing experience. There is no difference to the client and we have the required hooks in place to recompile the static site when content changes.
The initial inkling is that recompiling the static site on a content or code change is bad for performance, but the really is that it is really efficient. For the majority of websites the content changes far less often that there are page loads. Some static site generators can convert up to 1000 pages a second, and this does not affect your live site. Only once the site has been regenerated would it replace the live site.
The alternative (Server Side Rendering) means that your page is compiled on the server before it is returned to the client (browser) on each page load. Even if this is a 1 or 2 second process it escalates quickly when you scale your site to a couple of thousand users, putting more strain on your server.
If we consider a publisher’s website as an example, they might get 100,000’s page views a day and publish 20 new stories. Rebuilding a static site 20 times a day would still be far more efficient that server side rendering 100,000’s times a day.
Are you ready to make the leap to a static sites with the host of benefits mentioned above? Talk to us and we will guide you along the path of choosing the best solutions and strategies for your specific case to ensure the best possible solution.