Test Doc

Welcome to the Arsonry blog. This is where we’ll share project retrospectives, deep dives into the systems we build, and the occasional short note about something we’ve learned.

Why a blog

We build software across a wide stack — web platforms, desktop apps, firmware for single-board computers — and a lot of the interesting work happens in the seams between those layers. This space exists to document some of that, both for our own memory and for anyone curious about how we approach problems.

What to expect

We’ll keep posts focused and concrete. Some of the topics on the list:

• Performance work we’re proud of (and the dead ends that got us there)
• Hardware + software integration notes from the SBC side of the studio
• Opinions on tools, frameworks, and architectural choices
• Occasional announcements about what the team is up to

Cadence

Irregular. We’ll publish when we have something worth saying rather than on a schedule.

A style check

Since this is the first post, it doubles as a styling test. Inline code looks like const answer = 42; and block code like so:

export function greet(name: string): string {
  return `Hello, ${name}`;
}

Blockquotes are for quick asides or pulling out something said elsewhere.

Links point to places like our projects page, and we use bold sparingly and italics even more sparingly.

Tables can also be practical.

Header 1	Header 2	Header 3
Foo	Bar	Jaz
John	Doe	Banks

Mermaid diagrams perhaps ?

classDiagram
    Animal <|-- Duck
    Animal <|-- Fish
    Animal <|-- Zebra
    Animal : +int age
    Animal : +String gender
    Animal: +isMammal()
    Animal: +mate()
    class Duck{
      +String beakColor
      +swim()
      +quack()
    }
    class Fish{
      -int sizeInFeet
      -canEat()
    }
    class Zebra{
      +bool is_wild
      +run()
    }

What about checklists ?

• Step 1
• Step 2
• Step 3

Images, don’t we love em ?

---

That’s it for the welcome. More soon.