content/posts/leopold.md

@@ -59,19 +59,13 @@ Fortunately, there are already a number of actively developed libraries and fram
 So for a relatively basic CMS, in which there are no particularly special requirements, it makes perfect sense to make use of a pre-existing platform.
 In this case, I chose **October** for a number for reasons.
 
-{{<
-figure
-class="cheat-october-list"
-src=""
-alt="TODO - do properly with shortcode"
->}}
 * **Performant**
 
   October isn't bloated with unneeded functionality.
 
   It instead provides a base in which features and functionality may be added if required.
   This makes it faster than some alternatives, such as WordPress for example, which can suffer from having a large amount of features included as a base.
-  It also has useful default features such as minification of CSS and JavaScript. The templating engine, Twig, generates static HTML, giving the speed benefits of a static site, without database lookups.
+  It also has useful default features such as minification of CSS and JavaScript. The templating engine, Twig, generates static HTML.
 
 * **Developer Oriented**
 

static/css/custom.css

@@ -137,42 +137,3 @@ body.colorscheme-light .avatar img {
     display: none;
   }
 }
-
-/* TODO do this properly using a shortcode */
-.cheat-october-list {
-  display: none;
-}
-
-.cheat-october-list + ul {
-  margin-top: 0;
-  margin-bottom: 0;
-  padding-left: 0;
-}
-
-.cheat-october-list + ul > li {
-  list-style: none;
-}
-
-.cheat-october-list + ul > li > p:first-child {
-  position: relative;
-  margin-top: 0;
-  padding-left: 40px;
-}
-
-.cheat-october-list + ul > li > p:not(:first-child) {
-  padding-left: 40px;
-}
-
-.cheat-october-list + ul > li > p:first-child::before {
-  /* list-style-image: url(/images/logos/october-icon.png); */
-  content: "";
-  position: absolute;
-  display: block;
-  top: 0.2em;
-  bottom: 0.2em;
-  left: 0;
-  right: 0;
-  background-size: contain;
-  background-repeat: no-repeat;
-  background-image: url(/images/logos/october-icon.png);
-}