Remove H1 headers from multiple documentation files and delete the associated script

hotlong · hotlong · commit 2973586b96a9 · 2026-01-19T13:12:11.000+08:00
diff --git a/content/docs/concepts/ai-codex.mdx b/content/docs/concepts/ai-codex.mdx
@@ -3,7 +3,6 @@ title: The AI Codex
 description: Best practices for AI-assisted ObjectStack development
 ---
 
-# The AI Codex
 
 This guide helps developers leverage AI tools to enhance ObjectStack development efficiency.
 
diff --git a/content/docs/concepts/architecture.mdx b/content/docs/concepts/architecture.mdx
@@ -3,7 +3,6 @@ title: Architecture Overview
 description: Understanding the ObjectStack Trinity. How ObjectQL, ObjectOS, and ObjectUI collaborate to build the Enterprise Kernel.
 ---
 
-# Architecture Overview
 
 ObjectStack is not a monolithic framework. It is a composable ecosystem designed around a **Layered Architecture**. We call this the **"ObjectStack Trinity."**
 
diff --git a/content/docs/concepts/core-values.mdx b/content/docs/concepts/core-values.mdx
@@ -3,7 +3,6 @@ title: Core Values
 description: "Deep dive into the three pillars of ObjectStack: Protocol-Driven Architecture, Local-First Data Sovereignty, and Database Agnosticism."
 ---
 
-# Core Values
 
 ObjectStack is built upon three non-negotiable architectural values. These are not just "features"; they are the constraints that guide every design decision we make.
 
diff --git a/content/docs/concepts/enterprise-patterns.mdx b/content/docs/concepts/enterprise-patterns.mdx
@@ -3,7 +3,6 @@ title: Enterprise Patterns
 description: Handling complex ERP/CRM business logic (State Machines, Calculations, RBAC) using the Protocol-Driven approach.
 ---
 
-# Enterprise Patterns
 
 A common misconception about "Low-Code" or "Protocol-Driven" platforms is that they are only suitable for simple CRUD applications.
 
diff --git a/content/docs/concepts/manifesto.mdx b/content/docs/concepts/manifesto.mdx
@@ -3,7 +3,6 @@ title: The ObjectStack Manifesto
 description: The unshakable core principles that govern ObjectStack's existence and evolution
 ---
 
-# The ObjectStack Manifesto
 
 ObjectStack exists to return data application development to its essence. To maintain a healthy and open ecosystem, we pledge to uphold the following unshakable core principles:
 
diff --git a/content/docs/concepts/terminology.mdx b/content/docs/concepts/terminology.mdx
@@ -3,7 +3,6 @@ title: Terminology
 description: A glossary of key terms, concepts, and jargon used within the ObjectStack ecosystem.
 ---
 
-# Terminology
 
 To navigate the ObjectStack ecosystem effectively, it is helpful to understand the specific vocabulary we use. While many terms are standard in computer science, some have specific nuances in our "Protocol-Driven" context.
 
diff --git a/content/docs/index.mdx b/content/docs/index.mdx
@@ -5,7 +5,6 @@ description: The Standard for Post-SaaS Operating Systems
 
 import { FileText, Database, Layout, Settings, Book } from 'lucide-react';
 
-# ObjectStack Protocol
 
 **ObjectStack Protocol** is the "DNA" and constitution of the ObjectStack platform. It defines the metadata standards, schemas, and runtime behaviors that power a metadata-driven, low-code operating system.
 
diff --git a/content/docs/specifications/data/advanced-types.mdx b/content/docs/specifications/data/advanced-types.mdx
@@ -3,7 +3,6 @@ title: Advanced Types
 description: "Deep dive into Enterprise Data Types: Currency, Lookup, Formulas, and Summaries."
 ---
 
-# Advanced Enterprise Types
 
 While basic types like `text` and `boolean` handle standard data, Enterprise applications require specialized types to handle money, relationships, and on-the-fly calculations.
 
diff --git a/content/docs/specifications/data/analytics-protocol.mdx b/content/docs/specifications/data/analytics-protocol.mdx
@@ -3,7 +3,6 @@ title: Analytics Protocol
 description: Defining Aggregations, Pivot Tables, and BI Data Sources using the ObjectQL Protocol.
 ---
 
-# Analytics Protocol
 
 In traditional architectures, generating reports usually requires exporting data to a Data Warehouse or writing complex, non-portable SQL queries.
 
diff --git a/content/docs/specifications/data/ast-structure.mdx b/content/docs/specifications/data/ast-structure.mdx
@@ -3,7 +3,6 @@ title: The Core AST
 description: Understanding the Abstract Syntax Tree (AST) that powers the ObjectQL Protocol.
 ---
 
-# The Abstract Syntax Tree (AST)
 
 ObjectQL is not just a URL query parameter parser. It is a **Database Compiler**.
 
diff --git a/content/docs/specifications/data/index.mdx b/content/docs/specifications/data/index.mdx
@@ -3,7 +3,6 @@ title: ObjectQL Overview
 description: Introduction to the Data Protocol. Understanding the Database Compiler architecture and the Abstract Syntax Tree (AST).
 ---
 
-# ObjectQL Data Protocol
 
 **ObjectQL** is a database-agnostic protocol for defining, querying, and manipulating enterprise data.
 
diff --git a/content/docs/specifications/data/schema-definition.mdx b/content/docs/specifications/data/schema-definition.mdx
@@ -3,7 +3,6 @@ title: Schema Definition
 description: The core of ObjectQL. How to define Objects, Fields, and Relationships using declarative YAML protocols.
 ---
 
-# Schema Definition
 
 In ObjectQL, you do not write `CREATE TABLE` statements, nor do you define Mongoose Schemas or TypeORM Classes. Instead, you define **Objects** using a standard YAML (or JSON) protocol.
 
diff --git a/content/docs/specifications/data/transaction-model.mdx b/content/docs/specifications/data/transaction-model.mdx
@@ -5,7 +5,6 @@ sidebar_position: 5
 slug: /objectql/transaction-model
 ---
 
-# Transaction Model & Atomicity
 
 In Enterprise applications, data integrity is non-negotiable. A classic example is saving an **Order** and its **Line Items**. You cannot have an Order created without its Items, nor can you deduct inventory if the Order fails to save.
 
diff --git a/content/docs/specifications/data/wire-protocol.mdx b/content/docs/specifications/data/wire-protocol.mdx
@@ -3,7 +3,6 @@ title: Wire Protocol
 description: The HTTP/WebSocket transport specification. Request envelopes, Response formats, and Error handling standards.
 ---
 
-# Wire Protocol
 
 The **Wire Protocol** defines how ObjectQL ASTs and Mutations are serialized and transmitted over the network.
 
diff --git a/content/docs/specifications/index.mdx b/content/docs/specifications/index.mdx
@@ -3,7 +3,6 @@ title: Specifications Overview
 description: The authoritative guide to the ObjectStack protocols. Understanding the philosophy of "Intent over Implementation".
 ---
 
-# Specifications Overview
 
 > "We shape our tools and thereafter our tools shape us." — Marshall McLuhan
 
diff --git a/content/docs/specifications/server/audit-compliance.mdx b/content/docs/specifications/server/audit-compliance.mdx
@@ -3,7 +3,6 @@ title: Audit & Compliance
 description: The Protocol for Accountability. Field History Tracking, System Audit Trails, and Data Retention Policies.
 ---
 
-# Audit & Compliance
 
 In the enterprise world, "Who changed this?" is the most expensive question to leave unanswered.
 
diff --git a/content/docs/specifications/server/automation-rules.mdx b/content/docs/specifications/server/automation-rules.mdx
@@ -3,7 +3,6 @@ title: Automation Rules
 description: The Protocol for Server-Side Logic. Database Triggers, Scheduled Jobs, and No-Code Automation Flows.
 ---
 
-# Automation Rules
 
 While Workflows guide a record through a lifecycle, **Automation Rules** handle the immediate logic and side effects of data changes.
 
diff --git a/content/docs/specifications/server/index.mdx b/content/docs/specifications/server/index.mdx
@@ -3,7 +3,6 @@ title: ObjectOS Overview
 description: Introduction to the Business Operating System. The Kernel for Identity, Synchronization, and Orchestration.
 ---
 
-# ObjectOS Protocol
 
 **ObjectOS** is the runtime **Kernel** of the ObjectStack ecosystem.
 
diff --git a/content/docs/specifications/server/integration-etl.mdx b/content/docs/specifications/server/integration-etl.mdx
@@ -3,7 +3,6 @@ title: Integration & ETL
 description: The Protocol for Connectivity. Data Import/Export, Virtual Objects (External Data Sources), and API Mapping Standards.
 ---
 
-# Integration & ETL
 
 No enterprise application is an island. It must ingest CSVs from suppliers, sync orders to SAP, and pull lead data from LinkedIn.
 
diff --git a/content/docs/specifications/server/permission-governance.mdx b/content/docs/specifications/server/permission-governance.mdx
@@ -5,7 +5,6 @@ sidebar_position: 3
 slug: /objectos/permission-governance
 ---
 
-# Permission & Governance
 
 In ObjectStack, security is not implemented in API Controllers or UI logic. It is **Injected by the Kernel**.
 
diff --git a/content/docs/specifications/server/plugin-manifest.mdx b/content/docs/specifications/server/plugin-manifest.mdx
@@ -3,7 +3,6 @@ title: Plugin Manifest
 description: The specification for packaging capabilities. Manifest structure, Lifecycle hooks, and Dependency management.
 ---
 
-# Plugin Manifest
 
 ObjectOS follows a **Micro-Kernel Architecture**. The Core Engine is minimal, providing only the basic runtime (Auth, DB Driver, HTTP Server).
 
diff --git a/content/docs/specifications/server/workflow-engine.mdx b/content/docs/specifications/server/workflow-engine.mdx
@@ -3,7 +3,6 @@ title: Workflow Engine
 description: The Protocol for Business Process Management (BPM). State Machines, Approval Chains, and BPMN Mapping.
 ---
 
-# Workflow Engine
 
 The **ObjectOS Workflow Engine** is a deterministic state machine that governs the lifecycle of business objects.
 
diff --git a/content/docs/specifications/ui/action-triggers.mdx b/content/docs/specifications/ui/action-triggers.mdx
@@ -3,7 +3,6 @@ title: Action Triggers
 description: The client-side interaction protocol. Handling clicks, navigation, and API calls via JSON events.
 ---
 
-# Action Triggers
 
 In ObjectUI, interactivity is defined by **Actions**, not functions.
 
diff --git a/content/docs/specifications/ui/component-schema.mdx b/content/docs/specifications/ui/component-schema.mdx
@@ -3,7 +3,6 @@ title: Basic Components
 description: "The JSON Schema specification for atomic form elements: Input, Select, and DatePicker."
 ---
 
-# Basic Component Schema
 
 In ObjectUI, every form element is a **Leaf Node** in the render tree. These nodes map directly to **Shadcn UI** primitives, ensuring accessibility and a modern aesthetic.
 
diff --git a/content/docs/specifications/ui/index.mdx b/content/docs/specifications/ui/index.mdx
@@ -3,7 +3,6 @@ title: Overview
 description: Introduction to the Server-Driven UI (SDUI) Protocol. Treating User Interfaces as Data.
 ---
 
-# ObjectUI Protocol
 
 **ObjectUI** is a standard protocol for describing User Interfaces as **JSON Data**.
 
diff --git a/content/docs/specifications/ui/layout-system.mdx b/content/docs/specifications/ui/layout-system.mdx
@@ -3,7 +3,6 @@ title: Layout System
 description: Building complex application structures with Stack, Grid, Tabs, Wizard, and Master-Detail layouts.
 ---
 
-# Layout System
 
 In ObjectUI, layouts are **Recursive Containers**. A layout component doesn't hold data itself; it holds other components (`children`) and defines how they are arranged spatially.
 
diff --git a/content/docs/specifications/ui/report-template.mdx b/content/docs/specifications/ui/report-template.mdx
@@ -3,7 +3,6 @@ title: Report & PDF Protocol
 description: The specification for generating pixel-perfect printable documents (Invoices, Contracts) using HTML/CSS templates.
 ---
 
-# Report & PDF Protocol
 
 In Enterprise software, the ability to generate **Pixel-Perfect Documents**—Invoices, Packing Slips, Contracts, and Purchase Orders—is critical.
 
diff --git a/content/docs/specifications/ui/view-protocol.mdx b/content/docs/specifications/ui/view-protocol.mdx
@@ -3,7 +3,6 @@ title: Complex View Protocol
 description: "The specification for high-density collection views: Data Grid, Kanban, Gantt, and Calendar."
 ---
 
-# Complex View Protocol
 
 While Basic Components deal with a single field, **Views** deal with **Collections** of records.
 
diff --git a/scripts/remove-h1.js b/scripts/remove-h1.js

Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,6 @@ description: The Standard for Post-SaaS Operating Systems`
`5`	`5`
`6`	`6`	`import { FileText, Database, Layout, Settings, Book } from 'lucide-react';`
`7`	`7`
`8`		`-# ObjectStack Protocol`
`9`	`8`
`10`	`9`	`ObjectStack Protocol is the "DNA" and constitution of the ObjectStack platform. It defines the metadata standards, schemas, and runtime behaviors that power a metadata-driven, low-code operating system.`
`11`	`10`