Script include
Use script include when you must add page-level JavaScript; prefer shared clientlibs first.
Live demo
This component ships in AEM as apps/concordia/components/script (component group: Developer / special). Expand this section with visitor goals and author tasks once the dialog and templates are fully reviewed.
Behaviour
- Behaviour depends on dialog fields, underlying models, and clientlibs. Confirm against the current JSP, HTL, or Sling model in the repository.
Anatomy
- Root output from the component script.
- Child regions or parsys as defined in the implementation.
Replace with a labelled screenshot or diagram when ready.
Content guidelines
- Follow editorial and unit standards for the domain (directory, news, hub, academics, and so on).
- Keep labels and helper text plain language; avoid duplicating content that belongs in Title or Introduction.
Best practices
Do
- Match this component to the use case described in Overview; link to sibling components (for example Search vs Thunderstone variants) when authors might confuse them.
Don't
- Don't use this component where a Templates initial structure already fixes the same content unless editorial control requires an override.
When to use
- When the component group and template policy allow it on your page type.
When not to use
- When a simpler component or static content meets the need with less maintenance.