pyratelog

personal blog
git clone git://git.pyratebeard.net/pyratelog.git
Log | Files | Refs | README

commit 78a0ef1c5decbceac73c2d73d4365e8b3f71c24d
parent a33a87d840f5d0f1caf19b9c7a87b5ce44837858
Author: pyratebeard <root@pyratebeard.net>
Date:   Tue, 18 Oct 2022 22:39:44 +0100

as_a_matter_of_course

Diffstat:
Mentry/as_a_matter_of_course.md | 9+++++++--
1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/entry/as_a_matter_of_course.md b/entry/as_a_matter_of_course.md @@ -1,3 +1,8 @@ -This web log as been through a number of iterations. First it was TK, then I switched to Jekyll/Hugo using Github pages, then a docker container using Gitlab's CI/CD pipeline, and finally the current setup. +This web log as been through a number of iterations. First I used Jekyll on Github Pages, then I switched to Hugo using a docker container and Gitlab's CI/CD pipeline, and finally the current setup. -I moved away from the docker container as the build started failing and I hit too many issues trying to get it working. In an effort to simplify everything I thought, why couldn't I write my posts in markdown then use [pandoc](TK){target="_blank" rel="noreferrer"} to convert them to HTML. Sounds so easy, and it is in essence, but I have built up around it to try and smooth the whole process. +I moved away from the docker container as the build started failing and I hit too many issues trying to get it working. In an effort to simplify everything I thought why couldn't I write my posts in markdown then use [pandoc](https://pandoc.org/){target="_blank" rel="noreferrer"} to convert them to HTML. +``` +pandoc -f markdown -t html -o new_post.html new_post.md +``` + +Sounds so easy, and it is in essence. That command is the basis for how my blog works.