Pelican deployment successful, some thoughts
I finally have this blog deployed and I have some initial thoughts about the experience of deploying it, about pelican itself, and improvements. I want to revisit them but I also as usual am under a time crunch, so here is the cliff notes version.
- Describe later how I did this deployment. Here is the stack:
github.com
for sourceactions
to build pelican and deploy to vercelcodespaces
to edit the code and make new pagesvercel
to host on the hobby tier for freeregistrar
pointed my domain to vercel nameserverspelican
for the cms framework, static content makes for easy hosting
- Good things about pelican
- Easy to deploy anywhere
- Small footprint
- Static content lets me use the free hosting on vercel
- Control over most aspects of the pages
- I actually like the lo-fi look functionality.
- Things I don't like about Pelican as a blog
- It's really hard to set up an index page that isn't a blog
- It not entirely intuitive to understand to how pages/blog works
- Getting themes is a lot of steps
- There is not a good WYSIWG solution
Anyhow those are my initial thoughts. It's St. Patricks tomorrow and it's time get the Guinness.