From d4965480747285fc9c6d2b2f35de109863ece52d Mon Sep 17 00:00:00 2001 From: "leoadec@gmail.com" Date: Fri, 2 Aug 2024 00:40:48 +1000 Subject: [PATCH] draft text --- .gitignore | 1 + ...ating-my-github-pages-website-to-node-js.md | 18 ++++++++++++++++++ 2 files changed, 19 insertions(+) create mode 100644 _drafts/migrating-my-github-pages-website-to-node-js.md diff --git a/.gitignore b/.gitignore index 6b5810d..1b6eaf9 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,4 @@ +*.swp .jekyll-cache/ _site/ node_modules/ diff --git a/_drafts/migrating-my-github-pages-website-to-node-js.md b/_drafts/migrating-my-github-pages-website-to-node-js.md new file mode 100644 index 0000000..d177220 --- /dev/null +++ b/_drafts/migrating-my-github-pages-website-to-node-js.md @@ -0,0 +1,18 @@ +--- +--- +As many other people, I have been using GitHub Pages to host my personal +website: it is free, comes with unlimited CI/CD, and is quite straightforward. + +It is also powered behind the scenes by Jekyll, a static site generator built in +Ruby, which is a language I don't have that much familiarity with, and whose +adoption has been dwindling over the years. I had some aspirations to make the +website more complex, and for these I would probably need tools outside the Ruby +sphere, tools likely built with Node.js. In which case, why not build the +website in Node.js itself? + +## Preparations + +The first thing to notice is that you can customize the CI/CD for GitHub pages +deployment. In that way, if you have a `"script"` field specified in your +`packages.json`, you can add the commands there that test and build your +website.