docs(brand): add org logo, wordmark, profile README, sibling README drafts, and marketing site#5
Merged
Merged
Conversation
…rafts, and marketing site
Introduce a complete AgentDispatch brand kit under brand/:
- logo-mark{,-light}.svg + wordmark{,-dark}.svg: a "dispatch hub" mark
(one inbound spoke, glowing core, two outbound spokes to nodes) plus
horizontal wordmark lockups, for use as the org avatar and as the
README hero across every repo.
- profile-readme/profile/: org profile README intended for a .github
repo at the org level, with shared brand assets co-located.
- proposed-readmes/: drafts for each sibling repo (core, sdk-js, cli,
store-sqlite, adapter-aws-agentcore, worker-agentcore,
adapter-template, docs) using the same hero, navigation, and tone so
the whole stack reads as one product.
- website/: zero-build static site (index.html + styles.css +
script.js + assets/) ready to drop into GitHub Pages, Netlify, or
Cloudflare Pages. Includes OG image and SVG favicon.
- README.md (mcp-server root): rewritten as the viral entry point —
"give your AI assistant a fleet of cloud agents" — referencing the
new wordmark and tying the package to the rest of the stack.
- brand/README.md: deployment guide explaining how to publish each
asset (avatar, .github repo, per-repo READMEs, site) since this
session only has write access to mcp-server.
…oice around Claude Code, OpenClaw, Hermes
Mark redesign:
- Drop the abstract three-spoke hub for a cloud silhouette that
literally spawns three agent tiles via outbound spokes. Reads as
"cloud → spawn agents" instantly at favicon size.
- Glow + activity particles around the cloud. Play-glyph inside each
agent tile to reinforce "run/spawn".
- Refreshed wordmark, dark wordmark, favicon, and OG image to match.
Messaging refresh (dev-marketing voice, not enterprise):
- Hero: "Spawn cloud agents from your AI" — drop "provider-neutral"
from the lead; it was telling, not selling.
- Frame the value as: local agents plan, the cloud runs the marathon.
- Name the three target consumers up front: Claude Code, OpenClaw,
Hermes. Add a "Supported clients and frameworks" section calling
out that `framework` is a runtime-profile string the worker
consumes — Strands / OpenClaw / Hermes / your own.
- Website: new hero, new "Made for the agents you already ship with"
section with cards for each assistant, new feature cards with
punchier copy ("Real cloud, not your laptop" / "Built for
marathons" / "Always observable" / "Boring defaults"), new
architecture diagram showing the three local assistants feeding the
dispatcher. OG image updated with the same headline.
Files touched:
- brand/logo-mark{,-light}.svg, brand/wordmark{,-dark}.svg
- brand/website/{index.html, styles.css, assets/{favicon,og}.svg}
- brand/profile-readme/profile/{README.md, assets/*}
- README.md (mcp-server root)
Per request, do not ship READMEs for other org packages from this repo. Remove brand/proposed-readmes/ and trim the deployment guide accordingly. Org profile README and the marketing site remain.
The framework field on spawn_cloud_agent and runtime profiles exists and is passed through to the worker (src/index.ts, src/schemas.ts) — but AgentDispatch doesn't interpret it. Whether a given framework string is "supported" depends entirely on what the worker handles. Today the reference worker (worker-agentcore) ships with Strands. Adjust copy accordingly: - README "Supported clients and frameworks" → split into "Supported clients" (Claude Code, OpenClaw, Hermes, etc. — all MCP clients, accurate) and "What the cloud agent runs" (Strands ships today; any other framework works once your worker handles it). - Config example: framework "openclaw" → "strands" (truthful working example). - Architecture step 5 acknowledges only Strands ships today. - Org profile diagram caption: "runs Strands · OpenClaw · Hermes · your framework" → "runs Strands today · your framework next". - worker-agentcore table row: drop the "reference OpenClaw / Hermes workers live here" claim. - Website hero badge: "Strands · OpenClaw · Hermes" → "Strands today · BYO framework". OpenClaw and Hermes stay throughout the docs as **local MCP clients** (the actual use case), which is correct.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce a complete AgentDispatch brand kit under brand/:
(one inbound spoke, glowing core, two outbound spokes to nodes) plus
horizontal wordmark lockups, for use as the org avatar and as the
README hero across every repo.
repo at the org level, with shared brand assets co-located.
store-sqlite, adapter-aws-agentcore, worker-agentcore,
adapter-template, docs) using the same hero, navigation, and tone so
the whole stack reads as one product.
script.js + assets/) ready to drop into GitHub Pages, Netlify, or
Cloudflare Pages. Includes OG image and SVG favicon.
"give your AI assistant a fleet of cloud agents" — referencing the
new wordmark and tying the package to the rest of the stack.
asset (avatar, .github repo, per-repo READMEs, site) since this
session only has write access to mcp-server.