Submitting this for revision/consideration. Gonna try some CriticMarkup.

[RMBLRX]

This will need to be marked up in revision and then have those revisions implemented as proof-of-concept for CriticMarkup's inclusion into our workflow.

The post itself might be a bit heavy and abstract, so I'll need time to let it steep anyway. One funny thing about it is that it contains so many reference links that it pushes the limits of my present hexadecimal ref-numbering concept (which will be elaborated in the contribution guidelines at some point). We'll also need tags, but we don't currently have any usage for those in our theme yet (at least none that I'm currently aware of, and as a side note, we'll need those for the large volume of wayPoint projects already accumulating).

[RMBLRX]

Started off on the wrong foot. Correcting this to #9 in order to set a better precedent on how to go about submitting posts for revision or approval (i.e., naming the branch after the post, though in the future, I would prefer preceding the post title with post/ or something). This will also extend to the editing of most pages, I suppose, particularly if they are already more or less complete or someone's pet project (assuming that whoever's committing even has the option to merge changes to begin with).