rockerest’s avatarrockerest’s Twitter Archive—№ 19,229

      1. …in reply to @kmelve
        kmelve I don't personally have an opinion on server-side SSGs. All of the ones I've tried have been way too much overhead, so I wound up just writing pure NodeJS scripts that stitched data files into HTML templates. I don't think that's NECESSARILY the right way to go, but if you want
    1. …in reply to @rockerest
      kmelve to try it, I use template literals and functions 😂
  1. …in reply to @rockerest
    kmelve That includes CSS files (sent through postCSS, pushed to a CDN). For static assets, they NEVER go IN my API, and are instead in a third party image hosting service, so it's always just links. However, you could almost as easily have them in your own content API, then push to
    1. …in reply to @rockerest
      kmelve an image host.
      1. …in reply to @rockerest
        kmelve If you want to get a taste of one flavor of Web Component tooling without any _actual_ Web Components, I would upgrade the template literals and functions to lit-html and functions... which is still template literals, but it abstracts some of the boilerplate for binding data in.