liquidev
39a6155bdc
not to be confused with the Minecraft technical update I'm moving about the pages to be have a more flat, less nested structure. I feel like that'll improve URLs a lot, making them more readable than ever. over the years I've learned that flatter is better, and that tagging is generally a much more effective way of organising things. this doesn't get rid of categories entirely, as I think having the category makes the URL much a bit more readable in the end. my current vision does include a concept of "major categories" either way. |
||
|---|---|---|
| .. | ||
| _treehouse | ||
| about | ||
| design | ||
| games | ||
| music | ||
| philosophy | ||
| programming | ||
| treehouse | ||
| about.tree | ||
| design.tree | ||
| games.tree | ||
| index.tree | ||
| kuroneko.tree | ||
| music.tree | ||
| philosophy.tree | ||
| programming.tree | ||
| README.md | ||
| secret.tree | ||
| the-end-is-never.tree | ||
| treehouse.tree | ||
treehouse content
The treehouse is built on its own custom data format called .tree.
I'll spare the explanation, because it's an extremely simplistic format, but know that it nests:
- TOML metadata
- Djot markup
inside of itself.
TOML metadata is defined by Attributes from the treehouse crate.
Djot on the other hand has support for generic attributes.
Keys are not documented (read the generator if you want to know about them), but generally :-prefixed keys are
reserved for the treehouse's own purposes.
You probably don't want to read the content if you're not me. Browse the treehouse yourself, experience it fully, and then when you're sure you don't want to get spoiled, come back here and look for weird stuff.