OpenUI5 vs SAPUI5 list, and custom controls in their own BSP

[oblomov-dev]

Two corrections, one commit each.

1. Bootstrapping: sap.viz is SAPUI5, not OpenUI5

The "OpenUI5 vs SAPUI5" section of configuration/setup/ui5_bootstrapping.md listed sap.viz among the libraries OpenUI5 contains. It does not:

• @openui5/sap.viz does not exist on npm; only @sapui5/sap.viz does.
• The abap2UI5 linter lists it as SAPUI5-only.

A reader who stayed on the default OpenUI5 bootstrap for a VizFrame chart got a view that could not load.

The fix:

• sap.viz moves to the SAPUI5 bullet.
• Next to it are two other SAPUI5-only libraries readers run into: sap.ui.richtexteditor (RichTextEditor) and sap.ui.export (spreadsheet export).
• The closing paragraph now says what happens on the wrong bootstrap.

I checked every library the section names against the npm scopes. The OpenUI5 ones exist only as @openui5/*; the SAPUI5 ones exist only as @sapui5/*.

2. Custom controls: the own-BSP route, not the framework folder

advanced/extensibility/custom_control.md told readers to put a new control into the framework's app/webapp/cc/ and to copy Timer.js, which the framework marks obsolete (app/webapp/cc/Timer.js:8). The framework says app code belongs in a BSP of its own:

• The frontend reserves the resource roots z2ui5_ccc and z2ui5_cci in app/webapp/manifest.json.
• z2ui5_if_client says frontend code of the app's own ships as a custom control in z2ui5_ccc.
• Insight 12 on this site says the same.

The rewritten Frontend section covers:

• the two roots;
• the custom-controls-customer template, its Example control, npm run app2bsp and abapGit;
• how a control that wraps a third-party library loads it, following the custom-controls add-on: jsDelivr on main, which the CSP has to allow; the BSP itself on local.

The backend example now uses the template's real control and the z2ui5_ccc.cc namespace. A closing note gives the console check that tells a typo in the one differing letter apart from a missing BSP.

advanced/extensibility/frontend.md also told readers to run npm run auto_app2abap before a pull request. Per the framework's AGENTS.md, that step alone leaves the generated ABAP un-normalized. The command is now npm run app2abap, which formats, generates and normalizes.

Side note for the framework, not changed here: Component.js, z2ui5_cl_ui5_http_handler and the framework's AGENTS.md name abap2UI5/customer-frontend-extension as the z2ui5_ccc template. That repository does not exist; the template lives at abap2UI5-addons/custom-controls-customer, which is what this site already links from addons.md and renaming.md.

Verification

Run locally, all green:

• npm test
• check:vocabulary, check:line-length (custom_control.md is now a wrapped page)
• check:conventions (covers the new chain), check:playground
• check:api-names and check:examples, with A2UI5_HOME pointing at a framework clone on main
• check:images, check:design
• docs:build, check:cross-site

npm run build could not run in my environment: it borrows files from abap2ui5.github.io, which the proxy blocks, and it fails the same way on unchanged main. This PR's CI covers it.

🤖 Generated with Claude Code

https://claude.ai/code/session_014hMqkiuAQP6mAVnUEDHoTv

---

Generated by Claude Code