4 ms·
I understand what you are saying... and you are right for most of it. You have to change your mindset a bit to use a static site generator. But you should keep
by sandreas 5y ago
I understand what you are saying... and you are right for most of it. You have to change your mindset a bit to use a static site generator. But you should keep in mind that "classic content management systems" have some major disadvantages, that are real:
- security - a static site tends to have less vulnerabilities and security issues
- performance - there is nothing faster than a static site, if the webserver is configured properly
- maintainability - a static site has no database and is easy to version control, backup/restore and manage
> Then a proper editor feels nice.
And there is no one that prevents you from setting up "content management" for a static site generator... I tend to use my JetBrains IDE, but there is also Typora or MarkText for editing my files.
> It also lets you have more metadata without resorting to a weird data format.
Hugo supports external data files, and with little effort, even static site search. See https://pilabor.com/blog/2021/05/building-a-blog-with-hugo/#site-search https://pilabor.com/blog/2021/05/building-a-blog-with-hugo/#....
> Besides, you can just log in and change something.
You can use github actions for deployment, then you can just use github editor to change something.
Just my 2 cents. Maybe try it for a smaller site... it's awesome.
- naet 5y agoStatic site generator isn't the opposite of CMS. I have made tons of headless CMS powered static generated sites. And I've made personal mark up powered sites. The markup is fun if you are the only person who will ever work on it, otherwise I recommend hooking up a proper content editable site.