From 52f7d133ad67d4b9c9c3bb7d8901d97a7da96438 Mon Sep 17 00:00:00 2001 From: notplants Date: Tue, 26 Jul 2022 12:35:24 +0200 Subject: [PATCH] clarity --- static/content/wiki/cms-and-static-site-generators.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/static/content/wiki/cms-and-static-site-generators.md b/static/content/wiki/cms-and-static-site-generators.md index b9f8a45..b8d286b 100644 --- a/static/content/wiki/cms-and-static-site-generators.md +++ b/static/content/wiki/cms-and-static-site-generators.md @@ -31,9 +31,9 @@ as much as people hate on wordpress, there's perhaps a lot to love. all that said, wordpress is really complicated, and while lichen is beautiful and simple and good for many things, there are some limitations to what you can do with it. I also appreciate that gatsby is flexible, and once set-up, its worked pretty smoothly. my biggest annoyance with gatsby, -is that after a couple years, when I updated node, the build for my site broke, even though I hadn't made any changes to the site. +is that after a couple years, when I updated node for another project, the build for my site broke, even though I hadn't made any changes to the site. I found this very frustrating when I just wanted to make a small change to the site, and not to wrestle with webpack. I seem to have fixed this problem by switching to using [nvm](https://github.com/nvm-sh/nvm) to only use a specific version of node for building my gatsby site, and recording in my readme.md which version of node I use to build the site. Now I run "nvm use 14" before I ever build the site, -and am hopeful that this will mean no unexpected breaking of the build in the future, unless I choose to make a change. \ No newline at end of file +and am hopeful that this will mean reproducible builds in the future, and no unexpected breakages unless I choose to make a change. \ No newline at end of file