docs: add brand.md and align copy with brand identity

Add ooxml.dev brand.md (strategy, voice, visual layers). Align all
customer-facing copy: README, homepage, MCP page, SEO metadata, docs
intro, llms.txt, and footer. Rename SuperDoc references to
"SuperDoc — DOCX editing and tooling". Update docx-corpus count to 1M+.
Fix theme_color from orange to brand blue (#1355FF).

Author: caio-pizzol

README.md

@@ -8,47 +8,44 @@ The OOXML spec, explained by people who actually implemented it.
 
 ## What is this?
 
-An interactive reference for ECMA-376 (Office Open XML) with:
+An interactive reference for ECMA-376 (Office Open XML) built by the [SuperDoc — DOCX editing and tooling](https://superdoc.dev) team. Every page combines XML structure, live rendered previews, and implementation notes that tell you what the spec doesn't.
 
-- **Live previews** - See XML rendered in real-time with SuperDoc
-- **Implementation notes** - Real-world gotchas from building document processors
-- **Practical examples** - Working code, not just spec excerpts
+- **Live previews** — Edit XML and see it render in real-time. Every example is a working document.
+- **Implementation notes** — Where Word diverges from the spec, what will break your code, and what to do about it.
+- **Semantic spec search** — 18,000+ spec chunks searchable by meaning via MCP server.
 
 ## Why?
 
-The official ECMA-376 spec is 5,000+ pages. Most of it you'll never need. This reference focuses on what matters for building document tools, with insights from implementing [SuperDoc](https://superdoc.dev).
+The ECMA-376 spec is 5,000+ pages and it lies. Word's actual behavior diverges from the standard in ways you only discover by building against it. The knowledge to implement OOXML correctly is locked inside a handful of companies that have no incentive to share it.
 
-## MCP Server ![New](https://img.shields.io/badge/New-blue)
+We faced this at SuperDoc — building a document engine on native OOXML with no roadmap beyond an unreliable spec. We wrote down everything we learned and made it public. No one should have to reverse-engineer Word alone.
 
-**The world's first ECMA-376 MCP server.** Ask Claude about OOXML and get answers grounded in the actual spec.
+## MCP Server
+
+Search the ECMA-376 spec with AI. Ask questions in natural language, get answers grounded in the actual specification.
 
 ```bash
 claude mcp add --transport http ecma-spec https://api.ooxml.dev/mcp
 ```
 
-Example: *"How do I set paragraph spacing in WordprocessingML?"* - Claude searches 18,000+ spec chunks and returns the relevant sections.
+Works with Claude Code, Cursor, and any MCP-compatible client. Three tools: `search_ecma_spec` (semantic search), `get_section` (by ID), and `list_parts` (browse structure).
 
 ## Development
 
 ```bash
-# Install dependencies
-bun install
-
-# Start dev server
-bun dev
-
-# Build for production
-bun run build
+bun install    # Install dependencies
+bun dev        # Dev server at http://localhost:5173
+bun run build  # Production build
 ```
 
 ## Contributing
 
-Contributions welcome! Add implementation notes, fix examples, or improve docs.
+Contributions welcome. Add implementation notes, fix examples, or improve the reference.
 
 ## License
 
 MIT
 
 ---
 
-Built by 🦋[SuperDoc](https://superdoc.dev)
+Built by 🦋 [SuperDoc — DOCX editing and tooling](https://superdoc.dev)

apps/web/public/llms.txt

@@ -2,38 +2,41 @@
 
 > The OOXML spec, explained by people who actually implemented it.
 
-ooxml.dev is an interactive reference for ECMA-376 (Office Open XML), the standard behind .docx, .xlsx, and .pptx files. It features live previews, real-world implementation gotchas, and semantic spec search. Built by the SuperDoc team (https://www.superdoc.dev).
+ooxml.dev is the interactive reference for ECMA-376 (Office Open XML) — the standard behind .docx, .xlsx, and .pptx files. Built by SuperDoc — DOCX editing and tooling (https://superdoc.dev) from experience implementing a full OOXML document engine.
+
+Every page combines XML structure, live rendered previews, and implementation notes that tell you what the spec doesn't: where Word diverges from the standard, what will break your code, and what to do about it.
 
 ## Main Pages
 
 - [Home](https://ooxml.dev/): Overview and entry point
-- [Docs](https://ooxml.dev/docs/): Interactive OOXML reference documentation
-- [MCP Server](https://ooxml.dev/mcp/): Connect AI assistants to search 18,000+ ECMA-376 specification chunks via MCP
-- [Spec Explorer](https://ooxml.dev/spec/): Search and browse the ECMA-376 specification with semantic search
+- [Reference](https://ooxml.dev/docs/): Interactive OOXML reference with live previews and implementation notes
+- [Spec Explorer](https://ooxml.dev/spec/): Semantic search across the full ECMA-376 specification
+- [MCP Server](https://ooxml.dev/mcp/): Search 18,000+ spec chunks with AI via MCP
 
 ## Documentation
 
 ### Getting Started
-- [Introduction](https://ooxml.dev/docs/): Learn the basics of OOXML and how to use this reference
+- [Introduction](https://ooxml.dev/docs/): OOXML structure, namespaces, and how to use this reference
 
 ### WordprocessingML
 - [Paragraphs](https://ooxml.dev/docs/paragraphs/): Text structure and formatting — paragraphs, runs, and text elements (w:p)
 - [Paragraph Borders](https://ooxml.dev/docs/paragraph-borders/): Border properties, between-border groups, nil/none semantics (w:pBdr)
+- [Bidirectional Text](https://ooxml.dev/docs/bidirectional-text/): RTL layout, logical alignment, tab stop flipping, and bidi pitfalls
 - [Tables](https://ooxml.dev/docs/tables/): Table structure, properties, and implementation gotchas (w:tbl)
 - [Styles](https://ooxml.dev/docs/styles/): Style definitions, inheritance, and resolution (styles.xml)
 
 ### Guides
-- [Creating Documents](https://ooxml.dev/docs/creating-documents/): Step-by-step guide to creating a valid OOXML document from scratch
+- [Creating Documents](https://ooxml.dev/docs/creating-documents/): Building a valid OOXML document from scratch
 - [Common Gotchas](https://ooxml.dev/docs/common-gotchas/): Real-world implementation issues and how to solve them
 
 ## MCP Server
 
-The ooxml.dev MCP server provides AI assistants with access to the ECMA-376 specification. Available tools:
+Search the ECMA-376 spec with AI. 18,000+ spec chunks, searchable by meaning.
 
-- `search_ecma_spec`: Semantic search across 18,000+ specification chunks
-- `get_section`: Retrieve a specific section by ID (e.g., "17.3.2" for paragraph properties)
+- `search_ecma_spec`: Semantic search — ask questions in natural language
+- `get_section`: Retrieve a specific section by ID (e.g., "17.3.2")
 - `list_parts`: Browse the specification structure by part (1-4)
 
 ## About
 
-ooxml.dev is built and maintained by the SuperDoc team (https://www.superdoc.dev). SuperDoc is a document engine that implements the OOXML specification. The content on ooxml.dev comes from real-world experience building a full OOXML document engine.
+ooxml.dev is built by SuperDoc — DOCX editing and tooling (https://superdoc.dev). SuperDoc is a document engine that renders OOXML natively in the browser. The implementation notes on ooxml.dev come from building that engine against thousands of real-world documents.

apps/web/public/site.webmanifest

@@ -1,12 +1,12 @@
 {
 	"name": "ooxml.dev",
 	"short_name": "ooxml.dev",
-	"description": "The Implementer's Guide to OOXML",
+	"description": "The OOXML spec, explained by people who actually implemented it.",
 	"icons": [
 		{ "src": "/android-chrome-192x192.png", "sizes": "192x192", "type": "image/png" },
 		{ "src": "/android-chrome-512x512.png", "sizes": "512x512", "type": "image/png" }
 	],
-	"theme_color": "#ea580c",
+	"theme_color": "#1355FF",
 	"background_color": "#ffffff",
 	"display": "standalone"
 }

apps/web/scripts/prerender.ts

@@ -180,7 +180,7 @@ function buildHead(path: string): string {
 			headline: seo.title.split(" | ")[0].split(" — ")[0],
 			description: seo.description,
 			url,
-			author: { "@type": "Organization", name: "SuperDoc", url: "https://superdoc.dev" },
+			author: { "@type": "Organization", name: "SuperDoc — DOCX editing and tooling", url: "https://superdoc.dev" },
 			publisher: { "@type": "Organization", name: "ooxml.dev" },
 			about: {
 				"@type": "Thing",

apps/web/src/components/Footer.tsx

@@ -6,7 +6,7 @@ export function Footer() {
 				href="https://superdoc.dev/?utm_source=ooxml.dev&utm_medium=referral&utm_campaign=footer"
 				className="text-[var(--color-accent)] hover:underline"
 			>
-				SuperDoc
+				SuperDoc — DOCX editing and tooling
 			</a>
 		</footer>
 	);

apps/web/src/data/docs.ts

@@ -22,7 +22,7 @@ type ContentBlock =
 export const docs: Record<string, DocPage> = {
 	index: {
 		title: "Getting Started",
-		description: "Learn the basics of OOXML (Office Open XML) and how to use this reference.",
+		description: "OOXML structure, namespaces, and how to use this reference.",
 		content: [
 			{
 				type: "note",
@@ -33,7 +33,7 @@ export const docs: Record<string, DocPage> = {
 			{ type: "heading", level: 2, text: "What's Different Here" },
 			{
 				type: "paragraph",
-				text: "Unlike the official spec, this reference shows live previews, includes real implementation notes from building [SuperDoc](https://superdoc.dev/?utm_source=ooxml.dev&utm_medium=referral&utm_campaign=docs), and links to 100k+ real documents from [docx-corpus](https://docxcorp.us).",
+				text: "The official spec is 5,000+ pages and omits critical rendering details. This reference fills the gap: live previews, implementation notes from building [SuperDoc — DOCX editing and tooling](https://superdoc.dev/?utm_source=ooxml.dev&utm_medium=referral&utm_campaign=docs), and links to 1M+ real documents from [docx-corpus](https://docxcorp.us). Every note comes from shipping code, not reading the spec.",
 			},
 			{ type: "heading", level: 2, text: "OOXML Structure" },
 			{
@@ -764,7 +764,7 @@ w:rPr (run properties)
 		content: [
 			{
 				type: "paragraph",
-				text: "Lessons learned from building [SuperDoc](https://superdoc.dev/?utm_source=ooxml.dev&utm_medium=referral&utm_campaign=docs).",
+				text: "Lessons learned from building [SuperDoc — DOCX editing and tooling](https://superdoc.dev/?utm_source=ooxml.dev&utm_medium=referral&utm_campaign=docs).",
 			},
 			{ type: "heading", level: 2, text: "Word-Specific Issues" },
 			{

apps/web/src/data/seo.ts

@@ -8,27 +8,27 @@ export interface SeoMeta {
 
 const staticPages: Record<string, SeoMeta> = {
 	"/": {
-		title: "ooxml.dev — The Implementer's Guide to OOXML (ECMA-376)",
+		title: "ooxml.dev — The OOXML spec, explained by people who actually implemented it",
 		description:
-			"Interactive OOXML reference with live previews, implementation notes, and real-world gotchas. Built by the SuperDoc team.",
+			"Interactive ECMA-376 reference with live previews, implementation notes, and what the spec doesn't tell you. Built by SuperDoc — DOCX editing and tooling.",
 		type: "website",
 	},
 	"/mcp": {
 		title: "ECMA-376 MCP Server — Search the OOXML Spec with AI | ooxml.dev",
 		description:
-			"Connect your AI assistant to search 18,000+ OOXML specification chunks. Works with Claude Code, Cursor, and any MCP-compatible client.",
+			"Search 18,000+ OOXML spec chunks with natural language. Works with Claude Code, Cursor, and any MCP-compatible client.",
 		type: "website",
 	},
 	"/spec": {
-		title: "ECMA-376 Spec Explorer | ooxml.dev",
+		title: "ECMA-376 Spec Explorer — Search and Browse | ooxml.dev",
 		description:
-			"Search and browse the ECMA-376 Office Open XML specification with semantic search and PDF viewer.",
+			"Semantic search across the full ECMA-376 Office Open XML specification. Find sections by meaning, not just keywords.",
 		type: "website",
 	},
 	"/docs": {
 		title: "OOXML Reference — Getting Started | ooxml.dev",
 		description:
-			"Learn the basics of OOXML (Office Open XML) and how to use this interactive reference.",
+			"OOXML structure, namespaces, and how to use this reference. Live previews and implementation notes from building a real document engine.",
 		type: "article",
 	},
 };

apps/web/src/pages/Home.tsx

@@ -18,7 +18,7 @@ export function Home() {
 					The OOXML spec, explained by people who actually implemented it.
 					<br className="hidden sm:block" />
 					<span className="sm:hidden"> </span>
-					Interactive examples, real-world gotchas, live previews, and semantic spec search.
+					Live previews, implementation notes, and what the spec doesn't tell you.
 				</p>
 				<div className="flex justify-center gap-4 mb-6">
 					<Link

apps/web/src/pages/Mcp.tsx

@@ -62,8 +62,8 @@ export function Mcp() {
 					</div>
 					<h1 className="text-3xl font-bold mb-4">Search the ECMA-376 spec with AI</h1>
 					<p className="text-[var(--color-text-secondary)] max-w-xl mx-auto">
-						Connect your MCP-compatible client to search 18,000+ specification chunks using natural
-						language queries.
+						18,000+ spec chunks, searchable by meaning. Ask questions in natural language, get the
+						relevant sections back.
 					</p>
 				</div>
 
@@ -233,7 +233,7 @@ export function Mcp() {
 							rel="noopener noreferrer"
 							className="text-[var(--color-accent)] hover:underline"
 						>
-							SuperDoc
+							SuperDoc — DOCX editing and tooling
 						</a>
 					</span>
 					<Link