From db536ba9fa2cff4e608fda1635c4a7589a2fbdc8 Mon Sep 17 00:00:00 2001
From: yinnho <163239465+yinnho@users.noreply.github.com>
Date: Tue, 25 Aug 2026 19:15:08 +0800
Subject: [PATCH] Add curated topic definition for headless-browser

---
 topics/headless-browser/index.md | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 topics/headless-browser/index.md

diff --git a/topics/headless-browser/index.md b/topics/headless-browser/index.md
new file mode 100644
index 00000000000..05c317af43c
--- /dev/null
+++ b/topics/headless-browser/index.md
@@ -0,0 +1,10 @@
+---
+display_name: Headless Browser
+topic: headless-browser
+aliases: headless-browsers, headless
+related: browser-automation, web-scraping, puppeteer, playwright, chromium
+short_description: A headless browser runs a full web engine without a visible window for automation, scraping, and server-side rendering.
+---
+Headless browsers run a complete browser engine — HTML parsing, CSS layout, JavaScript execution, and rendering — without a graphical interface. They power server-side web scraping, automated testing, screenshot generation, and agent tools that read and act on the web.
+
+Headless operation trades a visible window for the ability to run many browser instances cheaply in containers and CI pipelines, often driving them over protocols such as CDP, WebDriver, or MCP.