Fixed typos. Improved optics.

Author: redcatbear

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "themes/hugo-flex"]
+	path = themes/hugo-flex
+	url = https://github.com/ldeso/hugo-flex.git

config.yml

@@ -1,5 +1,10 @@
 baseURL: 'http://blog.itsallcode.org/'
-languageCode: 'en-US'
+languageCode: 'en-us'
 defaultContentLanguage: 'en'
-title: 'Itsallcode Blog — Home of the everything-is-code enthusiasts'
-theme: 'github.com/nodejh/hugo-theme-mini'
+title: 'Itsallcode Blog'
+theme: 'github.com/nodejh/hugo-theme-mini'
+
+params:
+  description: 'Home of the everything-is-code enthusiasts'
+  showToc: true
+  showPowerBy: false

content/2018/07/03/oft-specfications-as-pdf.md

@@ -1,5 +1,5 @@
 ---
-title: "Oft Specfications as Pdf"
+title: "OFT Specifications as PDF"
 date: 2018-07-03T19:46:42+02:00
 draft: false
 params:
@@ -8,6 +8,8 @@ params:
 
 [PDFs](https://www.techterms.com/definition/pdf) are a fixed-size document format, which means that they made more sense in the days when PCs all had about the same video resolutions and screen geometries. But even then, they were never perfect for displaying them on a screen because most are in portrait mode and monitors rarely were. Nowadays, displays especially in mobile devices come in all shapes and sizes, so fixed-size formats are even more obsolete.
 
+<!--more-->
+
 What PDFs excel at to the present day is a universal document exchange format for read-only documents — especially if you plan on printing them.
 
 While specifications seldom get printed these days, they still tend to get archived — especially [PDF-A](https://en.wikipedia.org/wiki/PDF/A) — and a universally accepted format helps. That being said, we plan to make converting [OFT-native](https://medium.com/@williamwilling/oft-planning-made-leaner-5fc52e2e77f9) (aka. "requirement-enhanced Markdown") easy.

content/2018/07/06/named-vs-numeric-requirement-ids.md

@@ -1,12 +1,13 @@
 ---
-title: "Named vs. Numeric Requirement Ids"
+title: "Named vs. Numeric Requirement IDs"
 date: 2018-07-06T20:02:12+02:00
 draft: false
 params:
     author: Sebastian
 ---
 
 With every new project there will be a discussion whether requirement IDs should have a unique name or simply a numbering scheme.
+<!--more-->
 
 If you look at [OFT](https://github.com/itsallcode/openfasttrace)‘s [specification document](https://github.com/itsallcode/openfasttrace/blob/develop/doc/system_requirements.md), you will see that we chose named IDs. The reason in our case is quite simple: we use the ID as reference in OFT’s native specification format (aka. “requirement-enhanced Markdown”) and it is a lot simpler to understand the connections between the specification items in different artifact types if you can tell by the name what the requirement ID is about. It also helps debugging.
 

content/2018/07/14/openfasttrace-1-1-0-released.md

@@ -1,5 +1,5 @@
 ---
-title: "Openfasttrace 1 1 0 Released"
+title: "Openfasttrace 1.1.0 Released"
 date: 2018-07-14T20:17:27+02:00
 draft: false
 params:

content/2018/10/30/on-refactoring-an-hidden-technical-dept.md

@@ -8,6 +8,8 @@ params:
 
 Can you accumulate technical dept, even if you regularly clean up your sources meticulously? A short while ago I would have said that this is possible but unlikely. That was before I started taking on the migration of all of [OpenFastTrace](https://github.com/itsallcode/openfasttrace)‘s unit tests from [JUnit4](https://junit.org/junit4/) to [JUnit5](https://junit.org/junit5/).
 
+<!--more-->
+
 Like most non-trivial projects OFT accumulated quite a number of unit tests over the years and although it was always the plan to move to JUnit5 some day, they were all written for JUnit4. With the arrival of [OFT 2.0.0](https://github.com/itsallcode/openfasttrace/releases/tag/2.0.0) — which also was a major refactoring endeavor — I felt now would be the perfect time to make that migration happen. After all I was in the refactoring flow.
 
 ## To rule them all…

content/2018/11/24/gradle-plugin-upgraded-to-openfasttrace-2-1-0.md

@@ -1,5 +1,5 @@
 ---
-title: "Gradle Plugin Upgraded to Openfasttrace 2 1 0"
+title: "Gradle Plugin Upgraded to Openfasttrace 2.1.0"
 date: 2018-11-24T20:33:37+02:00
 draft: false
 params:

content/2018/11/25/recovering-jpgs-from-a-broken-file-system-on-a-flash-disk.md

@@ -1,5 +1,5 @@
 ---
-title: "Recovering Jpgs From a Broken File System on a Flash Disk"
+title: "Recovering JPGs From a Broken File System on a Flash Disk"
 date: 2018-11-25T20:36:13+02:00
 draft: false
 params:

content/2018/12/15/maven-plugin-for-oft-created.md

@@ -1,5 +1,5 @@
 ---
-title: "Maven Plugin for Oft Created"
+title: "Maven Plugin for OFT Created"
 date: 2018-12-15T20:44:05+02:00
 draft: false
 params:
@@ -8,4 +8,6 @@ params:
 
 Today we started a new project for creating a [Maven plugin for OpenFastTrace](https://github.com/itsallcode/openfasttrace-maven-plugin). This will allow you to trace requirements not only with the command line and Gradle but also with Maven!
 
-The project is still in its early stage but you can already trace requirements with the default configuration and a first integration test is working. See [Pull Request #1](https://github.com/itsallcode/openfasttrace-maven-plugin/pull/1) for the current sources. Reviews are welcome!
+<!--more-->
+
+The project is still in its early stage, but you can already trace requirements with the default configuration and a first integration test is working. See [Pull Request #1](https://github.com/itsallcode/openfasttrace-maven-plugin/pull/1) for the current sources. Reviews are welcome!

content/2019/03/09/time-recording-tool.md

@@ -6,7 +6,9 @@ params:
     author: Christoph 
 ---
 
-To keep track of my working time I wrote a small time recording tool called White Rabbit. You can find it at [https://github.com/itsallcode/white-rabbit](https://github.com/itsallcode/white-rabbit).
+To keep track of my working time I wrote a little time recording tool called White Rabbit. You can find it at [https://github.com/itsallcode/white-rabbit](https://github.com/itsallcode/white-rabbit).
+
+<!--more-->
 
 # Features
 
@@ -16,7 +18,7 @@ To keep track of my working time I wrote a small time recording tool called Whit
 - Manual interruptions: press `i` to start and stop interruptions
 - Supports weekend, public holiday, vacation, flex time and sickness (see json example)
 - Reporting of total overtime: press `r`
-- Automatic update in the background (press `u` to update manually): just keep it running and it will record your working time
+- Automatic update in the background (press `u` to update manually): just keep it running, and it will record your working time
     - Start of work is detected via
         - Program start
         - Computer resumes from sleep in the morning
@@ -28,11 +30,11 @@ To keep track of my working time I wrote a small time recording tool called Whit
     - Working time of 8h Monday to Friday
     - Mandatory break of 45 minutes after 6 hours of working
 
-# Architectural descisions
+# Architectural Descsions
 
-The architecture separates business logic (sub-project logic) from the user interface (textui). This allows you to add additional user interfaces e.g. using JavaFX or Swing.
+The architecture separates business logic (sub-project logic) from the user interface (`textui`). This allows you to add additional user interfaces e.g. using JavaFX or Swing.
 
-We use JSON for storage because this enables the user to manually make changes (e.g. add a sick day).  So we can keep the user interface as simple as possible.
+We use JSON for storage because this enables the user to manually make changes (e.g. add a sick day). So we can keep the user interface as simple as possible.
 
 # Example data file
 

content/2020/05/24/new-gradle-plugin-for-oft.md

@@ -1,5 +1,5 @@
 ---
-title: "New Gradle Plugin for Oft"
+title: "New Gradle Plugin for OFT"
 date: 2020-05-24T20:56:01+02:00
 draft: false
 params:

content/2020/11/08/initial-public-release-of-whiterabbit-time-recording.md

@@ -8,8 +8,10 @@ params:
 
 Need a tool for tracking your working time? Try [WhiteRabbit](https://github.com/itsallcode/white-rabbit)!
 
-We just release version 1.0.0 on [GitHub.](https://github.com/itsallcode/white-rabbit)
+We just released version 1.0.0 on [GitHub.](https://github.com/itsallcode/white-rabbit)
 
-![Screenshot of the WhiteRabbit UI](screenshot-white-rabbit-1.0.0.png)
+![Screenshot of the WhiteRabbit UI](/images/white-rabbit/screenshot-white-rabbit-1.0.0.png)
+
+<!--more-->
 
 You can start it via WebStart (see [https://whiterabbit.chp1.net/](https://whiterabbit.chp1.net/)) or download it from [https://github.com/itsallcode/white-rabbit/releases/tag/v1.0.0](https://github.com/itsallcode/white-rabbit/releases/tag/v1.0.0).