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

CMS & ssg

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

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

@ -10,6 +10,30 @@ description: ""
note: "Max Fowler"
---
lichen
the two cms and static site-generators I'm most interested in are:
gatsby-mdx
[lichen](https://lichen.sensorstation.co/)
[gatsby-mdx](https://www.gatsbyjs.com/docs/glossary/mdx/)
this site was made using gatsby and [kiezpilz.de](http://kiezpilz.de) was made using lichen
I appreciate that lichen is just four files of php. its so simple and lightweight and beautiful.
[@soapdog](https://andregarzia.com/) was able to quickly make a fork that supports [lichen-with-markdown](https://github.com/soapdog/lichen-with-markdown) to allow for inline-links (which gemtext does not support)
I also enjoyed discussing with [@trav](https://teafry.me/) that "maybe php isn't bad" ... what if that is just an idea we have, in part constructed by silicon valley facebook-react hype cycles?
what if php is actually pretty good at what it does?
on a related note, I've enjoyed thinking of wordpress as folk technology. its free, its open source, its used by millions for practical purposes.
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.
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.