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

@@ -3,6 +3,4 @@ summary: "Redirect to /gateway/authentication"
title: "Auth Monitoring"
---
# Auth Monitoring
This page moved to [Authentication](/gateway/authentication). See [Authentication](/gateway/authentication) for auth monitoring documentation.

View File

@@ -3,6 +3,4 @@ summary: "Redirect to Task Flow"
title: "ClawFlow"
---
# ClawFlow
ClawFlow was renamed to [Task Flow](/automation/taskflow). See [Task Flow](/automation/taskflow) for the current documentation.

View File

@@ -3,6 +3,4 @@ summary: "Redirect to /automation"
title: "Cron vs Heartbeat"
---
# Cron vs Heartbeat
This page moved to [Automation & Tasks](/automation). See [Automation & Tasks](/automation) for the decision guide comparing cron and heartbeat.

View File

@@ -3,6 +3,4 @@ summary: "Redirect to /automation/cron-jobs"
title: "Gmail PubSub"
---
# Gmail PubSub
This page moved to [Scheduled Tasks](/automation/cron-jobs#gmail-pubsub-integration). See [Scheduled Tasks](/automation/cron-jobs#gmail-pubsub-integration) for Gmail PubSub documentation.

View File

@@ -6,8 +6,6 @@ read_when:
title: "Hooks"
---
# Hooks
Hooks are small scripts that run when something happens inside the Gateway. They can be discovered from directories and inspected with `openclaw hooks`. The Gateway loads internal hooks only after you enable hooks or configure at least one hook entry, hook pack, legacy handler, or extra hook directory.
There are two kinds of hooks in OpenClaw:

View File

@@ -7,8 +7,6 @@ read_when:
title: "Automation & Tasks"
---
# Automation & Tasks
OpenClaw runs work in the background through tasks, scheduled jobs, event hooks, and standing instructions. This page helps you choose the right mechanism and understand how they fit together.
## Quick decision guide

View File

@@ -3,6 +3,4 @@ summary: "Redirect to /cli/message"
title: "Polls"
---
# Polls
This page moved to [Message tool](/cli/message). See [Message tool](/cli/message) for poll documentation.

View File

@@ -7,8 +7,6 @@ read_when:
title: "Standing Orders"
---
# Standing Orders
Standing orders grant your agent **permanent operating authority** for defined programs. Instead of giving individual task instructions each time, you define programs with clear scope, triggers, and escalation rules — and the agent executes autonomously within those boundaries.
This is the difference between telling your assistant "send the weekly report" every Friday vs. granting standing authority: "You own the weekly report. Compile it every Friday, send it, and only escalate if something looks wrong."

View File

@@ -7,8 +7,6 @@ read_when:
title: "Task Flow"
---
# Task Flow
Task Flow is the flow orchestration substrate that sits above [background tasks](/automation/tasks). It manages durable multi-step flows with their own state, revision tracking, and sync semantics while individual tasks remain the unit of detached work.
## When to use Task Flow

View File

@@ -7,8 +7,6 @@ read_when:
title: "Background Tasks"
---
# Background Tasks
> **Looking for scheduling?** See [Automation & Tasks](/automation) for choosing the right mechanism. This page covers **tracking** background work, not scheduling it.
Background tasks track work that runs **outside your main conversation session**:

View File

@@ -3,6 +3,4 @@ summary: "Redirect to /automation/cron-jobs"
title: "Automation Troubleshooting"
---
# Automation Troubleshooting
This page moved to [Scheduled Tasks](/automation/cron-jobs#troubleshooting). See [Scheduled Tasks](/automation/cron-jobs#troubleshooting) for troubleshooting documentation.

View File

@@ -3,6 +3,4 @@ summary: "Redirect to /automation/cron-jobs"
title: "Webhooks"
---
# Webhooks
This page moved to [Scheduled Tasks](/automation/cron-jobs#webhooks). See [Scheduled Tasks](/automation/cron-jobs#webhooks) for webhook documentation.