[hooks] Added a hook that groups contents header and list, and added custom styling for it to float right

13 files changed, 51 insertions, 51 deletions

diff --git a/src/tutorials/connect-to-mysql-in-dotnet-ef/index.md b/src/tutorials/connect-to-mysql-in-dotnet-ef/index.md
index b1e6bca..d6bde42 100644
--- a/src/tutorials/connect-to-mysql-in-dotnet-ef/index.md
+++ b/src/tutorials/connect-to-mysql-in-dotnet-ef/index.md
@@ -1,9 +1,5 @@
 # Connect to MySql in .NET and Entity Framework 
 
-I have found that connecting a `.NET` application to a `MySql` database (with Entity Framework) can be tricky. Here is what works for me.
-
-Also, [MySql.Data.EntityFrameworkCore](https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/) has been **depricated** since *October 2020*. If you need setup instructions with it, read [this](https://gitlab.com/Syndamia/syndamiadotcom/-/blob/0510e29526c6d7681587fff4c98a339e8c69e9b5/src/tutorials/connect-to-mysql-in-csharp-ef/article.md).
-
 ## Contents
 
 1. [NuGet packages](#nuget-packages) 
@@ -12,6 +8,10 @@ Also, [MySql.Data.EntityFrameworkCore](https://www.nuget.org/packages/MySql.Data
    1. [ASP.NET Startup](#asp.net-startup)
    2. [DBContext child class](#dbcontext-child-class)
 
+I have found that connecting a `.NET` application to a `MySql` database (with Entity Framework) can be tricky. Here is what works for me.
+
+Also, [MySql.Data.EntityFrameworkCore](https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/) has been **depricated** since *October 2020*. If you need setup instructions with it, read [this](https://gitlab.com/Syndamia/syndamiadotcom/-/blob/0510e29526c6d7681587fff4c98a339e8c69e9b5/src/tutorials/connect-to-mysql-in-csharp-ef/article.md).
+
 ## NuGet packages
 
 You'll need to install [Pomelo.EntityFrameworkCore.MySql](https://www.nuget.org/packages/Pomelo.EntityFrameworkCore.MySql/). It provides the stuff necessary for connecting and using a `MySql` database.
diff --git a/src/tutorials/export-skype/index.md b/src/tutorials/export-skype/index.md
index 11b3b19..1957a9c 100644
--- a/src/tutorials/export-skype/index.md
+++ b/src/tutorials/export-skype/index.md
@@ -1,13 +1,13 @@
 # How to export Skype data
 
-Skype has always allowed to export your chat history (and files), but it's not as straight forward as it should. Continue reading for the required steps on doing it.
-
 ## Contents
 
 1. [Downloading files](#downloading-files) 
 2. [Viewing your export - Official Tool](#viewing-your-export---official-tool)
 3. [Viewing your export - ArtemVeremienko Fork](#viewing-your-export---artemveremienko-fork)
 
+Skype has always allowed to export your chat history (and files), but it's not as straight forward as it should. Continue reading for the required steps on doing it.
+
 ## Downloading files
 
 1. Open [secure.skype.com/en/data-export](https://secure.skype.com/en/data-export)
diff --git a/src/tutorials/how-to-encrypt-email/index.md b/src/tutorials/how-to-encrypt-email/index.md
index 3eae26d..9d95b45 100644
--- a/src/tutorials/how-to-encrypt-email/index.md
+++ b/src/tutorials/how-to-encrypt-email/index.md
@@ -1,9 +1,5 @@
 # How to encrypt email
 
-In [this](/blog/encrypted-email) blog post I shared the most common technologies for email encryption and a bit of how they work. PGP and S/MIME are the most popular schemes, with support from a lot of clients.
-
-These are all the steps required to go from having no encryption, to encrypting all of your future emails.
-
 ## Contents
 
 1. [Getting keys](#getting-keys)
@@ -14,6 +10,10 @@ These are all the steps required to go from having no encryption, to encrypting
 2. [Exchanging keys](#exchanging-keys)
 3. [Configuring clients](#configuring-clients)
 
+In [this](/blog/encrypted-email) blog post I shared the most common technologies for email encryption and a bit of how they work. PGP and S/MIME are the most popular schemes, with support from a lot of clients.
+
+These are all the steps required to go from having no encryption, to encrypting all of your future emails.
+
 ## Getting keys
 
 PGP and S/MIME are both built upon [public-key cryptography](https://en.wikipedia.org/wiki/Public-key_cryptography) so you and all of your recipients need to have a pair of public and private keys.
diff --git a/src/tutorials/how-to-use-jira/cards.md b/src/tutorials/how-to-use-jira/cards.md
index 064a578..77d27a9 100644
--- a/src/tutorials/how-to-use-jira/cards.md
+++ b/src/tutorials/how-to-use-jira/cards.md
@@ -4,10 +4,6 @@
 
 <br>
 
-**Each issue is represented as an object with properties**. More specifically, these objects are called 'cards'.
-
-![](./img/kanban-cards.png)
-
 ## Contents
 
 1. [Properties](#properties)
@@ -19,6 +15,10 @@
    3. [Issue flagging](#issue-flagging)
    4. [Basic issue information](#basic-issue-information)
 
+**Each issue is represented as an object with properties**. More specifically, these objects are called 'cards'.
+
+![](./img/kanban-cards.png)
+
 ## Properties
 
 Each card has the following properties:
diff --git a/src/tutorials/how-to-use-jira/components.md b/src/tutorials/how-to-use-jira/components.md
index 9faf24c..4f22a31 100644
--- a/src/tutorials/how-to-use-jira/components.md
+++ b/src/tutorials/how-to-use-jira/components.md
@@ -4,13 +4,13 @@
 
 <br>
 
-Components are **yet another way to group issues together**. They don't have any specific meaning like versions, their usage depends on the project's organisation.
-
 ## Contents
 
 1. [Creating and editing](#creating-and-editing)
 2. [Adding issues](#adding-issues)
 
+Components are **yet another way to group issues together**. They don't have any specific meaning like versions, their usage depends on the project's organisation.
+
 ## Creating and editing
 
 Creating and editing them is done from the **`Components` menu in the sidebar**.
diff --git a/src/tutorials/how-to-use-jira/dashboards.md b/src/tutorials/how-to-use-jira/dashboards.md
index 2c65066..6b3185f 100644
--- a/src/tutorials/how-to-use-jira/dashboards.md
+++ b/src/tutorials/how-to-use-jira/dashboards.md
@@ -4,6 +4,11 @@
 
 <br>
 
+## Contents
+
+1. [Adding a dashboard](#adding-a-dashboard)
+2. [Adding gadgets](#adding-gadgets)
+
 Dashboards are a **place where you can view a lot of information**.
 
 ![](./img/default-dashboard.png)
@@ -14,11 +19,6 @@ Dashboards are composed of **gadgets**.
 
 Gadgets have functionality for **displaying certain information**, like `Average Age Chart` or `Issues in progress`. Each gadget can be setup to **take information from one or more projects and/or saved filters**.
 
-## Contents
-
-1. [Adding a dashboard](#adding-a-dashboard)
-2. [Adding gadgets](#adding-gadgets)
-
 ## Adding a dashboard
 
 Dashboard can be added from the top bar, under `Create dashboard` in the `Dashboards` menu
diff --git a/src/tutorials/how-to-use-jira/filters.md b/src/tutorials/how-to-use-jira/filters.md
index d6d2e03..97ec938 100644
--- a/src/tutorials/how-to-use-jira/filters.md
+++ b/src/tutorials/how-to-use-jira/filters.md
@@ -4,17 +4,17 @@
 
 <br>
 
+## Contents
+
+1. [Criteria](#Criteria)
+2. [JQL](#JQL)
+
 **Filters work like an advanced issue search that you can save**. With filters you filter issues from chosen project(s) by their properties (status, type, start date, etc.).
 
 Making filters is done through the `Advanced issue search` page, from the `Filters` menu.
 
 ![](./img/filters-advanced-issue-search.png)
 
-## Contents
-
-1. [Criteria](#Criteria)
-2. [JQL](#JQL)
-
 ## Criteria
 
 From here you can see some criteria: `Project`, `Type`, `Status`, `Assignee`.
diff --git a/src/tutorials/how-to-use-jira/index.md b/src/tutorials/how-to-use-jira/index.md
index 6ce830d..42a3364 100644
--- a/src/tutorials/how-to-use-jira/index.md
+++ b/src/tutorials/how-to-use-jira/index.md
@@ -4,12 +4,6 @@
 
 <br>
 
-[Jira](https://www.atlassian.com/software/jira) is one of the most used project management and issue tracking products out there.
-
-It has a lot of features that can be quite overwhelming for new comers, especially these who are new to project management software. That's why I'm writing this tutorial.
-
-**Note**: certain actions can be done only from a project administrator
-
 ## Contents
 
 1. [Filters](./filters.html)
@@ -47,3 +41,10 @@ It has a lot of features that can be quite overwhelming for new comers, especial
 10. [Dashboards](./dashboards.html)
     1. [Adding a dashboard](./dashboards.html#adding-a-dashboard)
     2. [Adding gadgets](./dashboards.html#adding-gadgets)
+
+[Jira](https://www.atlassian.com/software/jira) is one of the most used project management and issue tracking products out there.
+
+It has a lot of features that can be quite overwhelming for new comers, especially these who are new to project management software. That's why I'm writing this tutorial.
+
+**Note**: certain actions can be done only from a project administrator
+
diff --git a/src/tutorials/how-to-use-jira/kanban.md b/src/tutorials/how-to-use-jira/kanban.md
index 7fd6388..4818f5c 100644
--- a/src/tutorials/how-to-use-jira/kanban.md
+++ b/src/tutorials/how-to-use-jira/kanban.md
@@ -4,17 +4,17 @@
 
 <br>
 
+## Contents
+
+1. [Create board](#create-board)
+2. [Backlog](#backlog)
+
 Kanban is a **way for visually organising work items** (issues in our case). Kanban consists of **columns** and **cards**, where cards are the work items and are **moved from one column to another** depending on the situation. This should sound **familiar**, because that is how [Boards](./projects.md) work.
 
 In a projects that uses the kanban template, boards can access directly all of the available issues.
 
 This tutorial focuses on the basics, but you can find a lot of information in [these sets of articles](https://www.atlassian.com/agile/kanban) from Atlassian.
 
-## Contents
-
-1. [Create board](#create-board)
-2. [Backlog](#backlog)
-
 ## Create board
 
 This template can be chosen when **creating a project**
diff --git a/src/tutorials/how-to-use-jira/projects.md b/src/tutorials/how-to-use-jira/projects.md
index 0707902..cfe2e0e 100644
--- a/src/tutorials/how-to-use-jira/projects.md
+++ b/src/tutorials/how-to-use-jira/projects.md
@@ -4,10 +4,6 @@
 
 <br>
 
-![](./img/projects.png)
-
-In short, **projects are a collection of issues** with added functionality for **organising them, getting statistics, etc**.
-
 ## Contents
 
 1. [Creating a project](#creating-a-project)
@@ -17,6 +13,10 @@ In short, **projects are a collection of issues** with added functionality for *
 3. [Backlog](#backlog)
 4. [Add item](#add-item)
 
+In short, **projects are a collection of issues** with added functionality for **organising them, getting statistics, etc**.
+
+![](./img/projects.png)
+
 ## Creating a project
 
 To create a project, either **click on `Create project` from the menu `Projects` in the top bar**,
diff --git a/src/tutorials/how-to-use-jira/scrum.md b/src/tutorials/how-to-use-jira/scrum.md
index 9e6ab77..d4e9255 100644
--- a/src/tutorials/how-to-use-jira/scrum.md
+++ b/src/tutorials/how-to-use-jira/scrum.md
@@ -4,6 +4,12 @@
 
 <br>
 
+## Contents
+
+1. [Backlog](#backlog)
+2. [Boards and Issues](#boards-and-issues)
+3. [Create board](#create-board)
+
 The scrum template is very similar to the kanban template, with one big difference: **sprints**.
 
 **All issues** are put into the **backlog** (which is now a **separate page**). From there, they are organised into **sprints**. 
@@ -12,12 +18,6 @@ In general [agile software development](https://www.atlassian.com/agile), a **sp
 
 Your **boards only work on the issues of the currently active sprint**.
 
-## Contents
-
-1. [Backlog](#backlog)
-2. [Boards and Issues](#boards-and-issues)
-3. [Create board](#create-board)
-
 ## Backlog
 
 As we've discussed, the **backlog** is used for organising **all issues** into **sprints**.
diff --git a/src/tutorials/install-plan9-with-virt-manager/index.md b/src/tutorials/install-plan9-with-virt-manager/index.md
index 67b7b76..b81594c 100644
--- a/src/tutorials/install-plan9-with-virt-manager/index.md
+++ b/src/tutorials/install-plan9-with-virt-manager/index.md
@@ -1,12 +1,12 @@
 # Install Plan 9 with virt-manager
 
-Installing [Plan 9 by Bell Labs](https://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs) with `qemu` itself isn't difficult and there are [official instructions](https://9p.io/wiki/plan9/Installing_Plan_9_on_Qemu/). However, when using `virt-manager`, there are certain uncertainties that might worry a first-timer and certain issues that arise.
-
 ## Contents
 
 1. [Creating the virtual machine](#creating-the-virtual-machine)
 2. [Installing Plan 9 itself](#installing-plan-9-itself)
 
+Installing [Plan 9 by Bell Labs](https://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs) with `qemu` itself isn't difficult and there are [official instructions](https://9p.io/wiki/plan9/Installing_Plan_9_on_Qemu/). However, when using `virt-manager`, there are certain uncertainties that might worry a first-timer and certain issues that arise.
+
 ## Creating the virtual machine
 
 We'll be installing Plan 9 with a CD (ISO) image. You can download the latest version (compiled every night) from [here](https://9p.io/plan9/download.html). For a compressed version and checksums, refer to [this page](https://9p.io/wiki/plan9/Download/index.html).
diff --git a/src/tutorials/windows-run-dialog/index.md b/src/tutorials/windows-run-dialog/index.md
index 2f3a7f4..48eba00 100644
--- a/src/tutorials/windows-run-dialog/index.md
+++ b/src/tutorials/windows-run-dialog/index.md
@@ -1,7 +1,5 @@
 # Windows Run dialog
 
-On Windows, most often you run an application by finding and double-clicking it's `.exe` file. What a lot of people don't realise is that you can launch any application or open any file you want by typing a single command. That can be achieved inside the **Run dialog**.
-
 ## Contents
 
 1. [Opening the Run dialog](#opening-the-run-dialog)
@@ -11,6 +9,7 @@ On Windows, most often you run an application by finding and double-clicking it'
    3. [Windows settings](#windows-settings)
 3. [For more](#for-more)
 
+On Windows, most often you run an application by finding and double-clicking it's `.exe` file. What a lot of people don't realise is that you can launch any application or open any file you want by typing a single command. That can be achieved inside the **Run dialog**.
 
 ## Opening the Run dialog