feat: prefer raw-Markdown (.html→.md) over Playwright for developer.salesforce.com docs - #293
Open
rob-alexa wants to merge 1 commit into
Open
feat: prefer raw-Markdown (.html→.md) over Playwright for developer.salesforce.com docs#293rob-alexa wants to merge 1 commit into
rob-alexa wants to merge 1 commit into
Conversation
…salesforce.com docs Modern developer.salesforce.com guide pages now publish a raw-Markdown twin — swap the .html extension for .md on the same URL (the page's "Copy/View as Markdown" links expose it) and a plain web fetch returns clean Markdown with no JS shell. That's faster and lighter than browser-rendered extraction, so the fetching-salesforce-docs playbook should try it first for those pages. Documents the scope: it's confirmed for modern guide pages under /docs/platform/.../guide/*, does NOT work for legacy atlas.* pages (which return an HTML shell), and help.salesforce.com still needs the Playwright extractor — fall back to the existing playbook in those cases. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
References: Contributing guide · Skill authoring guide · Agent Skills spec
What changed
Updates the
fetching-salesforce-docsskill (SKILL.md + README.md) to try a raw-Markdown fetch first fordeveloper.salesforce.comguide pages, before falling back to the existing Playwright extractor.Modern developer-guide pages now publish a raw-Markdown twin: swap the
.htmlextension for.mdon the same URL and a plain web fetch returns clean Markdown (headings, fenced code, links) with no JS shell. Salesforce surfaces this via the "Copy as Markdown" / "View as Markdown" links on each page.Why
Browser-rendered (Playwright) extraction is heavy — it needs the isolated runtime and a Chromium download. For the large and growing set of pages that expose a
.mdtwin, a plain fetch is faster, lighter, and needs no browser at all. Trying it first keeps the Playwright path as a reliable fallback for everything else.Notes
developer.salesforce.com/docs/platform/.../guide/*. It does not work for legacyatlas.*pages (.mdreturns an HTML shell) orhelp.salesforce.com— those still use the existing playbook/extractor, so the change adds a fast path without removing any coverage.…/guide/js-dynamic-components.html→…/guide/js-dynamic-components.md(clean Markdown) and confirmedatlas.*returns a shell.requirements.txtchanges.🤖 Generated with Claude Code