Someone commented “I love the mono lake painting by the way, what was the prompt?” but then deleted it. I wanted to post my reply because I wanted to Yes-And their funny bit:
Lovely work!! On “Where did you paint this?”, I've gotten this myself as I've painted off and on over the years too, mostly landscapes. It's what drove me to start a side project years ago to put art on the map (consolidate specific viewpoints, photo comparisons, streetview, historic maps, etc). As those things go, I never got beyond a crude app while life competed for resources. Picked it back up this year, hoping to "launch" a first version soon. Mostly historical stuff because that's what's openly available, but maybe someday it could be a tool for placing my own and other artists' contemporary work!
I approached the same “static for everyone, dynamic for me” need from a different angle. Instead of building my own editor, I use self hosted Grist instance with customized widgets. Publishing means building a versioned snapshot of the catalog and pointing a tiny current.json at it. Old versions never change, so they cache forever and nothing needs invalidating. Staging and production are just two pointers, and rolling back means pointing back at the previous version.
jrm4today at 4:21 PM
So...yeah. Always been baffled at how this didn't become more of a norm.
It's never been much to look at but my personal website (from which I also serve public info and reading for the classes I teach for a living, when I can) has been a static running from http://zim-wiki.org -- for about 20 years or so. Pretty sure from well before the phrase "static site generator" even existed.
Didn't bother to read much about the tech because your art was too distracting. Lovely renditions! Love the difference between the framing in the shots of the scene vs what was chosen in the paintings.
ueantoday at 6:54 PM
I just wanted to say that the typeset, font, spacing, colors, design, and images are really nice to read and view. What a pleasure.
zelphirkalttoday at 4:57 PM
I am glad it still works when visiting with noscript blocking scripts. I didn't notice any defects while scrolling through the page. Well done.
sprainedanklestoday at 5:21 PM
Lovely, I am about to embark on building an art website for my spouse, and this is a great example of a technical approach I would be interested in using - cheers to feeding the two wolves! :)
ricardobeattoday at 6:07 PM
I've been using bunny.net for similar purposes, it's great and faster than everything else. It has a CDN, image resizing, edge functions, and a CLI that can do most of the setup automatically for you, including CI.
It's also nearly free for hosting small scale sites, my average spend is currently $0.22/month.
zodwicktoday at 6:06 PM
Great work. Pleasantly surprised seeing Kochi here ( I'm from there )
cowleveltoday at 8:10 PM
So it's a server-side rendered website, not a static one.
deletedtoday at 3:47 PM
zzzeektoday at 7:25 PM
OK for me the huge news of this blog post and I went through the whole thing to see this is that we have a bona fide visual artist that works with actual physical art mediums, *and* they nonetheless are using LLMs to produce the presentation structure, that is, to build out their website architecture (and also just in this blog post I see many highly polished visual elements that you pretty much only see on LLM-assisted projects).
this model: "I produce creative art that may be seen as threatened by AI, yet I still use AI to get things done" - seems uncommon right now. People who do visual art or writing especially, and to a lesser extent musicians, are just in permanent pitchfork mode when it comes to AI.
hingler36today at 3:53 PM
Not much to add, I just wanted to say this was lovely to read!