FINALLY!! A website We're proud of. The last one served a purpose, but it wasn't what We wanted.
Here is the (very technical) story of the new one!
Story time~
So years ago, We developed an app using Node JS and Next.js that generated static website files from easy to edit markdown files on a local machine and a custom directory structure we liked. The static files were VERY easy to host as there was no need for a database, and MANY places host it for free (We've used Gitlab pages for years)
Flash forward some time, We wanted to update to include Our stream content. However in the time between updates, Node had a major update that broke a ton of the code. So when faced with either troubleshooting old code and old versions, We decided to start again. In this same time frame away. the scene of static site generators has also expanded a ton!
Enter MkDocs, which looked very promising! At least at first... Even though We don't know much about Python, it was an opportunity to learn it. We'd been meaning to for awhile now, after all.
SO! We fumbled through it! Oddly, found more information about how to use MkDocs from a derivative project, Material for MkDocs. And developed the site around that. And... it lasted. It worked fine! Sorta... Though, found it a little hard to understand what APIs We could hook into in order to make future updates and cool features. It was a purely functional platform.
BUT! We're artists, you see! And creativity felt hampered and uninspired by this unfamiliar software. So functional as it may be, MkDocs simply wasn't going to cut it for Us.
Back to the drawing board then! Or... at least the research table. With a couple other potential options also available, even considered the "Indy Web" like Neocities. But, decided to give one in particular a try (thanks to the push from a youtuber that We like) We found 11ty (built with Node JS)!
The website today!
Over the last few weeks, Siobhan, Mathias, Sariana, and myself all worked tirelessly building out this new website design using 11ty. And this time, even built within a Docker container (using Podman) to hopefully future proof the stack, and make edits much easier to do across devices.
We will still be hosting the website through GitLab Pages. Though this time probably going to avoid using a Git Submodule for the content as we did last time. While sound in theory it added a layer of complication that We... simply don't need.
So with that... I'm excited for the new possibilities! :3
