Holland America Line โ Getting Started
+A developer & author guide for the Holland America Line website built on Adobe Experience Manager Edge Delivery Services. Learn what the project is, where the code and content live, and how to get running locally.
++ + The initiative +
+ +This project delivers the Holland America Line web experience on Adobe Experience Manager Edge Delivery Services (EDS). It is built from the AEM boilerplate and follows Adobe's standards for fast, easy-to-author, and maintainable web experiences.
+Content is authored in Document Authoring (DA) and served through the EDS pipeline. The codebase carries the Holland America brand system โ navy, orange, and the Quasimoda / Minion display typefaces โ applied through global styles and a library of reusable blocks. Adobe Edge Functions have been set up as a baseline for request-time customization at the CDN edge.
+ +Vanilla JS, modern CSS, no build step. Three-phase (eager / lazy / delayed) page loading targets a 100 Lighthouse score.
+Authors edit pages in Document Authoring; blocks decorate the content authors produce โ no code deploy required to publish.
+Brand tokens (navy #022658, orange #e46c24, Quasimoda + Minion) drive global styles, the header, hero, and cards.
+| Attribute | Value |
|---|---|
| GitHub org | AdobeDevXSC |
| Repository | hal |
| Primary branch | main |
| Content system | Document Authoring (DA) via da.live |
| Content mount | content.da.live/AdobeDevXSC/hal/ |
| Base boilerplate | adobe/aem-boilerplate |
| Extras | Adobe Edge Functions baseline |
+ + Key URLs +
+ +Every place you need to reach the code, the content, and the rendered site.
+{branch}--hal--AdobeDevXSC.aem.page (preview) or .aem.live (published). Swap main for your feature branch to preview it.
+ + + Find the GitHub repository +
+ +All of the site's code lives in one repository under the AdobeDevXSC GitHub organization.
+Open github.com/AdobeDevXSC/hal. If you have access it opens directly; otherwise request access to the AdobeDevXSC org.
Visit github.com/AdobeDevXSC, open the Repositories tab, and search for hal.
If you already have the code, run git remote -v (or gh repo view --json nameWithOwner) โ it reports AdobeDevXSC/hal.
AdobeDevXSC) and repo name (hal) are the two values you plug into every preview and live URL.
+ + + Find the DA content folder +
+ +Page content is authored in Document Authoring (DA), not in the repo. The repo's fstab.yaml tells you exactly which DA folder feeds this site.
At the repo root, fstab.yaml declares where content comes from:
The path after content.da.live/ is the DA org and folder: AdobeDevXSC / hal.
Translate that mount into the DA app URL by swapping content.da.live/ for da.live/#/:
Open da.live/#/AdobeDevXSC/hal to browse and edit pages, nav, footer, and metadata.
+Any page you preview at main--hal--AdobeDevXSC.aem.page is pulled from that DA folder. Inspect the raw content of a page with:
{org}/{repo}. Here that is AdobeDevXSC/hal โ the same org and name as GitHub.
+ + + Architecture +
+ +Content authored in DA and code from GitHub are combined by the EDS pipeline and served through preview and live CDN environments.
+AdobeDevXSC/hal
AdobeDevXSC/hal
+ Adobe Edge Functions
Repository structure
++ + Local development +
+ +The AEM CLI proxies your local code against previewed DA content. You edit code locally and see it against real content at localhost:3000.
scripts/aem.js โ it is the core EDS library. Add site logic in scripts.js, block files, or global styles instead.
+ + + Blocks reference +
+ +Blocks are the reusable building blocks that add styling and behavior to authored content. Each lives in /blocks/{name}/ as a {name}.js + {name}.css pair. The project currently ships these blocks:
Site navigation, styled to match the Holland America Line brand.
Global footer authored from a DA fragment.
Branded hero with imagery and headline, imported from poc-adobe-eds.
Responsive card grid using the brand palette.
Rotating slides for featured content.
Multi-column layout for mixed content.
Expandable/collapsible content sections.
Tabbed content panels.
Structured tabular content.
Pull quotes and testimonials.
Third-party embeds (video, social, etc.).
Inline and modal video playback.
Overlay dialogs triggered from content.
Author-configurable forms.
On-site search experience.
Reuse content authored elsewhere in DA.