Skip to main content
  1. Services/

Web Development & Design

2 mins
Table of Contents

We present a simple solution for scalable websites that rely on a content management system (CMS), with the use of a static site CMS (i.e. Decap CMS, or it’s fork Static CMS), an optional analytics platform like Plausible, and a static site generator (i.e. Hugo or Jekyll) you can quickly and efficiently deploy new pages to a website with a pipeline that works for you.

Why Static Sites? And, why this stack? #

  • Full In-House Control: Your data, your rules. You don’t have to give any monthly fees for Google Analytics or a managed hosting provider. Nothing is obfuscated, and all important details are at your fingertips. No data is collected of you or your users, Plausible is not just GDPR complaint but collects truly generalized data that still allows you to get the information you need without sacrificing user privacy.

  • Version Control: All your code resides in a Git repository alongside your content and a static site CMS is built to run CI/CD for your git repository. This means you can easily track all changes made to your website and quickly deploy it to a new server during an outage or upgrade.

  • Customization: Hugo brings a world of customization to your fingertips. Choose from a wide array of prebuilt themes or engage our team to draft a theme from scratch, perfectly tailored to you. We want to make it easy for your organization to have a snappy and reliable web presence. Take a look at the theme we used for this website.

  • Usability: Don’t sacrifice the usability afforded by tools like WordPress, most static site content management platforms we use and recommend provide a helpful UI to walk you through the process of managing your website. Static CMS demo.

Cost Savings #

All of these services can be entirely self-hosted on a VPS that costs less than 5 dollars a month. Less than 15 dollars if your organization requires dedicated resources on your VPS.

Don’t want your Git repository to be running on an off-site server? Separate your pipeline into physically disparate servers by purchasing a machine to function as a local Git repository that is accessible from a public IP using a decentrialized system. Better yet, repurpose an old computer to function as your own mini home datacenter.