An uneasy descent into order
Ah, order.
Organised.
Clean.
Starless now has tags that let me appropriately systematize both the lucid and fevered ramblings that I write.
This was something I've wanted to add since the initial (successful) deployment. It felt like a natural next step. I do have other plans but, for now, I'm focusing on building what I want to build, instead of trying to force some sort of derived set of features out.
They're not difficult to spot, clearly. Observe the top of an entry and you'll see them. On individual articles, you can click a tag to be taken to an archive of posts with the same tag.
If you struggle with this, I cannot help you. To be clear, I probably can. But I won't.
And the rest
A great deal of other changes were made in the same commit that the tag implementation was in. Granted, they're not nearly as obvious; mostly refactor work and minor improvements.
But if you're curious, read through the commit and review the summary:
configandviewswere finally moved to the root of the project (besidesrcinstead of inside it)- The broken meta tag output for the header has been fixed
- Views have been updated to only have two layers of nesting instead of three
- Components are better utilised in views for non-unique elements
- Tags are appropriately statically generated, similarly to how entries are
- A manifest and site icons now actually exist, instead of the Tempest default
- Use of
ImmutableArrayhas been improved in theEntryRepositoryto stop clashing data when build processes happen - Entries are now mapped manually to make sure that tags are loaded through appropriately
- Tempest has been updated to 2.7.0 (which means that some view paths now want to be wrapped in
root_pathfor some reason?) readonlyhas been applied to various places where it could be
A lot of changes for one commit but, once again, Starless isn't made under the guise of perfection. I'm usually averse to large commits but, given this stemmed from sitting down and writing code, I gave myself a break.