Publish the catalogue as a page on GitHub Pages

[oblomov-dev]

samples and samples-controls each publish the question their corpus is actually asked — a learning path there, a search over 430 control ports here. This corpus is asked something else again, and neither page answers it:

"my system is 7.50 and on-premise — what of this can I even run?"
"is there a sample for WebSockets, and what do I have to set up first?"

Both are questions about the system, not about the sample, which is what this repository is made of. So web/ is a search over the catalogue with two facets — the system you have and the technology you came for — at https://abap2ui5.github.io/samples-stack/.

What is on it

• Your system, one select for both halves of the release question: ABAP Cloud drops the three on-premise packages, a Standard release keeps every package at or below it. The counts are in the labels (7.40 SP08 → 18, 7.50 → 20, 7.54 → 30, Cloud → 27 of 32), so what an older system costs is visible before the click.
• Technology as chips rather than a select — ten values, and seeing all ten at once is half the answer to "what is even in here".
• Free text over class, title, @summary, @keywords, the ABAP-Doc header and the package text, which is why websocket finds src/07 although the word is in none of its classes.
• Per card: what the sample needs from the system, its release floor, the ?app_start= line with a copy button, its keywords as clickable chips, and — for the twelve classes that carry one — the ABAP-Doc header with its EML statements, the fullest description this repository holds of a sample.
• Below the results: How to run one, the nine packages as tiles that filter the list, and the three-step ladder. Filters live in the URL, so a search is linkable.

No playground link

Unlike on the two sibling pages. The playground runs a class with no system behind it, and a system is precisely what every sample here requires — a Gateway service, a RAP business object, an APC channel, a launchpad. Each app would open there and then fail, so the cards link to the source, to the package README's What you need, and to the one-package branch abapGit takes.

How it is built

No new source of truth: every fact is read out of what the repository already keeps — the scan behind SAMPLES.md (@summary, @keywords, the ABAP-Doc header, DESCRIPT), .github/packages.json and the README's package table. Adding a sample or a package therefore needs no step for the page. The title rule the two catalogues share moves into the scan as sampleTitle( ) so it cannot drift; SAMPLES.md is byte-identical.

web/apps.json is generated and not committed, so a sample pull request carries no diff of derived data and the page can never be staler than the tree.

deploy-web	regenerates the index and publishes web/ as the Pages artefact
check-web	the same generator with --check on every pull request — npm run check:web, also part of npm run check

check-web is what catches a package with no README row, a row whose cells no longer parse, or an app in a directory that is no package. All three break the page without touching web/, and none of them shows up before a deploy, which happens after the merge.

Verified

All node checks green (check-overview, check-keywords, check-abapdoc, check-prose-names, check-samples-md, check-web). The page rendered in Chromium with no console errors, light and dark, 390–1440 px without horizontal scrolling; deep links, facet counts and the keyword chips check out. No ABAP is touched by this change.

One manual step after merging

Settings → Pages → Source has to be set to GitHub Actions once, or the first deploy serves nothing.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CHNPdkwxjAfH3JxmteDiHt

---

Generated by Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.