refactor(docs): remove section headers from multiple protocol documentation files for improved readability

hotlong · hotlong · commit bc8e1ad10a33 · 2026-02-04T19:10:48.000+08:00
diff --git a/content/docs/objectql/query-syntax.mdx b/content/docs/objectql/query-syntax.mdx
@@ -5,7 +5,6 @@ description: Database-agnostic query language with filters, joins, aggregations,
 
 import { Search, Filter, GitMerge, BarChart } from 'lucide-react';
 
-# ObjectQL Query Syntax
 
 ObjectQL queries are expressed as **Abstract Syntax Trees (AST)** in JSON format. This enables database-agnostic querying—write once, compile to PostgreSQL, MongoDB, Redis, or any supported driver.
 
diff --git a/content/docs/objectql/schema.mdx b/content/docs/objectql/schema.mdx
@@ -5,8 +5,6 @@ description: The complete specification for defining objects, fields, and relati
 
 import { FileCode, Database, Layers, Package } from 'lucide-react';
 
-# Schema Definition
-
 In ObjectStack, **data structure is configuration, not code**. The Schema Definition Protocol governs how you declare your data model using declarative `.object.yml` files.
 
 > **Single Source of Truth:** This schema drives database DDL, API generation, UI form layouts, permission scopes, and validation rules.
diff --git a/content/docs/objectql/types.mdx b/content/docs/objectql/types.mdx
@@ -5,7 +5,6 @@ description: Complete reference for ObjectQL field types - Scalars, relationship
 
 import { Type, Link, Calculator, Database } from 'lucide-react';
 
-# ObjectQL Type System
 
 ObjectQL provides **20+ specialized field types** that encode business semantics, not just data storage primitives. Each type understands its purpose and automatically configures database schemas, UI renderers, validation rules, and API serialization.
 
diff --git a/content/docs/objectui/actions.mdx b/content/docs/objectui/actions.mdx
@@ -5,7 +5,6 @@ description: Buttons, triggers, navigation, and user interaction definitions
 
 import { MousePointer, Zap, ExternalLink, Workflow, GitBranch, Play, Component, Layout } from 'lucide-react';
 
-# Action Protocol: Defining User Interactions
 
 The **Action Protocol** specifies how user interactions (button clicks, menu selections, gestures) trigger business logic, navigation, or external integrations. Actions are the "verbs" of ObjectUI—they make things happen.
 
diff --git a/content/docs/objectui/concept.mdx b/content/docs/objectui/concept.mdx
@@ -5,7 +5,6 @@ description: The philosophy and architecture of metadata-driven user interfaces
 
 import { Blocks, Code, Zap, Users, Globe, Shield, Sparkles, Workflow } from 'lucide-react';
 
-# UI as Data: The ObjectUI Philosophy
 
 **Core Thesis:** User interfaces are **configuration, not code**. Forms, dashboards, and reports should be defined in declarative metadata (JSON/YAML), not imperative JavaScript.
 
diff --git a/content/docs/objectui/layout-dsl.mdx b/content/docs/objectui/layout-dsl.mdx
@@ -5,7 +5,6 @@ description: Declarative layout description language for pages, sections, and re
 
 import { Layout, Grid, Columns, Box, Monitor, Smartphone, Tablet, MousePointer } from 'lucide-react';
 
-# Layout DSL: Composing User Interfaces
 
 The **Layout DSL** (Domain-Specific Language) is ObjectUI's declarative syntax for defining page structure, sections, and responsive grids. It abstracts away CSS Grid, Flexbox, and platform-specific layout engines.
 
diff --git a/content/docs/objectui/widget-contract.mdx b/content/docs/objectui/widget-contract.mdx
@@ -5,7 +5,6 @@ description: Standard props, events, and lifecycle for ObjectUI components
 
 import { Component, Zap, Code, Check, AlertCircle, Globe } from 'lucide-react';
 
-# Widget Contract: Component Specification
 
 The **Widget Contract** defines the standard interface that all ObjectUI components must implement. This contract ensures consistency across renderers and enables components to be composed, configured, and extended predictably.
 
diff --git a/content/docs/references/auth/index.mdx b/content/docs/references/auth/index.mdx
@@ -3,7 +3,6 @@ title: Auth Protocol Overview
 description: Complete reference for all auth protocol schemas
 ---
 
-# Auth Protocol
 
 This section contains all protocol schemas for the auth layer of ObjectStack.
 
diff --git a/content/docs/references/data/validation.mdx b/content/docs/references/data/validation.mdx
@@ -1,10 +1,8 @@
 ---
-title: Validation
+title: Validation Protocol
 description: Validation protocol schemas
 ---
 
-# ObjectStack Validation Protocol
-
 This module defines the validation schema protocol for ObjectStack, providing a comprehensive
 
 type-safe validation system similar to Salesforce's validation rules but with enhanced capabilities.
diff --git a/content/docs/references/protocol-map.mdx b/content/docs/references/protocol-map.mdx
@@ -4,7 +4,6 @@ description: Visual guide to ObjectStack protocol relationships and dependencies
 ---
 
 
-# Protocol Architecture Map
 
 Understand how the 123 ObjectStack protocols fit together to form a complete business platform.
 

Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,6 @@ description: Database-agnostic query language with filters, joins, aggregations,`
`5`	`5`
`6`	`6`	`import { Search, Filter, GitMerge, BarChart } from 'lucide-react';`
`7`	`7`
`8`		`-# ObjectQL Query Syntax`
`9`	`8`
`10`	`9`	`ObjectQL queries are expressed as Abstract Syntax Trees (AST) in JSON format. This enables database-agnostic querying—write once, compile to PostgreSQL, MongoDB, Redis, or any supported driver.`
`11`	`10`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,6 @@ description: Complete reference for ObjectQL field types - Scalars, relationship`
`5`	`5`
`6`	`6`	`import { Type, Link, Calculator, Database } from 'lucide-react';`
`7`	`7`
`8`		`-# ObjectQL Type System`
`9`	`8`
`10`	`9`	`ObjectQL provides 20+ specialized field types that encode business semantics, not just data storage primitives. Each type understands its purpose and automatically configures database schemas, UI renderers, validation rules, and API serialization.`
`11`	`10`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,6 @@ description: Buttons, triggers, navigation, and user interaction definitions`
`5`	`5`
`6`	`6`	`import { MousePointer, Zap, ExternalLink, Workflow, GitBranch, Play, Component, Layout } from 'lucide-react';`
`7`	`7`
`8`		`-# Action Protocol: Defining User Interactions`
`9`	`8`
`10`	`9`	`The Action Protocol specifies how user interactions (button clicks, menu selections, gestures) trigger business logic, navigation, or external integrations. Actions are the "verbs" of ObjectUI—they make things happen.`
`11`	`10`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,6 @@ description: The philosophy and architecture of metadata-driven user interfaces`
`5`	`5`
`6`	`6`	`import { Blocks, Code, Zap, Users, Globe, Shield, Sparkles, Workflow } from 'lucide-react';`
`7`	`7`
`8`		`-# UI as Data: The ObjectUI Philosophy`
`9`	`8`
`10`	`9`	`Core Thesis: User interfaces are configuration, not code. Forms, dashboards, and reports should be defined in declarative metadata (JSON/YAML), not imperative JavaScript.`
`11`	`10`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,6 @@ description: Declarative layout description language for pages, sections, and re`
`5`	`5`
`6`	`6`	`import { Layout, Grid, Columns, Box, Monitor, Smartphone, Tablet, MousePointer } from 'lucide-react';`
`7`	`7`
`8`		`-# Layout DSL: Composing User Interfaces`
`9`	`8`
`10`	`9`	`The Layout DSL (Domain-Specific Language) is ObjectUI's declarative syntax for defining page structure, sections, and responsive grids. It abstracts away CSS Grid, Flexbox, and platform-specific layout engines.`
`11`	`10`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,6 @@ description: Standard props, events, and lifecycle for ObjectUI components`
`5`	`5`
`6`	`6`	`import { Component, Zap, Code, Check, AlertCircle, Globe } from 'lucide-react';`
`7`	`7`
`8`		`-# Widget Contract: Component Specification`
`9`	`8`
`10`	`9`	`The Widget Contract defines the standard interface that all ObjectUI components must implement. This contract ensures consistency across renderers and enables components to be composed, configured, and extended predictably.`
`11`	`10`
Original file line number	Diff line number	Diff line change
`@@ -4,7 +4,6 @@ description: Visual guide to ObjectStack protocol relationships and dependencies`
`4`	`4`	`---`
`5`	`5`
`6`	`6`
`7`		`-# Protocol Architecture Map`
`8`	`7`
`9`	`8`	`Understand how the 123 ObjectStack protocols fit together to form a complete business platform.`
`10`	`9`