In addition, a whole bunch of the site is backed by a database. For example, 3dos, mats, news, sots, lotw, etc. Maintaining a server with dynamic content is a pain. Especially when the "dynamic" part has actually been static for something like a decade.
I previously shared an "updated" design that doesn't use frames. It looks very similar (on purpose) but uses ... um css grid instead of frames (frames are bad, mmmmk). https://www.massassi.net/newdesign/
I have been slowly plugging away at a method for turning most (not all) dynamic resources into static ones. My current plan is to make everything static _except_ the forums and the levels/downloads. I'll deal with those at a later date.
As I was converting the site (I'll discuss this more in a bit) I got sad because so many sites that were linked to by massassi (in the news section, articles, programs, even the 3do site links to what were cool personal sites) are just dead. In the interest of making the content of massassi available (even if the site itself goes away at some point, like if I crash my bike and break my neck), I have the following proposal:
Turn Massassi into an "Open Content" site. This means that virtually all our content will be available in a public repo like github or similar. If anyone wants to make an edit to a page, just fork the repo, make the change, create a pull request.
This necessitates making all resources available as basic files (as opposed to dynamically generated pages). Following the current trend I am converting virtually everything to sets of markdown pages that are then (via a very simple static site generator) converted to HTML for publishing. I don't have the site online yet but I am going to try to get it there in the next couple of weeks (even if it's incomplete, which it will be).
Once I make the content available I will also make the site generator code available so anyone could just edit the html template and make a massassi of their own (with own look and style or whatever).
Is anyone interested in helping out? At this point I've gone through about a dozen tutorials and converted them to markdown. Some of the tutorials are really... unique... and I hate to lose that so if a tutorial has a design that doesn't match the current site design, I am also preserving those and making them available (as html in addition to the converted markdown files). It's a bit of a pain because the tools I'm using to convert html to markdown aren't perfect so for some tutorials I spend quite a bit of time making sure the markdown looks good and the tutorial still conveys the right information. For example in the old html we'd just juice the font size up for headings/sections and font information is stripped from the markdown so I end up finding the parts that were supposed to be big and making them into headers. Also sometimes tables get screwed up and the tutorials actually contain some cool data in tables. Also things like email address links and busted site links should be removed (working site links can be preserved).
I need help with the tutorials specifically because there are a lot of them and after making sure the idea worked I'm moving on to making other sections static (3dos, mats, news, etc.).
There are some considerations:
- people could just steal the site content -- yes, they're doing this already, though; I'm really comfortable just "letting it go" at this point
- levels - after the rest of the site is open/released I will worry about levels; I definitely want to release these as well, we just might lose or freeze comments/ratings
- I thought I had more things but I don't, but I need at least 3 bullets for this list to make sense