actix will instead use http 308, which is technically the more correct,
modern way to do this.
but http 308 isn't understood by some old browsers. today, 99.9% of
people wouldn't care about that. but i do.
since we want html template modifications to trigger content refreshes,
we need to reload the Tera renderer because it internally is caching
loaded html templates.
to be used to turn sublime text themes to css files which can then
be included in a pbe site to apply appropriate styling to syntax
highlighted code blocks
i don't intend to support syntect's alternative inline css html
rendering functionality which would otherwise allow you to skip needing
a separate css file (at the cost of some html output that is a little
bit more bloated and less customizable from a web styling perspective)
while we are actually using a CommonMark renderer instead of Markdown,
i think i just prefer referring to everything related to this as
"markdown" for simplicity's sake. meh.
currently syntax highlighting is limited to the default syntax
definitions that syntect comes pre-loaded with (which is the same
as sublime text's out-of-the-box language support)
since most often, we need to get posts sorted in descending order by
date, we now just store the actual posts in a Vec, pre-sorted by date.
everything else that needs to reference posts now does so by the post's
index in that Vec.
pages are also changed to be stored/referenced in a similar manner, but
it is somewhat less important for pages since we don't do any real
enumeration of pages at all anywhere. but it's nice to be consistent.
posts can be specified with a date only, or date and time as desired.
it is up to the site's specific template to render posts with an
appropriate date/time format string based on what the author's
preferences
Gered