Blue AppaloosaThere are many good reasons why I should build myself a portfolio website. But web development has gotten so complicated and tiring I just get overwhelmed before I ever start.
rafaelfajardo@BlueAppaloosa I still prefer my 2005 static website to my Wordpress powered one. Navigation is more challenging to update on the former though. I had set up template chunks and include statements so I could generate pages with BBedit. I have been loath to learn the new generators, Jekyll etc.
@rafaelfajardo Yeah, static hosting is about what I can afford. And I can build a site...I just don't remember much CSS anymore so I have to look up *everything*.
And even that would be fine (I can start with a free template and hack it), but then there's making it at least reasonably easy to update (so I don't have to relearn everything again in three months when I just want to add some new pictures), and attempting to combat bots/ai-scrapers (preparing images with watermarks, and maybe Glaze/Nightshade, and robot.txt files, and...)...
It's all that "extra" stuff that's really what gets me. Most of the pre-built stuff assumes you have a database and server-side scripting, so setting up a static site that's not *too* complicated to update means building most of it from scratch. And that means thinking about things like "should I only load a few images at a time to keep loading times down?", "How do I store meta-data so images can be filtered?"
And I know I'm overthinking it, but also, I can't stop myself.
@BlueAppaloosa I know that feeling, especially the “relearn how every three months”.
@rafaelfajardo Made something and posted it!
https://blueappaloosa.neocities.org/portfolio/
It's using an XML file as a "database", so to add to it I just toss the images into a folder and add a new entry into the XML file. It's not as easy as a CMS, but I should be able to just copy/paste/modify a previous XML entry, so hopefully won't be *too* painful.