The brand set
Four SVG files, all text already converted to outlines so nothing depends on a font being
installed wherever they are used: a light and a dark wordmark, and a light and a dark "log by"
lockup. Every conformant integration may cite its tier in plain text; the graphics below are
an optional way to show the same thing. An inlined copy keeps role="img" and the <title>; an <img> copy uses the alt text instead.
The wordmark
The wordmark is the name on its own, for a byline, an about page, or anywhere else the name needs to appear as a mark rather than as running text.
The "log by" lockup
The lockup is optional. Nothing about a conformance claim depends on displaying it, and removing it from an integration changes no conformance statement that integration makes. Where it appears, it reads "log by XC Athletes," and if it is a link, the link goes to the athlete-facing part of this site, never to a signup page or anything promotional.
An integration that would rather not ship an SVG can use the text-only equivalent instead:
the sentence "Training log hosted by XC Athletes," as plain text, styled however the rest of
that integration's UI is styled. That sentence is also the alt text an embedder supplies
whenever either lockup file is placed as an <img>: screen-reader users get
the same statement whether the mark renders as a graphic or not.
Sizing and clear space
Do not render either mark smaller than 14px tall; below that the letterforms stop resolving. Give the mark clear space on every side at least equal to its own x-height, meaning no other text, rule, or graphic element sits closer than that to the mark's edge.
Writing the name
The name is two words, both capitalized: XC Athletes. The host name is
written lowercase: xcathletes.org. Neither is ever run together as one word;
"XCAthletes" is not a form the name takes anywhere.
Making a conformance claim
An integration that has passed the published conformance suite for a tier may state that fact in either of two forms. The developer-facing form names the suite directly, for changelogs, READMEs, and API documentation: "passes the xclog-conformance suite, writer tier" (substituting reader, writer, or roster-aware as earned). The plain-English form is for end users who have never heard of the suite: "Built on the XC Log training-log standard, writer tier."
Either form is available to any integration that currently passes conformance for the tier named, and only for that tier; an integration that has passed reader tier does not get to say writer tier because it plans to add writes later. Conformance can also be lost: if an integration stops passing the suite for a tier it has claimed, or the claim misstates the tier actually reached, the right to make that claim ends until conformance is restored.