notplants
/
garden.canalswans.net
0
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

clarity

This commit is contained in:
notplants 2022-07-26 12:35:24 +02:00
parent 5c5946b213
commit 52f7d133ad
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
static/content/wiki/cms-and-static-site-generators.md
View File

@ -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.
and am hopeful that this will mean reproducible builds in the future, and no unexpected breakages unless I choose to make a change.