TechTide Swarm 357, Landing Site

Marketing site, documentation library, and engineering blog for TechTide Swarm 357, a Python multi-agent orchestration framework for Claude agents. Publishes 124 documentation pages and long-form writing on agent architecture, LLM cost control, agent memory, and human-in-the-loop approvals. Built with Next.js 16, React 19, and Tailwind CSS v4, deployed on Railway.

Landing 0.2.2, compatible with techtide-swarm 0.2.2.

Surface	URL
Marketing and docs	https://swarm357.techtideai.io
Documentation home	https://swarm357.techtideai.io/docs
Blog	https://swarm357.techtideai.io/blog
Blog feed (RSS 2.0)	https://swarm357.techtideai.io/feed.xml
About	https://swarm357.techtideai.io/about
Changelog	https://swarm357.techtideai.io/changelog
Evals	https://swarm357.techtideai.io/evals
Machine-readable index	https://swarm357.techtideai.io/llms.txt
TechTide AI (LinkedIn)	https://www.linkedin.com/company/techtide-ai/
Backend API	https://swarm357be.up.railway.app

Contents

• Quick start
• Tech stack
• Repository map
• Commands
• Environment
• Content pipeline
• Blog
• Design system
• Deployment
• Editorial standards
• Related repositories
• License

Quick start

bun install
bun run dev

The site runs at http://localhost:3000. Documentation pages read from content/, which is committed, so the site builds without the core repository present.

To install the product this site documents:

pip install techtide-swarm==0.2.2
swarm demo

Tech stack

Layer	Technology	Role
Framework	Next.js 16	App Router, server components, static documentation
UI runtime	React 19	Component model
Language	TypeScript	Strict mode across the codebase
Styling	Tailwind CSS v4	CSS-first tokens declared with @theme inline in app/globals.css
Content	MDX with remark-gfm, rehype-slug, rehype-pretty-code	Documentation library and blog
Syntax highlighting	Shiki	Build-time code themes
Animation	Motion	Presets in lib/motion.tsx with reduced-motion fallbacks
3D	React Three Fiber and drei	Optional WebGL dither cursor, disabled on mobile
Theming	next-themes	Class-based dark mode
Frontmatter	gray-matter	MDX metadata parsing
Toolchain	Bun	Install, scripts, and content generation
Hosting	Railway	Nixpacks build defined in nixpacks.toml

There is no component library dependency. Components are hand written against the class tiers in lib/ui-classes.ts.

Repository map

Path	Contents
app/	Routes. Marketing at page.tsx, plus about/, docs/, blog/, changelog/, evals/, status/, security/, and the server-only BFF under api/
components/	Landing sections, site chrome, and documentation shell components
lib/	Shared modules: ui-classes.ts (class tiers), motion.tsx (animation presets), navigation.ts (nav model), site-url.ts (canonical URLs), eval-baseline.ts (baseline metrics), content/ (MDX loader, nav tree, table of contents)
content/docs/	Generated MDX documentation library
content/blog/	Generated blog posts
content/data/	Generated snapshots: eval-baseline.json, status.md, changelog.md
public/	Static assets, diagrams, and the Open Graph image
scripts/	generate-content.ts (sync), check-content.ts (CI guard), verify-links.ts (link resolution)
DESIGN.md	Canonical design system reference

Commands

Command	Purpose
bun run dev	Local development server
bun run build	Production build
bun run start	Serve the production build
bun run lint	ESLint across the repository
bun run typecheck	TypeScript with --noEmit
bun run check:content	Dash policy, URL policy, frontmatter, and UI interaction guards
bun run verify:links	Resolve every internal documentation link
bun run generate:content	Sync documentation from the core repository
bun run format	Prettier with the Tailwind class sorter

Run this sequence before opening a pull request:

bun run check:content
bun run verify:links
bun run typecheck
bun run lint
bun run build

Environment

# Public site URL for the sitemap, JSON-LD, and llms.txt
NEXT_PUBLIC_SITE_URL=https://swarm357.techtideai.io

# Public API base for read-only client fetches (health, agents, status)
NEXT_PUBLIC_API_URL=https://swarm357be.up.railway.app

# Server-only key for the demo BFF at /api/swarm/run. Never prefix with NEXT_PUBLIC_.
SWARM_API_KEY=

NEXT_PUBLIC_* values are inlined at build time, so they must be present when the image is built rather than only at runtime.

Content pipeline

Documentation is authored in the core repository and generated into this one. content/ is committed so the site builds independently.

1. Clone the core repository as a sibling directory:

git clone https://github.com/TechTideOhio/swarm-357 ../swarm357-sync

2. Edit the canonical Markdown there, or edit a hand-written page under content/docs/.
3. Regenerate:

bun run generate:content

4. Validate, then commit the regenerated content/ alongside your change:

bun run check:content && bun run verify:links

scripts/generate-content.ts converts Markdown to MDX, strips em dashes, and rewrites repository-relative links. A path such as STATUS.md resolves to its published route; anything else falls back to the canonical repository URL. Sidebar order comes from lib/content/nav.ts, and a documentation page listed there must exist on disk or check:content fails.

Blog

Posts live in content/blog/*.mdx and are hand authored. generate:content only scaffolds a slug that does not exist yet, so regeneration never overwrites editorial work.

Required frontmatter, enforced by bun run check:content:

Field	Purpose
title, description, date, slug	Listing, feed, and BlogPosting schema
cover, coverAlt	1200x630 JPEG under public/art/blog/, also the og:image
author	Rendered as a schema.org Person with worksFor TechTide AI
keyword	Primary search phrase, registered in content/data/blog-keyword-owners.json
tags, faq, updated	Tag chips, FAQPage schema, and dateModified

One post owns one keyword. check:content fails the build if two posts claim the same phrase or a post claims an unregistered one, which is what keeps the cluster from cannibalizing itself. Each post emits BlogPosting, BreadcrumbList, and, when faq is present, FAQPage JSON-LD. The index, RSS feed at /feed.xml, sitemap, llms.txt, and the landing page strip all read from the same loader, so publishing a post updates every surface.

Design system

DESIGN.md is the canonical reference for color tokens, typography, class tiers, interaction states, motion, accessibility, and the link policy. A reader-friendly summary is published at /docs/resources/design.

Before writing UI:

1. Import a class string from lib/ui-classes.ts rather than assembling Tailwind stacks inline.
2. Animate through a preset in lib/motion.tsx and read useReducedMotion().
3. Add new colors as CSS variables in both themes in app/globals.css, never as raw hex in a component.
4. Run bun run check:content, which enforces focus rings, touch targets, call-to-action radii, form control styling, and the dash policy.

Deployment

Railway builds this repository from its root with the Dockerfile, per railway.toml. The image installs with Bun, runs bun run build, and starts with bun run start.

The Dockerfile is deliberate, not a preference. Nixpacks injects every service variable into the build environment, which put SWARM_API_KEY into build arguments and into the image configuration. A Dockerfile build only receives the arguments it declares, so the build stage sees NEXT_PUBLIC_API_URL and NEXT_PUBLIC_SITE_URL and nothing else.

Variable	Availability	Reason
NEXT_PUBLIC_API_URL	Build and runtime	Inlined into the client bundle. Public value.
NEXT_PUBLIC_SITE_URL	Build and runtime	Inlined into the client bundle. Public value.
SWARM_API_KEY	Runtime only	Read per request by the server route. Never declared as a build ARG.

Verify after a deploy that the write key is absent from the image configuration:

docker image inspect <image> --format '{{json .Config.Env}}'

Editorial standards

• Demo writes go through the same-origin BFF. The write key stays server-side and is never exposed as a NEXT_PUBLIC_* value.
• Use-case scenarios on the landing page are illustrative composites, not named customer endorsements.
• Opik cloud observability is Not implemented in core. Local JSONL traces are the source of truth.
• Feature maturity mirrors the status page. Dream cycle is Experimental; HITL and SSE are Beta.
• Eval numbers are read from the committed baseline in content/data/eval-baseline.json through lib/eval-baseline.ts, never typed into prose.
• Public copy contains no em dashes or en dashes. This is enforced in continuous integration.

Related repositories

Repository	Role
TechTideOhio/swarm-357	Core runtime, roster, Memvid bridge, documentation source
techtide-swarm on PyPI	Published package

License

Apache-2.0. See LICENSE.

Created by Alex Cinovoj at TechTide AI.