47 lines
1.5 KiB
Markdown
47 lines
1.5 KiB
Markdown
title: How to sneak in a static CMS
|
|
---
|
|
pub_date: 2019-09-24
|
|
---
|
|
author: Nico Schottelius
|
|
---
|
|
body:
|
|
|
|
## Introduction
|
|
|
|
To put you in the right mood for reading this article, I ask you
|
|
take some assumptions for reading this article:
|
|
|
|
Assume you are the CEO of a small IPv6, Linux and FOSS company. Assume
|
|
that some years ago you made the decision to use
|
|
[Django CMS Blog](https://github.com/nephila/djangocms-blog) for the
|
|
blog to support non-technical staff to post blog articles.
|
|
|
|
Also, for the sake of completeness, assume that you are still running
|
|
your own [private blog](https://www.nico.schottelius.org) with
|
|
[ikiwiki](http://ikiwiki.info).
|
|
|
|
## Motivation
|
|
|
|
I believe that before changing anything
|
|
([especially in IT](https://en.wikipedia.org/wiki/Not_invented_here)),
|
|
you should have a good reason for changing. So what could be
|
|
the reason for sneaking in a static CMS? The answer is relatively
|
|
easy:
|
|
|
|
* Reducing latency
|
|
* Reducing latency
|
|
* Reducing the inhibition threshold for writing blog articles
|
|
|
|
Let's have a look at each of the points in detail,
|
|
[before letting us convince
|
|
ourselves...](https://en.wikipedia.org/wiki/Not_invented_here).
|
|
|
|
### Reducing latency
|
|
|
|
One of the biggest problems for me is to wait for an web application
|
|
to *save* something. With Django CMS Blog, you have the standard
|
|
**write - save - publish flow**. So when I want to see the result, I
|
|
have to wait seconds. Depending on my distance to our blog this might
|
|
take 1 second (Europe) or about 5 seconds (South Korea). While this
|
|
does not sound like much, it **feels** very long.
|