Why this sucks: thoughts on how disappearing TV series mirror the Flickr debacle from four years ago.

@felix ... I feel highly attacked by the intro of that blog >.> (both in the amount of blogs I've made and then quickly abandoned, and using static generators rather than a more traditional CMS)

@melindrea I discontinued two blogs this year. And that was the point: using a SSG means you can safely stop at any point, and your blog will just sit there forever.

@felix Indeed. I'm currently working on a few bits on mine (hosting it on github pages). Yes, there's a touch of a charge for the domain name, but no cost for the hosting, which makes things a lot easier.

@melindrea *goes check* Your first post is fun! But the text needs more contrast.

@felix Yeah, I've noticed that too, so the next version (which I might as well push up now, thinking about it) has darker text colour in the light mode. Thanks! =)

@felix btw, out of curiosity ... Are you more coder/developer or designer?

i've kind of always assumed that, unfortunately, a lot of static site generators are more for people who like to get their hands dirty in code (partly because docs tend to be abysmal ...), but I saw one issue on the generator I use which lamented the lack of docs because "SSG is mainly used by designers". Which is pretty much the opposite of what I would've thought.

@melindrea Are you kidding? There's no way a less technical person can make any use of the typical SSG. Take Pelican: at the very least you need to know what pip and make are and how to use them.

@felix that's what I thought too! I'm sure there are some SSGs that are easier to dig into when you have no interest in the guts of the building and mainly want to focus on CSS and HTML, but ... Yeah ...

Thinking it through, I think my thoughts there are based on how to set up so that "all" that needs to be done is templates + CSS, then you still need either a) knowledge with terminal to build or b) someone having built a GUI for you.

And with b) you're better off using a CMS.

@melindrea Of the well-known options, BashBlog is easier, needing only general skill with the command line. I tried to make mine in the same spirit; AntiWiki even has a GUI. But yeah, a CMS makes more sense sometimes.

@felix Mine is probably a lot more complex than some others, but that's because it's literally built for *me* =)

I *think* anyone who'd use it as blogging software could *probably* figure it out with docs ... (though tags being defined in package.json might throw some for a loop).

I try to hide a lot of the complexity in commands behind scripts--whether make, NPM, composer ... those are the ones I know immediately. So "npm run build" , not "export NODE_ENV=prod && node index"

@melindrea It's probably better to accept that a SSG isn't really a kind of product but more of an approach, like Forth. You're supposed to make your own, not use one.

@felix agreed. I do like metalsmith--it has a (to me) fairly straightforward approach: you take all the files from "src directory", dump them into "build directory" and do whatever needs to be done to the files in between (though building plugins/treatments of the files isn't always obvious).

Which, hmm. Might be a decent idea for a small series of posts: how to build specific bits, like "function to handle things" and "small plugin". Since all my code is up on github it's not secret =)

@melindrea Not that making themes is always easy. The typical SSG makes it absurdly convoluted, and just try looking at one made for PluXML or Flatpress. Pelican is again at the upper limit of what I'll put up with.

@felix I think there's a very strong sense of elitism among Flickr Pro subscribers even before the SmugHug acquisition, so it was expected that they'd further distance themselves (at least in theory) from, say, Instagram, by pushing "amateurs" out of the platform.

@a Well, they succeeded. I hope they're happy now.

Sign in to participate in the conversation
Wandering Shop

The Wandering Shop is a Mastodon instance initially geared for the science fiction and fantasy community but open to anyone. We want our 'local' timeline to have the feel of a coffee shop at a good convention: tables full of friendly conversation on a wide variety of topics. We welcome everyone who wants to participate, so long as you're willing to abide by our Code of Conduct.