axi-designv1.50.0

Prose

Prose

One class on a container, styling the plain HTML inside it. A content pipeline can emit markdown with no classes at all and land inside the language.

.axi-prose

Long-form reading wants a different restraint from the rest of the language: the offset blocks that make a card feel physical would make a paragraph feel shouted. So nothing in here is blocked except the code block and the table, which are genuinely objects dropped into the text rather than part of its flow.

This is the one place rule 3's third weight lives. --axi-border-hairline draws inline code, the table rules and the list bullet, because either form step reads as too heavy for a line of running text - it is a prose rule weight and never an outline on a raised thing. The bullet is rule 7's diamond, drawn as a pseudo-element positioned against the list's own indentation rather than a background image, so it moves with the text.

A link inside prose announces itself in the accent, which is the opposite of the global default: a reader scanning an article is looking for links, and inheriting the body ink would hide them.

Rendered markdown, unclassed

Every element inside is plain HTML - no class but the container

Installing the suite

The fastest way to get every app is AxiOM, which installs and updates the rest for you.

Requirements

The desktop apps run on Windows and Linux. Combat analysis additionally needs arcdps installed and loading correctly.

  • A Guild Wars 2 installation
  • An API key with the account and guilds scopes

Verifying the install

axilog --version
axilog parse ./logs/20260920-wvw.zevtc --summary

If the parser reports zero agents, arcdps wrote the log but the fight never started.

AppWindowsLinux
AxiOMYesYes
AxiStreamYesNVENC only

Next steps

Continue to your first fight report.

<div class="axi-prose">
  <h1>Installing the suite</h1>
  <p>The fastest way to get every app is <a href="#">AxiOM</a>, which installs and updates the rest for you.</p>
  <h2>Requirements</h2>
  <p>The desktop apps run on <strong>Windows and Linux</strong>. Combat analysis additionally needs <code>arcdps</code> installed and loading correctly.</p>
  <ul>
    <li>A Guild Wars 2 installation</li>
    <li>An API key with the <code>account</code> and <code>guilds</code> scopes</li>
  </ul>
  <h3>Verifying the install</h3>
  <pre><code>axilog --version
axilog parse ./logs/20260920-wvw.zevtc --summary</code></pre>
  <blockquote><p>If the parser reports zero agents, arcdps wrote the log but the fight never started.</p></blockquote>
  <table>
    <thead><tr><th>App</th><th>Windows</th><th>Linux</th></tr></thead>
    <tbody>
      <tr><td>AxiOM</td><td>Yes</td><td>Yes</td></tr>
      <tr><td>AxiStream</td><td>Yes</td><td>NVENC only</td></tr>
    </tbody>
  </table>
  <hr>
  <h4>Next steps</h4>
  <p>Continue to <a href="#">your first fight report</a>.</p>
</div>

Prose at the reading measure

Wrapped in a narrow page inside a panel, which is how a doc page is built

First run, in order

  1. Sign in with your API key.
  2. Point AxiBridge at your arcdps log directory.
  3. Paste a Discord webhook and send a test report.
<div class="axi-panel">
  <div class="axi-prose axi-page axi-page--narrow" style="--axi-page-pad: 0">
    <h3>First run, in order</h3>
    <ol>
      <li>Sign in with your API key.</li>
      <li>Point AxiBridge at your arcdps log directory.</li>
      <li>Paste a Discord webhook and send a test report.</li>
    </ol>
  </div>
</div>

Rules this answers