5 ms·

for people disagreeing with this comment, mind elaborating?

by Mimmy 3y ago

smarx007 3y ago
I think 800+ million Wordpress blogs are not planning to shut down in 2023 after reading GP's comment.
- Cyphase 3y ago
  I don't think there are 800+ million WordPress blogs. WordPress is used for lots and lots of websites that are not blogs at all.
  - smarx007 3y ago
    Thank you, I stand corrected, 800M+ WordPress installations.
- Heloseaa 3y ago
  This doesn't provide a counterpoint to the original comment's point. IMHO, it's true that a static site generator should be the way to go in 2023, instead of using a web framework with a db. I am personally running a hugo blog, on netlify, with netlify CMS. I have 0 costs, great performances, everything needed out of the box. What else to ask for ?
  - smarx007 3y ago
    Does your blog support comments? Also, for a company blog, an SSG likely means a requirement to know Git, which could be inconvenient.
    - deleted 3y ago
      [deleted]
    - Heloseaa 3y ago
      In my blog, comments are not supported, and it would be easy to add if I developed my own blog with Django. But I feel that this single feature does not overweight the simplicity and velocity I have with such setup. If you really need comments in your blog when using Hugo, you can still integrate them with Disqus https://gohugo.io/content-management/comments/ https://gohugo.io/content-management/comments/ In regards to the requirement to know Git: It is just necessary in the setup phase, the blog posts creation and edition are controlled through Netlify CMS for me.
      - smarx007 3y ago
        Interesting, thank you for introducing me to Netlify CMS, didn't know about it.
simonw 3y ago
My https://simonwillison.net/ https://simonwillison.net/ blog has been running since 2002 and has 3015 long-form posts, 6718 bookmark posts and 770 quotations. Plus tag pages, archive-by-date-pages, series pages and more. I don't particularly want to have to wait for all of that to build! It also offers faceted search against all of that, powered by PostgreSQL: https://simonwillison.net/search/?q=static%20site%20generators https://simonwillison.net/search/?q=static%20site%20generato...
- davidwparker 3y ago
  Incremental builds exist, so you'd really only have to build once: https://nextjs.org/docs/pages/building-your-application/data-fetching/incremental-static-regeneration https://nextjs.org/docs/pages/building-your-application/data... That said, personally, I love PG and enjoy using a DB. But I can see pro's to both sides.
- rcarmo 3y ago
  Well, taoofmac.com has 20+ years, 9000-odd pieces of content (that translate into 47.000 blob storage items), multiple navigation constructs (archives, backlinks - it’s a wiki - and even a 3D sitemap), and an incremental build for a post that links to 5-6 others (and resizes images, updates the home page, archives, linked page footers and backlinks) takes ~10s, including uploading the results (and an updated SQLite database) to Azure. I use SQLite FTS for full-text search (it’s the only non-static endpoint). A full site re-render on a Raspberry Pi takes 5 minutes, and a full reindexing - FTS plus linkmap - plus publishing around 10, but I only do that yearly or when I update things like CSS, layout, etc. It all runs off a Git hook, uses SQLite to hold all the FTS, base HTML and metadata, and is as asynchronous as can be (including my own asyncio blob upload library). Costs me effectively zero.
  - simonw 3y ago
    That's awesome. Parts of that sound a little bit like how my https://til.simonwillison.net/ https://til.simonwillison.net/ site works.
    - 3y ago
hparadiz 3y ago
I want to be able to hit edit on the post, do it right there, save and see my change immediately. I could set that up with a static site system but.... the admin I made for editing the post would remain the same. Furthermore the editor I have has a bind for CTRL+V that checks for images and automatically uploads them but also inserts an html tag for the media I just uploaded. This is something that is a terrible experience when editing a git repo having to manually link images and other media. Code: https://github.com/hparadiz/technexus/blob/release/public/js/media.js https://github.com/hparadiz/technexus/blob/release/public/js... https://github.com/hparadiz/technexus/blob/release/public/js/admin/posts/edit.js https://github.com/hparadiz/technexus/blob/release/public/js...

for people disagreeing with this comment, mind elaborating?

by Mimmy 3y ago

for people disagreeing with this comment, mind elaborating?

smarx007 3y ago

I think 800+ million Wordpress blogs are not planning to shut down in 2023 after reading GP's comment.

Cyphase 3y ago
I don't think there are 800+ million WordPress blogs. WordPress is used for lots and lots of websites that are not blogs at all.
- smarx007 3y ago
  Thank you, I stand corrected, 800M+ WordPress installations.
Heloseaa 3y ago
This doesn't provide a counterpoint to the original comment's point. IMHO, it's true that a static site generator should be the way to go in 2023, instead of using a web framework with a db. I am personally running a hugo blog, on netlify, with netlify CMS. I have 0 costs, great performances, everything needed out of the box. What else to ask for ?
- smarx007 3y ago
  Does your blog support comments? Also, for a company blog, an SSG likely means a requirement to know Git, which could be inconvenient.
  - deleted 3y ago
    [deleted]
  - Heloseaa 3y ago
    In my blog, comments are not supported, and it would be easy to add if I developed my own blog with Django. But I feel that this single feature does not overweight the simplicity and velocity I have with such setup. If you really need comments in your blog when using Hugo, you can still integrate them with Disqus https://gohugo.io/content-management/comments/ https://gohugo.io/content-management/comments/ In regards to the requirement to know Git: It is just necessary in the setup phase, the blog posts creation and edition are controlled through Netlify CMS for me.
    - smarx007 3y ago
      Interesting, thank you for introducing me to Netlify CMS, didn't know about it.

simonw 3y ago

My https://simonwillison.net/ https://simonwillison.net/ blog has been running since 2002 and has 3015 long-form posts, 6718 bookmark posts and 770 quotations. Plus tag pages, archive-by-date-pages, series pages and more. I don't particularly want to have to wait for all of that to build! It also offers faceted search against all of that, powered by PostgreSQL: https://simonwillison.net/search/?q=static%20site%20generators https://simonwillison.net/search/?q=static%20site%20generato...

davidwparker 3y ago
Incremental builds exist, so you'd really only have to build once: https://nextjs.org/docs/pages/building-your-application/data-fetching/incremental-static-regeneration https://nextjs.org/docs/pages/building-your-application/data... That said, personally, I love PG and enjoy using a DB. But I can see pro's to both sides.
rcarmo 3y ago
Well, taoofmac.com has 20+ years, 9000-odd pieces of content (that translate into 47.000 blob storage items), multiple navigation constructs (archives, backlinks - it’s a wiki - and even a 3D sitemap), and an incremental build for a post that links to 5-6 others (and resizes images, updates the home page, archives, linked page footers and backlinks) takes ~10s, including uploading the results (and an updated SQLite database) to Azure. I use SQLite FTS for full-text search (it’s the only non-static endpoint). A full site re-render on a Raspberry Pi takes 5 minutes, and a full reindexing - FTS plus linkmap - plus publishing around 10, but I only do that yearly or when I update things like CSS, layout, etc. It all runs off a Git hook, uses SQLite to hold all the FTS, base HTML and metadata, and is as asynchronous as can be (including my own asyncio blob upload library). Costs me effectively zero.
- simonw 3y ago
  That's awesome. Parts of that sound a little bit like how my https://til.simonwillison.net/ https://til.simonwillison.net/ site works.
  - 3y ago

hparadiz 3y ago

I want to be able to hit edit on the post, do it right there, save and see my change immediately. I could set that up with a static site system but.... the admin I made for editing the post would remain the same. Furthermore the editor I have has a bind for CTRL+V that checks for images and automatically uploads them but also inserts an html tag for the media I just uploaded. This is something that is a terrible experience when editing a git repo having to manually link images and other media. Code: https://github.com/hparadiz/technexus/blob/release/public/js/media.js https://github.com/hparadiz/technexus/blob/release/public/js... https://github.com/hparadiz/technexus/blob/release/public/js/admin/posts/edit.js https://github.com/hparadiz/technexus/blob/release/public/js...