Extend the DAM frontend

Use JavaScript and HTML extensions for menus, list columns, detail sections, and enterprise forms. The frontend handles interaction and presentation; backend extensions or supported REST APIs must enforce permissions, state transitions, and writes.

Development steps

1. Use browser developer tools to identify entry points, methods, prefixes, IDs, pagination, and errors.
2. Create routes, permission identifiers, components, and API clients in a separate frontend module. Read addresses from environment configuration.
3. Display current revision, approval state, and failures before permitting changes to standards, assets, quality, or metadata.
4. Use returned totals and cursors. Show instance IDs and polling state for long-running work.
5. Release static assets with the matching server build and retain API contracts and rollback revisions.

Permissions and compatibility

Hidden routes are not authorization. Handle 401, 403, invisible objects, and revision conflicts. Regress menus, localization, pagination, empty states, errors, and browser refresh after upgrades. Integrate enterprise pages through extension routes, components, and themes rather than modifying product page source directly.