This website, as seen here, is static html and css, with no scripting, no cookies or anything else like that. Furthermore, as it also says in the footer, I make an effort to not link any offsite content to improve loading times and privacy. The fonts are uploaded directly to the hosting server, and so are the images.
More on the images: to improve loading times, they are exclusively provided in the wonderful webp format. Thanks to this, a reasonably high fidelity is achievable with astronomically small file sizes, a few dozen kB at most. Furthermore, there are also low-quality versions of bigger images (usually 800px wide and with the compression cranked) which are loaded first by referencing them in the body of the site. Only then are the images from the css "sources" loaded, ensuring that an image is available quickly, and the high-quality one loads on top.
I strive to maximise accessibility — please ⛓ contact me if there are any issues, I will be happy to correct them! I apologise for any omissions, whether they be poor contrast, screen reader difficulties, or anything else. As such, every image on this website that uses the ⛓ Image Viewer system has a hopefully helpful verbal description, both in the "title" and "alt" tags, as well as displayed in the body of its Image Viewer page. Again, if I happen to forget any, or if they're not helpful enough, I'd be happy to correct them and I'm sorry for not doing them right the first time around!
As for how I keep all pages consistent, I wrote a little bash script that scans for special markers and inserts the contents of a specified file. As you can imagine, this enables a wonderful level of recursiveness. Many elements, like menus, common css expressions and entire portions of boilerplate, are relegated to separate files loaded at buildtime. The resulting static files are highly self-sufficient, and quicker to load, due to including everything internally.
As an example, this is the template file that I use when making a new page:
//INS!init.html
TITLE GOES HERE
//INS!menus.html
//INS!submenubegin.html
SUBMENU CONTENT GOES HERE
//INS!submenuend.html
//INS!content.html
//INS!titlepostbegin.html
IMPORTANT CONTENT IN THE MAIN FLOWBOX GOES HERE
//INS!postend.html
//INS!postbegin.html
REGULAR CONTENT IN THE MAIN FLOWBOX GOES HERE
//INS!postend.html
//INS!finisher.html
...and here is the page that it generates:TITLE GOES HERE
//INS!menus.html
//INS!submenubegin.html
SUBMENU CONTENT GOES HERE
//INS!submenuend.html
//INS!content.html
//INS!titlepostbegin.html
IMPORTANT CONTENT IN THE MAIN FLOWBOX GOES HERE
//INS!postend.html
//INS!postbegin.html
REGULAR CONTENT IN THE MAIN FLOWBOX GOES HERE
//INS!postend.html
//INS!finisher.html
As you can hopefully see, it's a perfectly complete "new avery.dog"-style page, with everything I might need ready to go! Click ⛓ here to view it in your full browser window.
...or, I suppose, you can just navigate within it, if you're so inclined. Go ahead, use the navbar to open up this page inside of the iframe. Come on. Do it, I know you want to. See how deeply you can recurse before your browser gives up on you! :]
Ahem. Anyway. If you want the script, it'll be available in the ⛓ Creations section once that's finished.
