fetching-salesforce-docs

Salesforce Help articles often require browser execution to reveal content. Using Playwright with stealth plugins renders JS-heavy pages, extracts the actual article body, and navigates child links to retrieve the complete documentation text.

Salesforce documentation pages are frequently JavaScript-heavy or shell-rendered, causing standard fetch methods to fail. Browser-based extraction via Playwright renders the page fully, revealing the real article body that standard retrieval cannot access.

Yes, this retrieves official Salesforce documentation from public web pages across Apex, LWC, SLDS, and Help articles. It prioritizes Salesforce-owned domains and validates exact-concept matching to ensure the extracted page contains the requested identifier.

Yes, evidence-based grounding validates that the extracted page contains the requested concept or identifier. It rejects landing pages and weak matches, ensuring the output includes the title, official URL, source type, and browser-rendering signals.

The best way to ground LWC API answers is retrieving official Salesforce docs via browser-based extraction. This ensures the content comes from Salesforce-owned domains and includes structured output with the official URL and source type for verification.

Playwright is required when fetching Salesforce setup articles from public web pages because these pages are JS-heavy and shell-rendered. Standard fetching returns only shells, while Playwright with stealth plugins executes the browser to reveal the real article body.