About
Me
The site
Code
My site is built with my own framework, Bumblebee, which is based off of speakthesky's now-archived Zonelots, a fork of Marina Kittaka's Zonelets. I've also made use of a patch by strflr for a Zonelets bug that made its way into Zonelots. I've made some pretty major changes, but the fundamental logic and basic structure of the code remains the same. Moreover, I learned JavaScript by playing with the Zonelets code—I'm deeply indebted to it.
The theme switcher is based off this tutorial by Studytonight, with the stacking effect based off this snippet by Stephanie Eckles.
My guestbook and comments section code comes from Virtual Observer's comment widget. The moderation edits came from Frills. I have edited it further from there.
The syntactical styling for code blocks (e.g. here) is done with Prism.js, with a theme I customized. Charts are done with Chart.js 4.4.4, lightly modified.2
Tooltips are pure HTML/CSS, made with the help of this tutorial by ReplayBird.
God only knows how much help I've gotten from W3Schools and assorted StackOverflow answers over the course of this project.
Design elements
My favicon bee is vector art made by me. My background is also vector art, sort of, in that I used a program to vectorize a photograph (this one by Joel Holland) and then modified it to my liking, mostly by changing the colors to match my theme color palette and also by adding my bee;3 then I had to export it as a raster file because the SVG was huge. My buttons all started life as vector files on my computer, but I also exported them as raster files (in this case, for the aesthetic).
A note on permissions
The things noted above are made by people who are not me, and you'll have to go to them for permissions (though all are free, most have no stipulations, and the ones that do only require extremely reasonable things like "don't remove the credit statement from my code").
The rest of the code on the site is mine, and you should feel free to use whatever you want, however you want. I like being credited (especially if you tell me about it—I love to hear that people are making use of the things I share!) but it's a nice bonus, not a requirement.
When it comes to text and graphics, I'm a little more restrictive, in that I'd like to be credited if you reproduce any text and I would ask that you not use any graphics with the exception of the buttons.4
But code? Do whatever. If you want to use browser tools to inspect my code and lift a bit you like, go for it. If you want to see my styles or scripts and you don't know how to find them yourself, reach out by email; I'm happy to share. You can also reach out if you'd like clarification on why/how I've done what I've done.





