Browse Source

Standardise on <figure>

master
Chris Smith 4 years ago
parent
commit
d564c38c23
Signed by: Chris Smith <chris@chameth.com> GPG Key ID: 3A2D4BBDC4A3C9A9

+ 1
- 0
.gitignore View File

1
 .DS_Store
1
 .DS_Store
2
+.idea
2
 
3
 
3
 # When running outside of docker, Hugo writes content here
4
 # When running outside of docker, Hugo writes content here
4
 /site/public
5
 /site/public

+ 4
- 3
site/content/post/2016-04-10-sense-api.md View File

10
 area: REST APIs
10
 area: REST APIs
11
 ---
11
 ---
12
 
12
 
13
-<div class="image right">
14
- <img src="/res/images/sense/sense.jpg" alt="Sense">
15
-</div>
13
+<figure class="right">
14
+  <img src="/res/images/sense/sense.jpg" alt="Sense">
15
+  <figcaption>A Sense unit and its two pillow sensors</figcaption>
16
+</figure>
16
 
17
 
17
 Sense is a little device that sits by your bedside and, in
18
 Sense is a little device that sits by your bedside and, in
18
 conjunction with a little 'pill' attached to your pillow, monitors your sleeping patterns and
19
 conjunction with a little 'pill' attached to your pillow, monitors your sleeping patterns and

+ 4
- 3
site/content/post/2016-05-02-monitoring-power-with-wemo.md View File

10
 area: data analysis
10
 area: data analysis
11
 ---
11
 ---
12
 
12
 
13
-<div class="image right">
14
- <img src="/res/images/wemo/switch.jpg" alt="WeMo Insight Switch">
15
-</div>
13
+<figure class="left">
14
+  <img src="/res/images/wemo/switch.jpg" alt="WeMo Insight Switch">
15
+  <figcaption>A WeMo Insight Switch</figcaption>
16
+</figure>
16
 
17
 
17
 I recently picked up a couple of <a href="http://www.belkin.com/uk/p/P-F7C029/">Belkin's WeMo
18
 I recently picked up a couple of <a href="http://www.belkin.com/uk/p/P-F7C029/">Belkin's WeMo
18
 Insight Switches</a> to monitor power usage for my PC and networking equipment. WeMo is Belkin's
19
 Insight Switches</a> to monitor power usage for my PC and networking equipment. WeMo is Belkin's

+ 4
- 3
site/content/post/2016-05-21-docker-automatic-nginx-proxy.md View File

10
 area: Docker
10
 area: Docker
11
 ---
11
 ---
12
 
12
 
13
-<div class="image left">
14
- <img src="/res/images/docker/logo.png" alt="Docker logo">
15
-</div>
13
+<figure class="right">
14
+  <img src="/res/images/docker/logo.png" alt="Docker logo">
15
+  <figcaption>The Docker project logo</figcaption>
16
+</figure>
16
 
17
 
17
 Over the past few weeks I've gradually been migrating services from running in LXC containers to
18
 Over the past few weeks I've gradually been migrating services from running in LXC containers to
18
 Docker containers. It takes a while to get into the right mindset for Docker - thinking of
19
 Docker containers. It takes a while to get into the right mindset for Docker - thinking of

+ 4
- 3
site/content/post/2016-06-17-why-you-should-be-using-https.md View File

9
 area: security
9
 area: security
10
 ---
10
 ---
11
 
11
 
12
-<div class="image right">
13
- <img src="/res/images/https/https-everywhere.jpg" alt="EFF HTTPS Everywhere logo">
14
-</div>
12
+<figure class="left">
13
+  <img src="/res/images/https/https-everywhere.jpg" alt="EFF HTTPS Everywhere logo">
14
+  <figcaption>The EFF's HTTPS Everywhere logo</figcaption>
15
+</figure>
15
 
16
 
16
 One of my favourite hobbyhorses recently has been the use of HTTPS, or lack thereof. HTTPS is the
17
 One of my favourite hobbyhorses recently has been the use of HTTPS, or lack thereof. HTTPS is the
17
 thing that makes the little padlock appear in your browser, and has existed for over 20 years.
18
 thing that makes the little padlock appear in your browser, and has existed for over 20 years.

+ 4
- 3
site/content/post/2016-08-11-offline-gnupg-master-yubikey-subkeys.md View File

9
 area: security
9
 area: security
10
 ---
10
 ---
11
 
11
 
12
-<div class="image left">
13
- <img src="/res/images/yubikey/keys.png" alt="Two yubikeys">
14
-</div>
12
+<figure class="right">
13
+  <img src="/res/images/yubikey/keys.png" alt="Two yubikeys">
14
+  <figcaption>A (key-)pair of Yubikeys. (Sorry.)</figcaption>
15
+</figure>
15
 
16
 
16
 I recently noticed that I'd accidentally lost my previous GPG private key &mdash; whoops. It was on
17
 I recently noticed that I'd accidentally lost my previous GPG private key &mdash; whoops. It was on
17
 a drive that I'd since formatted and used for a fair amount of time, so there's no hope of
18
 a drive that I'd since formatted and used for a fair amount of time, so there's no hope of

+ 5
- 3
site/content/post/2016-10-18-shoring-up-sshd.md View File

8
 description: Tools and suggestions for improving the security of SSHd by disabling weak algorithms and modern config tweaks.
8
 description: Tools and suggestions for improving the security of SSHd by disabling weak algorithms and modern config tweaks.
9
 area: security
9
 area: security
10
 ---
10
 ---
11
-<div class="image right">
12
- <img src="/res/images/ssh/openssh.png" alt="OpenSSH logo">
13
-</div>
11
+
12
+<figure class="left">
13
+  <img src="/res/images/ssh/openssh.png" alt="OpenSSH logo">
14
+  <figcaption>The OpenSSH project logo</figcaption>
15
+</figure>
14
 
16
 
15
 I recently came across a useful tool on GitHub called
17
 I recently came across a useful tool on GitHub called
16
 [ssh-audit](https://github.com/arthepsy/ssh-audit). It's a small Python script
18
 [ssh-audit](https://github.com/arthepsy/ssh-audit). It's a small Python script

+ 5
- 4
site/content/post/2017-12-17-dns-over-tls-on-edgerouter-lite.md View File

7
 area: security
7
 area: security
8
 ---
8
 ---
9
 
9
 
10
-<div class="image left">
11
- <img src="/res/images/erl/edgerouter.jpg" alt="EdgeRouter Lite">
12
-</div>
10
+<figure class="left">
11
+  <img src="/res/images/erl/edgerouter.jpg" alt="An EdgeRouter Lite">
12
+  <figcaption>The EdgeRouter Lite</figcaption>
13
+</figure>
13
 
14
 
14
 DNS-over-TLS is a fairly recent specificiation described in
15
 DNS-over-TLS is a fairly recent specificiation described in
15
 [RFC7858](https://tools.ietf.org/html/rfc7858), which enables DNS clients to
16
 [RFC7858](https://tools.ietf.org/html/rfc7858), which enables DNS clients to
167
 sudo tcpdump -Xi eth0 port 53
168
 sudo tcpdump -Xi eth0 port 53
168
 {{< / highlight >}}
169
 {{< / highlight >}}
169
 
170
 
170
-You should, hopefully, not see anything.
171
+You should, hopefully, not see anything.

+ 7
- 2
site/content/post/2019-04-01-understanding-docker-volume-mounts.md View File

7
 area: Docker
7
 area: Docker
8
 ---
8
 ---
9
 
9
 
10
+<figure class="left">
11
+  <img src="/res/images/docker/logo.png" alt="Docker logo">
12
+  <figcaption>The Docker project logo</figcaption>
13
+</figure>
14
+
10
 One thing that always confuses me with Docker is how exactly mounting
15
 One thing that always confuses me with Docker is how exactly mounting
11
 volumes behaves. At a basic level it's fairly straight forward: you
16
 volumes behaves. At a basic level it's fairly straight forward: you
12
 declare a volume in a Dockerfile, and then either explicitly mount
17
 declare a volume in a Dockerfile, and then either explicitly mount
13
 something there or docker automatically creates an anonymous volume
18
 something there or docker automatically creates an anonymous volume
14
 for you. Done. But it turns out there's quite a few edge cases...
19
 for you. Done. But it turns out there's quite a few edge cases...
15
 
20
 
16
-<!--more-->
17
-
18
 ### Changing ownership of the folder
21
 ### Changing ownership of the folder
19
 
22
 
20
 Perhaps the most common operation done on a Docker volume other than
23
 Perhaps the most common operation done on a Docker volume other than
22
 If your Docker process runs as a certain user you probably want the
25
 If your Docker process runs as a certain user you probably want the
23
 directory to be writable by that user.
26
 directory to be writable by that user.
24
 
27
 
28
+<!--more-->
29
+
25
 At first we might try something like:
30
 At first we might try something like:
26
 
31
 
27
 {{< highlight docker >}}
32
 {{< highlight docker >}}

Loading…
Cancel
Save