wip adding articles

config.yaml

@@ -6,6 +6,11 @@ params:
   mainSections:
     - nixos
 
+markup:
+  goldmark:
+    renderer:
+      unsafe: true
+
 menu:
   main:
     - name: "main"

content/nixos/tinc.md

@@ -36,7 +36,7 @@ This should make it easy to define all your networks
 in one file (to keep track about everything),
 and micromanage in the computer specific definitions.
 
-# How to import
+## How to import
 
 You can use `fetchgit` to import it without downloading it yourself.
 
@@ -62,9 +62,9 @@ in {
 
 Now you are ready to go!
 
-# Create Keys
+## Create Keys
 
-First of all,
+First,
 we have to create tinc keys for every computer in the VPN Mesh.
 To put the keys in the current folder we use the `'--config .'` option,
 
@@ -78,7 +78,7 @@ After that is done we create the `hostfile` by
 $> cat *.pub > hostfile ; rm *.pub
 ```
 
-## Key-File-structure for these Examples
+### Key-File-structure for these Examples
 
 In the following examples I expect the following file-structure for keys and config files.
 
@@ -103,10 +103,10 @@ In the following examples I expect the following file-structure for keys and con
 ```
 
 
-# Connect 3 computers
+## Connect 3 computers
 
 We want to connect 3 computers in a private network of range ``10.1.1.0/24``.
-One computer needs to be accessable from the internet,
+One computer needs to be accessible from the internet,
 it will be the computer that connects all the other computer.
 You can have multiple computers which are reachable from the internet
 but for this example we only have one.
@@ -230,10 +230,10 @@ PING HAL.private (10.1.1.3) 56(84) bytes of data.
 **Awesome!** That was easy!
 
 
-# Connect 2 sub-networks
+## Connect 2 sub-networks
 
 So far so good,
-but lets imagine we have some virtual machines running on 2 computers and want to make these virtual machines see each other.
+but let's imagine we have some virtual machines running on 2 computers and want to make these virtual machines see each other.
 This is a very common problem in [Kubernetes](https://kubernetes.io/).
 It can be resolved by using the `tincSubnet` parameter,
 to configure sub-network routing.
@@ -243,7 +243,7 @@ to configure sub-network routing.
 Achieving this is very simple,
 just add the `tincSubnet` parameter in the `hosts` attribute and your done.
 
-```nix
+```
 ...
 
 default =
@@ -282,7 +282,7 @@ default =
 ...
 ```
 
-After deployment we can see that `Gibson` has proper routing to the configured `tincSubnet`
+After deployment, we can see that `Gibson` has proper routing to the configured `tincSubnet`
 ranges as well as to `10.1.1.0/24` to reach the other network-nodes.
 
 ```

layouts/shortcodes/note.html

@@ -1,4 +1,3 @@
-
 <div class="note">
 {{ .Inner }}
 </div>

src/lessc/page/main.less

@@ -203,7 +203,7 @@ p {
   .block-margin();
 }
 
-.panel {
+.note {
   background: @color-note-background;
   border-left: .4em solid @color-note-border;