docs: remove duplicate H1 where frontmatter title already sets it

This commit is contained in:
Vincent Koc
2026-04-23 13:11:14 -07:00
parent 219a11d2bd
commit 4a2cd533ac
251 changed files with 1 additions and 503 deletions

View File

@@ -8,8 +8,6 @@ title: "Agent Bootstrapping"
sidebarTitle: "Bootstrapping"
---
# Agent Bootstrapping
Bootstrapping is the **firstrun** ritual that prepares an agent workspace and
collects identity details. It happens after onboarding, when the agent starts
for the first time.

View File

@@ -5,8 +5,6 @@ read_when:
title: "Docs directory"
---
# Docs Directory
<Note>
This page is a curated index. If you are new, start with [Getting Started](/start/getting-started).
For a complete map of the docs, see [Docs hubs](/start/hubs).

View File

@@ -6,8 +6,6 @@ read_when:
title: "Getting Started"
---
# Getting Started
Install OpenClaw, run onboarding, and chat with your AI assistant — all in
about 5 minutes. By the end you will have a running Gateway, configured auth,
and a working chat session.

View File

@@ -5,8 +5,6 @@ read_when:
title: "Docs Hubs"
---
# Docs hubs
<Note>
If you are new to OpenClaw, start with [Getting Started](/start/getting-started).
</Note>

View File

@@ -7,8 +7,6 @@ title: "Onboarding Overview"
sidebarTitle: "Onboarding Overview"
---
# Onboarding Overview
OpenClaw has two onboarding paths. Both configure auth, the Gateway, and
optional chat channels — they just differ in how you interact with the setup.

View File

@@ -7,8 +7,6 @@ title: "Onboarding (macOS App)"
sidebarTitle: "Onboarding: macOS App"
---
# Onboarding (macOS App)
This doc describes the **current** firstrun setup flow. The goal is a
smooth “day 0” experience: pick where the Gateway runs, connect auth, run the
wizard, and let the agent bootstrap itself.

View File

@@ -6,8 +6,6 @@ read_when:
title: "Quick start"
---
# Quick start
<Info>
Quick start is now part of [Getting Started](/start/getting-started).
</Info>

View File

@@ -6,8 +6,6 @@ read_when:
title: "Setup"
---
# Setup
<Note>
If you are setting up for the first time, start with [Getting Started](/start/getting-started).
For onboarding details, see [Onboarding (CLI)](/start/wizard).

View File

@@ -7,8 +7,6 @@ read_when:
- Updating community project highlights
---
# Showcase
OpenClaw projects are not toy demos. People are shipping PR review loops, mobile apps, home automation, voice systems, devtools, and memory-heavy workflows from the channels they already use — chat-native builds on Telegram, WhatsApp, Discord, and terminals; real automation for booking, shopping, and support without waiting for an API; and physical-world integrations with printers, vacuums, cameras, and home systems.
<Info>

View File

@@ -7,8 +7,6 @@ title: "CLI Automation"
sidebarTitle: "CLI automation"
---
# CLI Automation
Use `--non-interactive` to automate `openclaw onboard`.
<Note>

View File

@@ -7,8 +7,6 @@ title: "CLI Setup Reference"
sidebarTitle: "CLI reference"
---
# CLI Setup Reference
This page is the full reference for `openclaw onboard`.
For the short guide, see [Onboarding (CLI)](/start/wizard).

View File

@@ -7,8 +7,6 @@ title: "Onboarding (CLI)"
sidebarTitle: "Onboarding: CLI"
---
# Onboarding (CLI)
CLI onboarding is the **recommended** way to set up OpenClaw on macOS,
Linux, or Windows (via WSL2; strongly recommended).
It configures a local Gateway or a remote Gateway connection, plus channels, skills,