what's going on inside the house? (a changelog)

revision 10: I am speed
- the treehouse now caches most static assets, so that they don’t have to be redownloaded. especially that very large font, which I should probably optimize now that I think about it!
  - there are some minor exceptions to this, which include:
    pages themselves. we cannot cache those at all. well, maybe in release mode, for like 10 seconds, which defeats the point.
    we can only cache those assets which are guaranteed not to change given their URL.
    
    caching on the treehouse is performed by means of a ?cache query parameter which contains a truncated BLAKE3 sum of the cached file’s contents. that way we can tell the browser to redownload the asset by changing out the hash.
    
    this is impossible to do for pages, because they may change at any point in time.
    I tend to update the treehouse very often - including post-deploy, if I fuck something up - so if I enable caching for e.g. an hour, and people visit the broken version, they’re then stuck with a broken version for an hour. seriously, timed caching is not a good solution for incremental website updates.
    except for /sandbox maybe, because that tends to be fetched in short bursts… I’ll think about it.
    linked branches. it’s hard and not worth it for the few extra kilobytes saved - for snappiness it would be much better to prefetch branch content when the user hovers over a branch.
    not sure what to do about mobile devices, because they don’t have a hover state.
- more images now have proper width="" height="" attributes, which should help eliminate layout shift when loading pages.
- the treehouse is now powered by Djot, not Markdown! took me an evening or two to rewrite everything to the new markup, but I think it’ll be worth it. I can already see some pretty big clarity wins.
  - my favorite feature so far is that you can add custom attributes to anything. like this, for example:
    
    {:program=haku} ```haku (- 100 35) ```
    and have you noticed that there’s a code block inside this code block? you can’t do that in Markdown!
    
``````djot {:program=haku} ```haku (- 100 35) ``` ``````
- literate programming blocks are now correctly rendered with JavaScript disabled, thanks to me rewriting the HTML renderer in the Djot transition.
- I also took the liberty to add some highlighting to missing emojis. meaning they now stick out like a sore thumb :sore_thumb: to nag me about adding them in (or pulling them in from other branches. hello :verified: :TODO: :DONE: how have you been)
  - yeah yeah we all know how ad blindness works, this is totally not gonna push me to do this isn’t it
revision 9: summer cleaning
- cleaned up a bunch of pages! see new for the details
- there are now a bunch of colorful icons next to pages
  - experiments show that this improves readability by 100% despite the icons being ugly and blurry due to not integer-scaling. it’s not like I can really fix that though, since they’re next to text; good luck making pixel-perfect icons that are meant to appear next to fonts of like 10 different sizes that increment by very little.
    maybe one day I’ll hint them to a bunch of sizes…
- the treehouse’s design is now certified 4% more accessible :verified: by means of using rem metrics for all the UI elements, so now the UI will scale depending on the font size you’ve set in your browser. ain’t that cool?
  - on the one hand it seems cool, but I have to note here that I designed this website with 14px fonts and pixel metrics in mind. having switched it to rem everywhere might have produced some wonky layout bugs; if you find any, please report them to me!
  - I also have the feeling that the layout is now a lot more spacious, but I can’t quite figure out why. you may expect the layout to shrink a bit in the coming days. or not. I use a slightly smaller font size in my browser so I might just forget about it.
revision 8: fancy syntax highlighting
- over the past few months the treehouse has been receiving a bunch more syntax highlighters
- there are now syntaxes for Lua, Rust, JSON, and C!
  - C++ probably coming soon™, but with its much more complex syntax it’s likely the highlighting isn’t gonna be as nice
    and I’m only mentioning it because there are some C++ code snippets in the treehouse, and it would be really nice if they finally started being highlighted
- what’s cool is that all the syntax highlighters work even if you have JavaScript disabled. which I wouldn’t recommend, but it’s nice. because you absolutely do not need to embed a heavyweight JavaScript library for this
  - and it enhances the responsiveness! you don’t need to wait for code to be highlighted.
- I was also told there’s a secret now? like, no clue what they mean by that but cool?
revision 7: the main page is now a lot more colorful :rainbow:
- each major content category now has an icon and a liquidex brand color™ assigned to it
  - there may be more colors in the future, given that there are probably gonna be more categories
    and I’d like the other non-hobby categories to get their own colors too, but the four that are currently here are good enough for now.
revision 6: it now works on Webkit
- this was a hefty refactor, but I introduced a replacement for the standard is="" attribute that works on Webkit.
  - seriously, fuck you, Apple. wish the people who work there and oppose industry standards would stop sitting there with a finger up their ass and accept that reality is not always what you want it to be.
    even as I’m writing this, I’m trembling over how half my website is probably gonna break after this refactor, due to me having it written in pure JavaScript rather than TypeScript, but eh, fuck it.
    
    reality is not always what you want it to be.
    just know that I’m writing this not because I think the standards are good, but because one vendor not following them just results in extra work on our part - the developers’ part - doing more work than is actually really necessary to accomplish a certain task.
    using the browser’s built-in capabilities is good. you’re just making me (and hundreds of thousands of other developers) write a shitty, slow version of what the browser could do by default, had it been following Web standards.
- also, the links are now a bit prettier! everybody likes pretty links, right?
  - page links no longer need to have the .html at the end. I’m still in progress of porting the website over to the new format, so you may see some spots where there’s a .html extension.
    buut if you really wanna, you can strip it off when sending the link to other people.
revision 5: added news page!
- this page will show you all the updates that have been happening since your last visit
- it will also lightly nag you whenever there are new posts with a 1 badge
  - if that’s too annoying for you, it’s easy to disable - scroll down on the news page and there’s a (collapsed by default) settings section for the page
- another thing: there are now indent guides! my girlfriend said these make the website a lot more readable for her, so I guess they’re good
revision 4: there’s now a thing in the footer
revision 3: just a bit more polish
- emoji tooltips now have a neat animation on hover rather than just sort of appearing and disappearing immediately
- pages can now have thumbnails that display in embeds
revision 2: just really comfy UX
- first thing you probably noticed: added indent guides (may require a modern browser due to usage of :has)
- added some nice animations
  - hovering over branches is now animated
  - when a branch is focused via a hyperlink, the background will now pulse in and out to grab your attention
    this replaces the previous dotted underline which my friends reported to be hard to spot
- added dates to branches (requires JavaScript)
  - JavaScript requirement due to dates being formatted in your system’s locale
  - right now these are invisible on the mobile layout because it’s unclear where they should be positioned
- added page titles (you can see them on this page!)
- fixed “hey expand me” chevrons sometimes shifting layout when a branch is expanded
  - yeah, these ones - like the one that just disappeared when you clicked on the branch above
- /b endpoint is now used for shorter links. it also generates OpenGraph metadata so that Your Favorite Messaging Platform can display the linked branch’s content
  - what’s left here is to add some more OpenGraph to do stuff like: thumbnails, default descriptions, and so on and so forth - but the seeds for that have already been planted
- internals: branches are now based on flexboxes rather than background images. this requires sending a bit more HTML, but the layout is a lot more stable as well as being easier to extend