From 3aaa969c4e7741be9b1669fd8d46426303933f2b Mon Sep 17 00:00:00 2001 From: shr4pnel Date: Mon, 8 Apr 2024 00:43:26 +0100 Subject: [PATCH] =?UTF-8?q?Update=20shr4pnelblog=20=E2=80=9C2024-04-07-int?= =?UTF-8?q?egrating-jekyll-with-decap-cms=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- _posts/2024-04-07-integrating-jekyll-with-decap-cms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-04-07-integrating-jekyll-with-decap-cms.md b/_posts/2024-04-07-integrating-jekyll-with-decap-cms.md index d026317..bfcf27d 100644 --- a/_posts/2024-04-07-integrating-jekyll-with-decap-cms.md +++ b/_posts/2024-04-07-integrating-jekyll-with-decap-cms.md @@ -6,7 +6,7 @@ permalink: jekyll --- ## Introduction -Yesterday, I rewrote my blog to use [Jekyll](https://jekyllrb.com/). I was previously using a backwards stupid method to fetch new posts on each page load from the server filesystem. If this content changed often it may have been a viable strategy but the posts are static and logically should be in the filesystem +Yesterday, I rewrote my blog to use [Jekyll](https://jekyllrb.com/). I was previously using a backwards stupid method to fetch new posts on each page load from the server filesystem. If this content changed often it may have been a viable strategy but the posts are static and logically should be in the index itself. ## Jekyll