kris/afv-library
1
0
Fork 0
mirror of https://github.com/forcedotcom/afv-library.git synced 2026-07-30 03:09:50 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge 14c5adeaf2 into a95d0d3f82

Browse Source
This commit is contained in:
Rob Alexander 2026-06-26 15:12:51 +09:00 committed by GitHub
commit 987c59adff
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 21 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
skills/fetching-salesforce-docs/README.md
View File

@ -28,6 +28,14 @@ This skill does not include:
- deciding when to follow child links from broad official guide pages
- rejecting weak results such as shells, landing pages, and third-party summaries
## Markdown shortcut (developer.salesforce.com)
Modern developer-guide pages publish a raw-Markdown twin: swap `.html` → `.md` on the same URL
and fetch it with a **plain web fetch** — no Playwright needed. The page's "Copy as Markdown" /
"View as Markdown" links expose this. Try it **first** for `developer.salesforce.com/docs/platform/.../guide/*`
pages. It does **not** work for legacy `atlas.*` pages (those return an HTML shell), and
`help.salesforce.com` still needs the renderer — use the extractor below for those.
## Optional utility
A tiny wrapper is available for official Salesforce doc URLs:

14
skills/fetching-salesforce-docs/SKILL.md
View File

@ -95,7 +95,19 @@ This is especially important for:
### 5. For `developer.salesforce.com`
Use this playbook:
**Try the Markdown variant first — it needs no browser.** Modern developer-guide pages now
publish a raw-Markdown twin: swap the `.html` extension for `.md` on the same URL and fetch it
with a **plain web fetch** (the "Copy/View as Markdown" links on the page expose this). It returns
clean Markdown (headings, fenced code, links) with no JS shell, so it's faster and lighter than
Playwright. Example: `…/guide/js-dynamic-components.html` → `…/guide/js-dynamic-components.md`
(verified 2026-06-24).
- **Scope:** confirmed for modern guide pages under `developer.salesforce.com/docs/platform/.../guide/*`.
It does **not** work for legacy **`atlas.*`** pages — `.md` there returns an HTML shell, so fall
back to browser-rendered extraction for those.
- If the `.md` fetch 404s or returns a shell ("Salesforce Developers" with no body), drop to the
Playwright playbook below.
Otherwise use this playbook:
- start with the most likely official guide root
- if the page is JS-heavy, prefer browser-rendered extraction
- check whether the exact concept appears on the page