From 02f4c6c68cd091974a6c758a0b13ae8473b0bf1f Mon Sep 17 00:00:00 2001 From: unknown Date: Mon, 6 Feb 2023 14:02:18 +0000 Subject: [PATCH] CI/CD Commit: 2023-02-06T14:02:18+00:00 --- content/posts/drone-and-hugo/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/posts/drone-and-hugo/index.md b/content/posts/drone-and-hugo/index.md index c401485..0fd8735 100644 --- a/content/posts/drone-and-hugo/index.md +++ b/content/posts/drone-and-hugo/index.md @@ -175,6 +175,9 @@ The steps are pretty simple ## Green checkmarks At this point, I've got a fully automated publishing pipeline. As soon as a commit gets pushed to my blog repository, Drone jumps into action and runs a fresh Hugo build. The process is far from perfect, though. +![[Resources/attachments/obsidian-pipeline-screenshot.png]] +[[Resources/attachments/obsidian-pipeline-screenshot.png]] + You might've noticed a lack of screenshots or other media in my posts. At the moment, I'm authoring my blog posts in [Obsidian](https://obsidian.md), my preferred note-taking application, because it gives me quick access to...well, my notes. The catch is that Obsidian and Hugo use different conventions for linking between documents and referencing attachments/images. In the long term, what I want to do is probably write a script and pipeline which can