3 ms·

I've tried this twice and it didn't work out for me. If you want even just some features like categories and tags you end up with a tool that has some weird me

I've tried this twice and it didn't work out for me. If you want even just some features like categories and tags you end up with a tool that has some weird metadata language you put over the actual text, the markup obviously is yet another slightly different kind of markdown, and then learn the umpteenth way of linking to internal sites. Then you run the generator, triple check everything is not messed up because of a misplaced space in the meta data and then upload everything to your server. Compare this to a simple wysiwyg editor in the browser where you hit save. I've made my choice.

matt_kantor 5y ago
I don't think I understand your point. Weird markup vs WYSIWYG authoring is orthogonal to static vs dynamic serving.
- iforgotpassword 5y ago
  Static serving usually means you don't have anything running on the server but an actual web server, and you upload the static files to its webroot. So it's not technically possible to have any fancy editor in your browser. You have all the brains in some tool you run on your machine that processes your markup files and spits out html files. Sure, you could throw PHP or whatnot on your server, have a nice editor and whenever you edit or add content it statically generates all the html files, which would probably technically still be called a static site generator but then I don't see why you'd want to do that instead of just going all the way and use normal blogging software and putting a cache in front.
  - realityking 5y ago
    There’s a whole category of headless content management systems, either API or git based, to give a friendly editorial experience (also for non technical editors) while maintaining the advantages of static sites. Here’s a good starting point (not my post): https://pagepro.co/blog/jamstack-headless-cms-which-one-to-use-in-2021/ https://pagepro.co/blog/jamstack-headless-cms-which-one-to-u... Disclaimer: I work for a vendor in this space

matt_kantor 5y ago

I don't think I understand your point. Weird markup vs WYSIWYG authoring is orthogonal to static vs dynamic serving.

iforgotpassword 5y ago
Static serving usually means you don't have anything running on the server but an actual web server, and you upload the static files to its webroot. So it's not technically possible to have any fancy editor in your browser. You have all the brains in some tool you run on your machine that processes your markup files and spits out html files. Sure, you could throw PHP or whatnot on your server, have a nice editor and whenever you edit or add content it statically generates all the html files, which would probably technically still be called a static site generator but then I don't see why you'd want to do that instead of just going all the way and use normal blogging software and putting a cache in front.
- realityking 5y ago
  There’s a whole category of headless content management systems, either API or git based, to give a friendly editorial experience (also for non technical editors) while maintaining the advantages of static sites. Here’s a good starting point (not my post): https://pagepro.co/blog/jamstack-headless-cms-which-one-to-use-in-2021/ https://pagepro.co/blog/jamstack-headless-cms-which-one-to-u... Disclaimer: I work for a vendor in this space