diff --git a/assets/scss/_posts.scss b/assets/scss/_posts.scss
index ffd30ed..0583c3a 100644
--- a/assets/scss/_posts.scss
+++ b/assets/scss/_posts.scss
@@ -82,6 +82,10 @@
     }
 }
 
+.featured-image img {
+    width: 100%;
+}
+
 #posts-footer {
     display: flex;
     flex-direction: column;
@@ -117,6 +121,10 @@
             outline-color: darkslateblue;
             color: slateblue;
         }
+
+        img {
+            width: 100%;
+        }
     }
 
 }
diff --git a/assets/scss/style.scss b/assets/scss/style.scss
index c311178..957bdc4 100644
--- a/assets/scss/style.scss
+++ b/assets/scss/style.scss
@@ -103,3 +103,21 @@ body {
         }
     }
 }
+
+blockquote {
+    border-left: .25em solid;
+    margin: 1em;
+    padding: 0 1em;
+    font-style: italic;
+
+    cite {
+      font-style: normal;
+      display: flex;
+      justify-content: end;
+      gap: 6px;
+
+      &::before {
+        content: "—— ";
+      }
+    }
+  }
diff --git a/config.toml b/config.toml
index fdc0669..1d800bf 100644
--- a/config.toml
+++ b/config.toml
@@ -26,6 +26,11 @@ paginate = 5
     style = 'github'
     tabWidth = 4
 
+  [markup.goldmark]
+    [markup.goldmark.renderer]
+      unsafe = true
+
+
 [languages]
   [languages.tr]
     disabled = false
diff --git a/content/posts/2021ramazan/index.md b/content/posts/2021ramazan/index.md
new file mode 100644
index 0000000..bd8b12c
--- /dev/null
+++ b/content/posts/2021ramazan/index.md
@@ -0,0 +1,23 @@
+---
+title: "Bu Ramazan'ın Özeti"
+date: 2021-12-05T04:40:02Z
+draft: false
+toc: false
+featuredImg: japon.jpg
+tags:
+  - günlük
+---
+
+Yaklaşık bir ay önce başlanılmış ramazan macerasının “yeniden” sonuna geldik. Yeniden, çünkü her sene çıkılan bir macera bu. Belki ondandır içimde derin bir hüzün yok, yalnızca hafif bir iç burukluğu, seneye tekrardan geleceğini biliyorum nasıl olsa. Tabii bir daha gelecek diye bu kısa zaman dilimini küçümsemiyorum, zira hipotezlerime göre “ramazan algısı” hesaplanırken o güne kadar geçirdiğin tüm ramazanlar hesaba katılıyor.
+
+Ne yaşarsanız yaşayın, tecrübeleri “iyi” veya “kötü” olarak değerlendirmek çok zordur. Çünkü yaşadığınız tüm olaylar size bir şey öğretir. Tabii “iyi” tecrübeleriniz çoksa buna mutlu veya başarılı hayat diyoruz, “kötü” tecrübelerinizin çok olması ise, düşe kalka ilerleyen bir hayatınız olduğu anlamına geliyor. Düştükten sonra kalkmayanları ve iyi-kötü bir hayata sahip olanları konunun dışında tutuyorum. Şimdi bu bakış açısıyla bakacak olursak, ramazan nasıl geçti?
+
+En başta çok hareketli geçmediğini söyleyebilirim. Çoğunlukla evimde, bilgisayarımın başındaydım. Yalnız günde 30, 40 dakika yürüyüş yapmaya gayret ettim, duyduğuma göre bu kan dolaşımına faydalıymış hatta neredeyse sağıklı bir kardiyovasküler sistem için zaruriymiş. Bu 30, 40 dakikayı saymazsak, çoğunlukla ders çalışarak, oyun oynayarak, anime izleyerek bitirdim bu ramazanı (yaklaşık 100 saat oyun oynadım ve 3 tane anime serisini bitirdim, ders çalışma süremin de yüksek olmasını umuyorum, detaylı hesaplamalara girişmeyeceğim *öhöm öhöm*).
+
+Manevi olarak gayet kurak bir dönemdi. İbadetimde diğer aylara nazaran -oruç tutmak dışında- bir fazlalık yoktu. Açıkçası bu üzücü bir gerçek, inşallah gelecek ramazanlarda durum değişir?
+
+Sosyal açıdan, arkadaşlarımla telefonda görüşmeyi saymazsak manevi hayatımdan bile daha kurak bir dönem oldu. Yani olmadı desem de olur herhalde. Bu da bulunduğumuz halin iktiza ettiği bir durum olsa gerek, çünkü geçmiş ramazanlarım böyle geçmemişti. Zaten okul vardı, arkadaşlar ile muhabbet sohbet, neyse işte…
+
+Hülasa, “iyiliği” “kötülüğü” bir yana, görünüşe göre bu ramazan oldukça sessiz, hareketsiz ve yalnız geçmiş. Aslında bu sonuç beni üzmeli ama o kadar uzun süredir böyle yaşıyorum ki şu an umurumda bile değil. Bakalım gelecek ramazanlar nasıl geçecek.
+
+Allah kabul etsin, daha nice ramazanlara.
diff --git a/content/posts/2021ramazan/japon.jpg b/content/posts/2021ramazan/japon.jpg
new file mode 100644
index 0000000..a681867
Binary files /dev/null and b/content/posts/2021ramazan/japon.jpg differ
diff --git a/content/posts/goisforlovers.en.md b/content/posts/goisforlovers.en.md
deleted file mode 100644
index a5d639d..0000000
--- a/content/posts/goisforlovers.en.md
+++ /dev/null
@@ -1,340 +0,0 @@
-+++
-title = "Yazmak Güzeldir"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2014-04-02"
-+++
-
-Hugo and uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-```go
-{{ foo }} asdadasdasad
-```
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers.md b/content/posts/goisforlovers.md
deleted file mode 100644
index 7ef92a5..0000000
--- a/content/posts/goisforlovers.md
+++ /dev/null
@@ -1,347 +0,0 @@
-+++
-title = "Yazmak Güzeldir"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2014-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-```go
-package main
-
-import "fmt"
-
-func main() {
-    fmt.Println("hello world")
-}
-```
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers2.md b/content/posts/goisforlovers2.md
deleted file mode 100644
index 7425e85..0000000
--- a/content/posts/goisforlovers2.md
+++ /dev/null
@@ -1,339 +0,0 @@
-+++
-title = "Lorem Ipsum"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2015-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers3.md b/content/posts/goisforlovers3.md
deleted file mode 100644
index a8a3c45..0000000
--- a/content/posts/goisforlovers3.md
+++ /dev/null
@@ -1,339 +0,0 @@
-+++
-title = "With The Help of God"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2016-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers4.md b/content/posts/goisforlovers4.md
deleted file mode 100644
index 3406844..0000000
--- a/content/posts/goisforlovers4.md
+++ /dev/null
@@ -1,339 +0,0 @@
-+++
-title = "Dolor Sit Amet"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2017-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers5.md b/content/posts/goisforlovers5.md
deleted file mode 100644
index e08187a..0000000
--- a/content/posts/goisforlovers5.md
+++ /dev/null
@@ -1,339 +0,0 @@
-+++
-title = "The Excellent Hugo"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2018-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers6.md b/content/posts/goisforlovers6.md
deleted file mode 100644
index 0984d17..0000000
--- a/content/posts/goisforlovers6.md
+++ /dev/null
@@ -1,339 +0,0 @@
-+++
-title = "Is There a Way Back?"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2019-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers7.md b/content/posts/goisforlovers7.md
deleted file mode 100644
index 0e1ecdf..0000000
--- a/content/posts/goisforlovers7.md
+++ /dev/null
@@ -1,339 +0,0 @@
-+++
-title = "Forget About the Past"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2020-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers8.md b/content/posts/goisforlovers8.md
deleted file mode 100644
index e4f3dbb..0000000
--- a/content/posts/goisforlovers8.md
+++ /dev/null
@@ -1,339 +0,0 @@
-+++
-title = "Commemoration"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2021-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/goisforlovers9.md b/content/posts/goisforlovers9.md
deleted file mode 100644
index 4248e30..0000000
--- a/content/posts/goisforlovers9.md
+++ /dev/null
@@ -1,339 +0,0 @@
-+++
-title = "Internation Business"
-tags = [
-    "go",
-    "golang",
-    "templates",
-    "themes",
-    "development",
-]
-date = "2022-04-02"
-toc = true
-+++
-
-Hugo uses the excellent [Go][] [html/template][gohtmltemplate] library for
-its template engine. It is an extremely lightweight engine that provides a very
-small amount of logic. In our experience that it is just the right amount of
-logic to be able to create a good static website. If you have used other
-template systems from different languages or frameworks you will find a lot of
-similarities in Go templates.
-
-This document is a brief primer on using Go templates. The [Go docs][gohtmltemplate]
-provide more details.
-
-## Introduction to Go Templates
-
-Go templates provide an extremely simple template language. It adheres to the
-belief that only the most basic of logic belongs in the template or view layer.
-One consequence of this simplicity is that Go templates parse very quickly.
-
-A unique characteristic of Go templates is they are content aware. Variables and
-content will be sanitized depending on the context of where they are used. More
-details can be found in the [Go docs][gohtmltemplate].
-
-## Basic Syntax
-
-Golang templates are HTML files with the addition of variables and
-functions.
-
-**Go variables and functions are accessible within {{ }}**
-
-Accessing a predefined variable "foo":
-
-    {{ foo }}
-
-**Parameters are separated using spaces**
-
-Calling the add function with input of 1, 2:
-
-    {{ add 1 2 }}
-
-**Methods and fields are accessed via dot notation**
-
-Accessing the Page Parameter "bar"
-
-    {{ .Params.bar }}
-
-**Parentheses can be used to group items together**
-
-    {{ if or (isset .Params "alt") (isset .Params "caption") }} Caption {{ end }}
-
-
-## Variables
-
-Each Go template has a struct (object) made available to it. In hugo each
-template is passed either a page or a node struct depending on which type of
-page you are rendering. More details are available on the
-[variables](/layout/variables) page.
-
-A variable is accessed by referencing the variable name.
-
-    <title>{{ .Title }}</title>
-
-Variables can also be defined and referenced.
-
-    {{ $address := "123 Main St."}}
-    {{ $address }}
-
-
-## Functions
-
-Go template ship with a few functions which provide basic functionality. The Go
-template system also provides a mechanism for applications to extend the
-available functions with their own. [Hugo template
-functions](/layout/functions) provide some additional functionality we believe
-are useful for building websites. Functions are called by using their name
-followed by the required parameters separated by spaces. Template
-functions cannot be added without recompiling hugo.
-
-**Example:**
-
-    {{ add 1 2 }}
-
-## Includes
-
-When including another template you will pass to it the data it will be
-able to access. To pass along the current context please remember to
-include a trailing dot. The templates location will always be starting at
-the /layout/ directory within Hugo.
-
-**Example:**
-
-    {{ template "chrome/header.html" . }}
-
-
-## Logic
-
-Go templates provide the most basic iteration and conditional logic.
-
-### Iteration
-
-Just like in Go, the Go templates make heavy use of range to iterate over
-a map, array or slice. The following are different examples of how to use
-range.
-
-**Example 1: Using Context**
-
-    {{ range array }}
-        {{ . }}
-    {{ end }}
-
-**Example 2: Declaring value variable name**
-
-    {{range $element := array}}
-        {{ $element }}
-    {{ end }}
-
-**Example 2: Declaring key and value variable name**
-
-    {{range $index, $element := array}}
-        {{ $index }}
-        {{ $element }}
-    {{ end }}
-
-### Conditionals
-
-If, else, with, or, & and provide the framework for handling conditional
-logic in Go Templates. Like range, each statement is closed with `end`.
-
-
-Go Templates treat the following values as false:
-
-* false
-* 0
-* any array, slice, map, or string of length zero
-
-**Example 1: If**
-
-    {{ if isset .Params "title" }}<h4>{{ index .Params "title" }}</h4>{{ end }}
-
-**Example 2: If -> Else**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{else}}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-**Example 3: And & Or**
-
-    {{ if and (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-
-**Example 4: With**
-
-An alternative way of writing "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent.
-
-The first example above could be simplified as:
-
-    {{ with .Params.title }}<h4>{{ . }}</h4>{{ end }}
-
-**Example 5: If -> Else If**
-
-    {{ if isset .Params "alt" }}
-        {{ index .Params "alt" }}
-    {{ else if isset .Params "caption" }}
-        {{ index .Params "caption" }}
-    {{ end }}
-
-## Pipes
-
-One of the most powerful components of Go templates is the ability to
-stack actions one after another. This is done by using pipes. Borrowed
-from unix pipes, the concept is simple, each pipeline's output becomes the
-input of the following pipe.
-
-Because of the very simple syntax of Go templates, the pipe is essential
-to being able to chain together function calls. One limitation of the
-pipes is that they only can work with a single value and that value
-becomes the last parameter of the next pipeline.
-
-A few simple examples should help convey how to use the pipe.
-
-**Example 1 :**
-
-    {{ if eq 1 1 }} Same {{ end }}
-
-is the same as
-
-    {{ eq 1 1 | if }} Same {{ end }}
-
-It does look odd to place the if at the end, but it does provide a good
-illustration of how to use the pipes.
-
-**Example 2 :**
-
-    {{ index .Params "disqus_url" | html }}
-
-Access the page parameter called "disqus_url" and escape the HTML.
-
-**Example 3 :**
-
-    {{ if or (or (isset .Params "title") (isset .Params "caption")) (isset .Params "attr")}}
-    Stuff Here
-    {{ end }}
-
-Could be rewritten as
-
-    {{  isset .Params "caption" | or isset .Params "title" | or isset .Params "attr" | if }}
-    Stuff Here
-    {{ end }}
-
-
-## Context (aka. the dot)
-
-The most easily overlooked concept to understand about Go templates is that {{ . }}
-always refers to the current context. In the top level of your template this
-will be the data set made available to it. Inside of a iteration it will have
-the value of the current item. When inside of a loop the context has changed. .
-will no longer refer to the data available to the entire page. If you need to
-access this from within the loop you will likely want to set it to a variable
-instead of depending on the context.
-
-**Example:**
-
-      {{ $title := .Site.Title }}
-      {{ range .Params.tags }}
-        <li> <a href="{{ $baseurl }}/tags/{{ . | urlize }}">{{ . }}</a> - {{ $title }} </li>
-      {{ end }}
-
-Notice how once we have entered the loop the value of {{ . }} has changed. We
-have defined a variable outside of the loop so we have access to it from within
-the loop.
-
-# Hugo Parameters
-
-Hugo provides the option of passing values to the template language
-through the site configuration (for sitewide values), or through the meta
-data of each specific piece of content. You can define any values of any
-type (supported by your front matter/config format) and use them however
-you want to inside of your templates.
-
-
-## Using Content (page) Parameters
-
-In each piece of content you can provide variables to be used by the
-templates. This happens in the [front matter](/content/front-matter).
-
-An example of this is used in this documentation site. Most of the pages
-benefit from having the table of contents provided. Sometimes the TOC just
-doesn't make a lot of sense. We've defined a variable in our front matter
-of some pages to turn off the TOC from being displayed.
-
-Here is the example front matter:
-
-```
----
-title: "Permalinks"
-date: "2013-11-18"
-aliases:
-  - "/doc/permalinks/"
-groups: ["extras"]
-groups_weight: 30
-notoc: true
----
-```
-
-Here is the corresponding code inside of the template:
-
-      {{ if not .Params.notoc }}
-        <div id="toc" class="well col-md-4 col-sm-6">
-        {{ .TableOfContents }}
-        </div>
-      {{ end }}
-
-
-
-## Using Site (config) Parameters
-In your top-level configuration file (eg, `config.yaml`) you can define site
-parameters, which are values which will be available to you in chrome.
-
-For instance, you might declare:
-
-```yaml
-params:
-  CopyrightHTML: "Copyright &#xA9; 2013 John Doe. All Rights Reserved."
-  TwitterUser: "spf13"
-  SidebarRecentLimit: 5
-```
-
-Within a footer layout, you might then declare a `<footer>` which is only
-provided if the `CopyrightHTML` parameter is provided, and if it is given,
-you would declare it to be HTML-safe, so that the HTML entity is not escaped
-again.  This would let you easily update just your top-level config file each
-January 1st, instead of hunting through your templates.
-
-```
-{{if .Site.Params.CopyrightHTML}}<footer>
-<div class="text-center">{{.Site.Params.CopyrightHTML | safeHtml}}</div>
-</footer>{{end}}
-```
-
-An alternative way of writing the "if" and then referencing the same value
-is to use "with" instead. With rebinds the context `.` within its scope,
-and skips the block if the variable is absent:
-
-```
-{{with .Site.Params.TwitterUser}}<span class="twitter">
-<a href="https://twitter.com/{{.}}" rel="author">
-<img src="/images/twitter.png" width="48" height="48" title="Twitter: {{.}}"
- alt="Twitter"></a>
-</span>{{end}}
-```
-
-Finally, if you want to pull "magic constants" out of your layouts, you can do
-so, such as in this example:
-
-```
-<nav class="recent">
-  <h1>Recent Posts</h1>
-  <ul>{{range first .Site.Params.SidebarRecentLimit .Site.Recent}}
-    <li><a href="{{.RelPermalink}}">{{.Title}}</a></li>
-  {{end}}</ul>
-</nav>
-```
-
-
-[go]: https://golang.org/
-[gohtmltemplate]: https://golang.org/pkg/html/template/
diff --git a/content/posts/im22andfailed.en.md b/content/posts/im22andfailed.en.md
new file mode 100644
index 0000000..4f818c6
--- /dev/null
+++ b/content/posts/im22andfailed.en.md
@@ -0,0 +1,16 @@
+---
+title: "I'm 22 and I Failed"
+date: 2021-09-18T04:15:04Z
+draft: false
+toc: false
+tags:
+  - diary
+---
+
+Yeah, it's been 22 years living, 8 years coding. It was all fun at the beginning. I and friends were making cool flash animations--there was flash once, we even tried to make a shooter game with 3D graphics. Then I jumped into the world of coding. I was reading books, coding small things, eating popcorn while watching edX courses. I was constantly shifting my focus, different programming languages, different platforms, cool new technologies. Then I had to decide on a university. I thought: "Hey, I don't want to deal with introductory python courses, and stupid freshmen, I want to be the cool computer wiz without a degree!". And I choose an arts bachelor for fun and easy scholarship, I had good marks.
+
+I think this was my first mistake, I didn't know university was actually all about the environment, I found myself surrounded by people talking and interested in boring history, sociology, psychology stuff, and completely ignorant of computers. Actually, I made some friends, I even loved psychology and philosophy. But still, I was spending my time alone in the library coding and learning while my friends were preparing their fifth response paper on Metamorphoses. I felt alone. After a while university began to tease me because of my low grades. And it was psychologically disturbing. I tried to balance my academic life and computer passion but I failed. And I couldn't leave the school because I was in need of that scholarship they were giving me. 3 years passed with this unbalanced life.
+
+6 months ago I decided to leave the school and I moved to an easier no-scholarship state university. And I began thinking about my career as a software engineer. How am I going to find a job? I began scrolling down LinkedIn job postings and found out I should be able to do "one thing" well. I should've mastered Django, Rails, Android, etc. "Yeah, I can make that!" I said, they said, "No, you don't have a degree, the only thing you have is an ugly GitHub page with unfinished or empty repos, go away!". They were right in a way, all these years all I was doing was having fun, I wasn't prepared for a job. But now I didn't have money, a scholarship, or any plan to earn a living. Parents went ugly, they said I was a careless, stupid, ignorant boy. I know they are not right. But I didn't know what to do. Life seemed so boring, and meaningless. Wished I'd die. But then I pulled myself together and accepted the challenge. There is no dying, I'll work hard and I'll find a job, not just "a job", someplace where I can have fun working. I know the next 3-4 months won't be easy but I know I can do it.
+
+See you there!
diff --git a/content/posts/karar/index.md b/content/posts/karar/index.md
new file mode 100644
index 0000000..67ddf72
--- /dev/null
+++ b/content/posts/karar/index.md
@@ -0,0 +1,19 @@
+---
+title: "Karar"
+date: 2021-05-25T04:19:40Z
+draft: false
+toc: false
+featuredImg: "spiral.jpg"
+tags:
+  - günlük
+---
+
+İnsan karar verirken aklını veya duygularını önceler. Yalnız bazı durumlarda ikisini de öncelemez. Yalnızca bir seçeneğin bulunduğu koşullarda, halde, psikolojide, çevrede verilebilecek en iyi karar olduğunu fark eder. Diğer seçenekleri yanlış yapmaz bu, hayır, mesele çoktan doğru/yanlış mevzusunu aşmıştır. İnsan düşündükçe fark eder ki, aklı başında olan için yanlış karar yoktur. Belki sonuçlarını yüklenemeyeceği kararlar vardır.
+
+Bendeniz de 1 haftalık tefekkürün ardından bir karara vardım. Bu süreçte bir sürü arkadaşımla konuştum, “çocukça”, “saçma” diyen oldu, “altından kalkamazsın” diyen oldu, “acaba şöyle mı yapsan?” diyen oldu, “sen bu kadar basit bir insansın işte, her işi yarım bırakırsın, senin gibileri çok gördük, rezil olacaksın, iki pezevenk, orospu için…” diyen oldu, birde “gönlünün sesini dinle bence” diyen oldu. Neticede herkes söyleyeceğini söyledi, karar verildi ve defter kapandı.
+
+Öncelikle verdiğim kararın aslında ne kadar ehemmiyetsiz olduğunu fark ettim, kendimi bir oyuncaktan farksız gördüm şu koca dünyada. Ardından hiç pişmanlık duymadığımı fark ettim, çünkü neredeyse hiç fedakarlıkta bulunmamıştım hayatımda. Pişmanlık duymak istedim, bir karar vermek, pişman olmak ve hatamı telafiye çalışmak. Bunu güçlü bir motivasyon olduğunu sezdim. Ayrıca anladım ki bu umursamazlığım, dertsizliğim, “başkalarının kararlarını” vermemle alakalıymış. Komşu komşunun eşeğini türkü çığırarak ararmış ya, benzer bir durum. Benimsemedikçe eşya kıymetsiz…
+
+Ve evet, sonunda bir karar verdim, pişman olmak veya olmamak umrumda değil ama pişman olmamak için elimden geleni yapacağım.
+
+Gelecek geliyor...
diff --git a/content/posts/karar/spiral.jpg b/content/posts/karar/spiral.jpg
new file mode 100644
index 0000000..c9e8d41
Binary files /dev/null and b/content/posts/karar/spiral.jpg differ
diff --git a/content/posts/relife/index.md b/content/posts/relife/index.md
new file mode 100644
index 0000000..7915a03
--- /dev/null
+++ b/content/posts/relife/index.md
@@ -0,0 +1,53 @@
+---
+title: "Relife"
+date: 2023-12-11T04:43:49Z
+draft: false
+toc: false
+featuredImg: relife1.png
+tags:
+  - anime
+---
+
+
+## Genel Bilgiler
+
+- Yayın Yılı: 2016
+- Stüdyo: TMS
+- Bölüm: 13
+- Tür: Hayattan Kesitler, Romantik, Okul
+
+## İnceleme
+
+Kaizaki Arata, bir baltaya sap olamamış, travmatik yetişkin hayatına uyum sağlayamamış, yıkık, mutsuz ve yalnız bir “neet”tir. Bir gece vakti, yarı uyanık yarı sarhoş, sokakta sendeleye sendeleye yürürken “ReLife” Labaratuvarları’nın bir çalışanı tarafından durdurulur ve kendisine oldukça tuhaf bir teklif sunulur: bir seneliğine liseye geri dönmek!
+
+Ayağına gelen bu fırsatı geri tepmek istemeyen Kaizaki, teklifi kabul eder ve kendisi henüz bilmesede hayatını tümden değiştirecek bir serüvene adımını atmış olur.
+
+Hikayenin ana teması, Kaizaki’nin bu süreçte edindiği arkadaşları ve onlarla maceraları. Tabii 27 yaşındaki bir adamın alınıp da liseye konulması pek çok komikliklere, tuhaflıklara yol açıyor. Zamanla kendini sınıfın sosyal ilişkiler danışmanı olarak bulan Kaizaki’nin sevenlerin arasını yapmasına, küskünleri barıştırmasına ve ilginç bir şekilde “ReLife” öncesi hayatının travmalarını da atlatmasına şahit oluyoruz.
+
+![Kaizaki Arata](relife.png)
+
+Serinin bu temayı oldukça başarılı bir şekilde işlediğini söylemek mümkün. Karakterlerimizin neredeyse tümü orijinal tipler, hepsinin değişik arkaplanları, karakterleri, mizaçları var. Bunları aynı sınıfa koyduğunuzda ortaya çıkan sosyal hayat da haliyle oldukça renkli oluyor. Yazarımız bunu güzel kurgulamış. Her birinin kendilerini aşma çabalarını seyretmek oldukça keyifli. Burada eleştirilebilecek bir nokta, zaman zaman bu yan karakterlerin üzerinde fazlaca durulması ve bunun ana karakterin hikayesini gölgede bırakması.
+
+> İnsanlarla geçinmenin mutlak bir kuralı yoktur, herkesin farklı beklentileri vardır.
+>
+> <cite>Kaizaki Arata</cite>
+
+Bunun dışında işlenen yan temalar da var. Mesela iş hayatına, bu hayatın ne kadar acımasız ve çetin olduğuna, insanların nasıl birbirlerinin kuyusunu kazdığına sık sık göndermeler yapılıyor. Zaten ileride de Kaizaki’nin bu hayattan çok çektiğini öğreniyoruz.
+
+Ayrıca hikayeye bir kaç adım geriden bakınca, tüm olanların aslında bir lise hayatı betimlemesi olduğunu fark ediyoruz. Sanki satır arasında bize şu söyleniyor: Lise, insanın kendini keşfettiği, sevmeyi ve arkadaş olmayı öğrendiği yerdir. Bu açıdan liseli okurlarımızın seriyi ayrıca beğeneceğini düşünüyorum.
+
+![Hishiro Chizuru](relife3.png)
+
+Hikayenin romantizmi seviyeli bir şekilde işlemesi oldukça sevindirici, öbür türlüsü ana temaya da zıt düşerdi doğrusu. Ama hikayede rahatsız edici bulduğum noktalar da yok değil. Mesela hikayenin sonu, hikayenin en önemli dinamiklerinden birini doğrudan yok sayıyor (spoiler vermek istemiyorum), bu tutarsızlık rahatsız edici. Daha sonra Arata’nın arkaplanı, yani ReLife öncesi hayatı nedense kulağa pek gerçekçi gelmiyor, biraz dramatize edilmiş gibi. Son olarak da şu Nabunaga ile Akira ikilisi var ki, “Niye oradalar?” diye soruyor insan. Nabunaga yine anlaşılabilir, babacan, sevecen bir karakter ama Akira, ölçüsüz, sert ve aşırı koruyucu tavırlarıyla "olmasa da olurmuş" tarzda bir karakter, arkadaşlarının yanında sırıtıyor açıkçası. Sasuke'nin seslendirmeni bile kurtaramamış kendisini.
+
+> Ne kadar güzel vakit geçirirsek, ayrıldığımızda o kadar üzüleceğiz.
+>
+> <cite>Hishiro Chizuru</cite>
+
+Sanatsal açıdan çok dikkat çekici bir tarafı yok ReLife’ın. Fakat pek çok sahne “chibification” dedikleri, dilimize “sevimlileştirme” olarak çevirebileceğimiz bir çizim tarzı ile zenginleştirilmiş (altta bir örneği var). Bunun dışında ortalama bir çizim kalitesine sahip. Serinin müziklerinde enstrüman olarak daha ziyade piyano tercih edilmiş, ayrıca neredeyse tüm bitiş müzikleri birbirinden farklı, bu da dikkat çekici bir unsur.
+
+Özetle ReLife bir lise hayatı draması. Neşeli, hüzünlü anlarıyla, tartışmaları, barışmalarıyla bize keyifli ve eğlenceli bir 12 bölüm vaadediyor. Okul animelerini seviyorsanız, biraz duygulanmak, biraz gülmek, biraz da dinlenmek istiyorsanız izlemeniz tavsiye olunur!
+
+![Kaizaki Arata](relife2.png)
+
+Yazımı okuduğunuz için teşekkür ederim!
diff --git a/content/posts/relife/relife.png b/content/posts/relife/relife.png
new file mode 100644
index 0000000..efecf7e
Binary files /dev/null and b/content/posts/relife/relife.png differ
diff --git a/content/posts/relife/relife1.png b/content/posts/relife/relife1.png
new file mode 100644
index 0000000..0cd5d11
Binary files /dev/null and b/content/posts/relife/relife1.png differ
diff --git a/content/posts/relife/relife2.png b/content/posts/relife/relife2.png
new file mode 100644
index 0000000..e5db81e
Binary files /dev/null and b/content/posts/relife/relife2.png differ
diff --git a/content/posts/relife/relife3.png b/content/posts/relife/relife3.png
new file mode 100644
index 0000000..3e17862
Binary files /dev/null and b/content/posts/relife/relife3.png differ
diff --git a/layouts/posts/single.html b/layouts/posts/single.html
index 4487765..9c7bb60 100644
--- a/layouts/posts/single.html
+++ b/layouts/posts/single.html
@@ -1,21 +1,8 @@
-{{ define "head" }}
-	{{ if .Params.featuredImg -}}
-	<style>.bg-img {background-image: url('{{.Params.featuredImg}}');}</style>
-	{{- else if .Params.images -}}
-		{{- range first 1 .Params.images -}}
-		<style>.bg-img {background-image: url('{{. | absURL}}');}</style>
-		{{- end -}}
-	{{- end -}}
-{{ end }}
-
 {{ define "header" }}
 {{ partial "post/header.html" . }}
 {{ end }}
 
 {{ define "main" }}
-	{{- if (or .Params.images .Params.featuredImg) }}
-	<div class="bg-img"></div>
-	{{- end }}
 	<main class="site-main section-inner animated fadeIn faster">
 		<article class="thin">
 			<header class="post-header">
@@ -27,6 +14,13 @@
 				</div>
 				{{- end }}
 			</header>
+
+			{{- if (or .Params.images .Params.featuredImg) }}
+			<div class="featured-image">
+				<img src="{{.Params.featuredImg}}">
+			</div>
+			{{- end }}
+
 			<div class="post-content">
 				{{ .Content | safeHTML }}
 			</div>
diff --git a/resources/_gen/assets/scss/scss/style.scss_871e1d33253f63f556fbcaa4227752be.content b/resources/_gen/assets/scss/scss/style.scss_871e1d33253f63f556fbcaa4227752be.content
index 83b3d92..615697f 100644
--- a/resources/_gen/assets/scss/scss/style.scss_871e1d33253f63f556fbcaa4227752be.content
+++ b/resources/_gen/assets/scss/scss/style.scss_871e1d33253f63f556fbcaa4227752be.content
@@ -1 +1 @@
-.bg{background-color:#fff}.chroma{background-color:#fff;padding:16px;border-radius:4px;border:1px dashed grey}.chroma .err{color:#a61717;background-color:#e3d2d2}.chroma .lnlinks{outline:none;text-decoration:none;color:inherit}.chroma .lntd{vertical-align:top;padding:0;margin:0;border:0}.chroma .lntable{border-spacing:0;padding:0;margin:0;border:0}.chroma .hl{background-color:#e5e5e5}.chroma .lnt{white-space:pre;-webkit-user-select:none;user-select:none;margin-right:.4em;padding:0 .4em;color:#7f7f7f}.chroma .ln{white-space:pre;-webkit-user-select:none;user-select:none;margin-right:.4em;padding:0 .4em;color:#7f7f7f}.chroma .line{display:flex}.chroma .k{color:#000;font-weight:700}.chroma .kc{color:#000;font-weight:700}.chroma .kd{color:#000;font-weight:700}.chroma .kn{color:#000;font-weight:700}.chroma .kp{color:#000;font-weight:700}.chroma .kr{color:#000;font-weight:700}.chroma .kt{color:#458;font-weight:700}.chroma .na{color:teal}.chroma .nb{color:#0086b3}.chroma .bp{color:#999}.chroma .nc{color:#458;font-weight:700}.chroma .no{color:teal}.chroma .nd{color:#3c5d5d;font-weight:700}.chroma .ni{color:purple}.chroma .ne{color:#900;font-weight:700}.chroma .nf{color:#900;font-weight:700}.chroma .nl{color:#900;font-weight:700}.chroma .nn{color:#555}.chroma .nt{color:navy}.chroma .nv{color:teal}.chroma .vc{color:teal}.chroma .vg{color:teal}.chroma .vi{color:teal}.chroma .s{color:#d14}.chroma .sa{color:#d14}.chroma .sb{color:#d14}.chroma .sc{color:#d14}.chroma .dl{color:#d14}.chroma .sd{color:#d14}.chroma .s2{color:#d14}.chroma .se{color:#d14}.chroma .sh{color:#d14}.chroma .si{color:#d14}.chroma .sx{color:#d14}.chroma .sr{color:#009926}.chroma .s1{color:#d14}.chroma .ss{color:#990073}.chroma .m{color:#099}.chroma .mb{color:#099}.chroma .mf{color:#099}.chroma .mh{color:#099}.chroma .mi{color:#099}.chroma .il{color:#099}.chroma .mo{color:#099}.chroma .o{color:#000;font-weight:700}.chroma .ow{color:#000;font-weight:700}.chroma .c{color:#998;font-style:italic}.chroma .ch{color:#998;font-style:italic}.chroma .cm{color:#998;font-style:italic}.chroma .c1{color:#998;font-style:italic}.chroma .cs{color:#999;font-weight:700;font-style:italic}.chroma .cp{color:#999;font-weight:700;font-style:italic}.chroma .cpf{color:#999;font-weight:700;font-style:italic}.chroma .gd{color:#000;background-color:#fdd}.chroma .ge{color:#000;font-style:italic}.chroma .gr{color:#a00}.chroma .gh{color:#999}.chroma .gi{color:#000;background-color:#dfd}.chroma .go{color:#888}.chroma .gp{color:#555}.chroma .gs{font-weight:700}.chroma .gu{color:#aaa}.chroma .gt{color:#a00}.chroma .gl{text-decoration:underline}.chroma .w{color:#bbb}#home-main{display:flex;flex-direction:column;align-items:start;justify-content:space-between;height:100vh;max-width:720px;margin:auto;font-size:1.5rem}@media(max-width:768px){#home-main{margin-left:24px}}#home-center{display:flex;flex-direction:column;align-items:flex-start;margin-top:16vh}#home-nav{display:flex;flex-direction:column}#home-nav a{color:#252525;font-family:inter,sans-serif;font-size:40px;font-style:normal;font-weight:400;line-height:150%;text-decoration-line:underline}#posts-body{max-width:720px;margin:auto;display:flex;flex-direction:column;justify-content:start;height:100vh;margin-bottom:0}@media(max-width:768px){#posts-body{margin:0 24px}}#posts-list{display:flex;flex-direction:column}#posts-header{padding-top:10vh;font-size:20px;font-style:normal;font-weight:400}#posts-header a{text-decoration:none;color:#656565}#posts-header a:hover{text-decoration:underline;color:#151515}#post-header{padding-top:10vh}#post-header a{text-decoration:none;color:#656565}#post-header a:hover{text-decoration:underline;color:#151515}#post-title{font-size:2.5em;font-weight:400;margin-bottom:8px}.post-meta{font-size:1.5em}.post-meta span{color:#303030}.post-tags{margin:10px 0;display:flex;gap:6px}.post-tags .tag{font-size:.9em;padding:3px 14px;text-transform:lowercase;border:1px solid;margin-bottom:6px}.post-tags .tag a{outline:none;text-decoration:none;color:#5c5c5c;font-weight:500}#posts-footer{display:flex;flex-direction:column;flex-grow:1;justify-content:end}.post-item a{color:#252525;font-weight:400;line-height:150%;text-decoration-line:underline;font-size:2em}.post-content{font-size:1.3em;color:#202020;line-height:1.4}.post-content h2{border-bottom:1px solid rgba(71,61,139,.5)}.post-content p{text-align:justify}.post-content p a{text-decoration-line:none;text-decoration-style:solid;text-decoration-color:#483d8b;outline-color:#483d8b;color:#6a5acd}.post-to-top-link{text-decoration:none;color:#656565}.post-to-top-link:hover{text-decoration:underline;color:#151515}body{font-family:inter,sans-serif;line-height:1.4;background-color:#ebf4f3;margin:0}#header-title{color:#202020;font-family:inter,sans-serif;font-style:normal;font-weight:500;line-height:normal}.post-header{margin-bottom:40px}#site-footer{width:100%}#site-footer p{color:#5c5c5c;font-family:Inter;font-size:20px;font-style:normal;font-weight:300;line-height:normal;display:flex;gap:8px;justify-content:center}#site-footer a{color:#5c5c5c;font-family:Inter;font-size:20px;font-style:normal;font-weight:300;line-height:normal;display:flex;gap:8px;justify-content:center;text-decoration:none}#site-footer a:hover{text-decoration:underline}.pagination{display:flex;list-style:none;padding:0;margin:0;justify-content:center;align-items:center;font-family:Inter}.pagination a{text-decoration:none;color:#252525}.pagination .page-item{margin:0}.pagination .page-link{display:block;padding:5px 10px;margin:0 2px}#site-footer{width:100%;user-select:none}#site-footer #copyright{display:flex;align-items:center;justify-content:center}[aria-disabled=true]{text-decoration:none!important}.page-item.active a{text-decoration:none!important}
\ No newline at end of file
+@charset "UTF-8";.bg{background-color:#fff}.chroma{background-color:#fff;padding:16px;border-radius:4px;border:1px dashed grey}.chroma .err{color:#a61717;background-color:#e3d2d2}.chroma .lnlinks{outline:none;text-decoration:none;color:inherit}.chroma .lntd{vertical-align:top;padding:0;margin:0;border:0}.chroma .lntable{border-spacing:0;padding:0;margin:0;border:0}.chroma .hl{background-color:#e5e5e5}.chroma .lnt{white-space:pre;-webkit-user-select:none;user-select:none;margin-right:.4em;padding:0 .4em;color:#7f7f7f}.chroma .ln{white-space:pre;-webkit-user-select:none;user-select:none;margin-right:.4em;padding:0 .4em;color:#7f7f7f}.chroma .line{display:flex}.chroma .k{color:#000;font-weight:700}.chroma .kc{color:#000;font-weight:700}.chroma .kd{color:#000;font-weight:700}.chroma .kn{color:#000;font-weight:700}.chroma .kp{color:#000;font-weight:700}.chroma .kr{color:#000;font-weight:700}.chroma .kt{color:#458;font-weight:700}.chroma .na{color:teal}.chroma .nb{color:#0086b3}.chroma .bp{color:#999}.chroma .nc{color:#458;font-weight:700}.chroma .no{color:teal}.chroma .nd{color:#3c5d5d;font-weight:700}.chroma .ni{color:purple}.chroma .ne{color:#900;font-weight:700}.chroma .nf{color:#900;font-weight:700}.chroma .nl{color:#900;font-weight:700}.chroma .nn{color:#555}.chroma .nt{color:navy}.chroma .nv{color:teal}.chroma .vc{color:teal}.chroma .vg{color:teal}.chroma .vi{color:teal}.chroma .s{color:#d14}.chroma .sa{color:#d14}.chroma .sb{color:#d14}.chroma .sc{color:#d14}.chroma .dl{color:#d14}.chroma .sd{color:#d14}.chroma .s2{color:#d14}.chroma .se{color:#d14}.chroma .sh{color:#d14}.chroma .si{color:#d14}.chroma .sx{color:#d14}.chroma .sr{color:#009926}.chroma .s1{color:#d14}.chroma .ss{color:#990073}.chroma .m{color:#099}.chroma .mb{color:#099}.chroma .mf{color:#099}.chroma .mh{color:#099}.chroma .mi{color:#099}.chroma .il{color:#099}.chroma .mo{color:#099}.chroma .o{color:#000;font-weight:700}.chroma .ow{color:#000;font-weight:700}.chroma .c{color:#998;font-style:italic}.chroma .ch{color:#998;font-style:italic}.chroma .cm{color:#998;font-style:italic}.chroma .c1{color:#998;font-style:italic}.chroma .cs{color:#999;font-weight:700;font-style:italic}.chroma .cp{color:#999;font-weight:700;font-style:italic}.chroma .cpf{color:#999;font-weight:700;font-style:italic}.chroma .gd{color:#000;background-color:#fdd}.chroma .ge{color:#000;font-style:italic}.chroma .gr{color:#a00}.chroma .gh{color:#999}.chroma .gi{color:#000;background-color:#dfd}.chroma .go{color:#888}.chroma .gp{color:#555}.chroma .gs{font-weight:700}.chroma .gu{color:#aaa}.chroma .gt{color:#a00}.chroma .gl{text-decoration:underline}.chroma .w{color:#bbb}#home-main{display:flex;flex-direction:column;align-items:start;justify-content:space-between;height:100vh;max-width:720px;margin:auto;font-size:1.5rem}@media(max-width:768px){#home-main{margin-left:24px}}#home-center{display:flex;flex-direction:column;align-items:flex-start;margin-top:16vh}#home-nav{display:flex;flex-direction:column}#home-nav a{color:#252525;font-family:inter,sans-serif;font-size:40px;font-style:normal;font-weight:400;line-height:150%;text-decoration-line:underline}#posts-body{max-width:720px;margin:auto;display:flex;flex-direction:column;justify-content:start;height:100vh;margin-bottom:0}@media(max-width:768px){#posts-body{margin:0 24px}}#posts-list{display:flex;flex-direction:column}#posts-header{padding-top:10vh;font-size:20px;font-style:normal;font-weight:400}#posts-header a{text-decoration:none;color:#656565}#posts-header a:hover{text-decoration:underline;color:#151515}#post-header{padding-top:10vh}#post-header a{text-decoration:none;color:#656565}#post-header a:hover{text-decoration:underline;color:#151515}#post-title{font-size:2.5em;font-weight:400;margin-bottom:8px}.post-meta{font-size:1.5em}.post-meta span{color:#303030}.post-tags{margin:10px 0;display:flex;gap:6px}.post-tags .tag{font-size:.9em;padding:3px 14px;text-transform:lowercase;border:1px solid;margin-bottom:6px}.post-tags .tag a{outline:none;text-decoration:none;color:#5c5c5c;font-weight:500}.featured-image img{width:100%}#posts-footer{display:flex;flex-direction:column;flex-grow:1;justify-content:end}.post-item a{color:#252525;font-weight:400;line-height:150%;text-decoration-line:underline;font-size:2em}.post-content{font-size:1.3em;color:#202020;line-height:1.4}.post-content h2{border-bottom:1px solid rgba(71,61,139,.5)}.post-content p{text-align:justify}.post-content p a{text-decoration-line:none;text-decoration-style:solid;text-decoration-color:#483d8b;outline-color:#483d8b;color:#6a5acd}.post-content p img{width:100%}.post-to-top-link{text-decoration:none;color:#656565}.post-to-top-link:hover{text-decoration:underline;color:#151515}body{font-family:inter,sans-serif;line-height:1.4;background-color:#ebf4f3;margin:0}#header-title{color:#202020;font-family:inter,sans-serif;font-style:normal;font-weight:500;line-height:normal}.post-header{margin-bottom:40px}#site-footer{width:100%}#site-footer p{color:#5c5c5c;font-family:Inter;font-size:20px;font-style:normal;font-weight:300;line-height:normal;display:flex;gap:8px;justify-content:center}#site-footer a{color:#5c5c5c;font-family:Inter;font-size:20px;font-style:normal;font-weight:300;line-height:normal;display:flex;gap:8px;justify-content:center;text-decoration:none}#site-footer a:hover{text-decoration:underline}.pagination{display:flex;list-style:none;padding:0;margin:0;justify-content:center;align-items:center;font-family:Inter}.pagination a{text-decoration:none;color:#252525}.pagination .page-item{margin:0}.pagination .page-link{display:block;padding:5px 10px;margin:0 2px}#site-footer{width:100%;user-select:none}#site-footer #copyright{display:flex;align-items:center;justify-content:center}[aria-disabled=true]{text-decoration:none!important}.page-item.active a{text-decoration:none!important}blockquote{border-left:.25em solid;margin:1em;padding:0 1em;font-style:italic}blockquote cite{font-style:normal;display:flex;justify-content:end;gap:6px}blockquote cite::before{content:"—— "}
\ No newline at end of file
diff --git a/resources/_gen/assets/scss/scss/style.scss_871e1d33253f63f556fbcaa4227752be.json b/resources/_gen/assets/scss/scss/style.scss_871e1d33253f63f556fbcaa4227752be.json
index 4c9348f..7058a7a 100644
--- a/resources/_gen/assets/scss/scss/style.scss_871e1d33253f63f556fbcaa4227752be.json
+++ b/resources/_gen/assets/scss/scss/style.scss_871e1d33253f63f556fbcaa4227752be.json
@@ -1 +1 @@
-{"Target":"css/style.min.709a2ebf07dce3f8b5106058034b134c0f8e343dd9241f6182a31ba387131b72.css","MediaType":"text/css","Data":{"Integrity":"sha256-cJouvwfc4/i1EGBYA0sTTA+OND3ZJB9hgqMbo4cTG3I="}}
\ No newline at end of file
+{"Target":"css/style.min.3b8773726571fa9e7d673c971d249fad79d5c7713a58a0ebe2f97e03f3fac93c.css","MediaType":"text/css","Data":{"Integrity":"sha256-O4dzcmVx+p59ZzyXHSSfrXnVx3E6WKDr4vl+A/P6yTw="}}
\ No newline at end of file