Obligatory "ignore this space" : https://sacoronavirus.co.za

I don't like a mess. Reserving the word chaos for, that which has no pattern, the beach can hardly be called chaotic. But it is an example of change which requires no management. If you disagree with me, and feel the need to refer to fights with the ocean that involve public and private funds, I'm not about to try to change you.

A version vector, though a well-established trend, sends this user in all directions. Real numbers might be offensive to programmers who must work with things which other people call numbers, which can't be compared for equality. But we're grown-up Kiddoes who know that numbers can be compared without being converted. Leaving minors to parents, therefore, as well as musicians, and letting the majors bring the soldiers to make sure everyone is behaving like they were born in a barn for the personal space they contract for themselves, I ask the remaining programmers how meaningful it is to compare one version increment to another?

The question is an honest one: users only need to know how to compare two numbers. This we cannot teach them.

Users of a lib, who are programmers, know about apis. If you've an api and you know it clap your hands. Now, how many times did you clap them? Starting from scratch, the hounds that have me tied to this work suggested I put the api on the denominator. Now that makes me feel at home.

Initial identifiers are configurable, but the matter of diplomats brings us to another chapter, which has much to do with the making of corrections thereabouts, with the only means to do so, our words; and so we remember dancing figures who gave us theirs, in preference. Kiddoes know to stay away from clubs the entrance of which is the wagging of the tongue about having moved on from childhood.

Here's to you. The dynamic tags referred to as initial identifiers, listed in the following table, allow us to put the beach into a semblance of order.

<cache_control/>static dynamicApplies rules for If-Modified-Since handling (cannot be in an include file).
<play/>idReplaced with the (structured) contents of a clip.
<record>idPlaces the contents (sub-tree) into a clip, overwriting if necessary.
<include/>pathReplaced with the contents of the web relative path.
Note that the mapping does not utilize the web server's url mapping.
<form.cache_dynamic>Substitute tag: produces a <form> with the same attributes, but provides a query parameter which allows caching of blank forms.
<shipyard>Branch only visible on test servers.
<sailing>Complementary to <shipyard>.
<a.site>href activeclassSubstitute tag: produces <a> with the same attributes, but using activeclass instead of class if href points to the enclosing webdoc.
<redirect/>locationPHP rules: this aught to be the very first tag.
<shipyard-log/>Replaced with the contents of what has been sent to libconfig/brian.api-6

On the matter of self-closing tags, it must be understood that whether a tag is self-closing or enclosing, matters to the processing of them, not the parser: for all tags are closed automatically when their parent tag is closed. But if you don't self-close <include> what comes after it is now a sub-tree and therefore ignored;</include> you will find out for yourself by experimentation that the Egg-Sgml parser treats all tags equally--with the exception of <script/> and <style/>.

Getting started.

/templates_config.xml sets things up that can't be setup after a webdoc has been found. It only contains the one tag, and output is sent to /dev/null.

<main!-- api --
no-doctype!-- < 6Should be present. --
fallback=404!-- Loaded in case the requested webdoc is not found. --
shipyard-auth=923f1!-- >= 5Overrides value in shipyard.txt (file is still required). --
shipyard-doc=/shipyard!-- Loaded when shipyard auth fails. --
>Values are not defaults.</main>


The file shipyard.txt aught to be present on test servers, but it is recommended to keep this as an untracked file. The main intention is to prevent search engines from including your test sites, but if you're concerned about prying eyes an update will be necessary so as to keep the auth code inaccessible from the web.


These are grouped by api, which is therefore put as the number on top.

5/1Optional (downgrade from recommendation)
Place shipyard auth code into templates_config.xml (see shipyard-auth in the reference).
Remove the contents of shipyard.txt (the empty file must remain).
6/2Entry code
Custom templates.php requires modules.php (enqueue_modules).
Remove no-doctype from templates_config.xml.