From ee24a8eeb13eafe7c199211a74cd13060da0095e Mon Sep 17 00:00:00 2001 From: Lamont Crook Date: Wed, 8 Jul 2026 18:19:28 -0600 Subject: [PATCH 1/4] Update Getting Started guide for new blocks, hero variants, and themes Reflect project changes merged since the guide was written: - Add HAL cruise blocks (cruise-ships, find-a-cruise, hero-search) as a distinct group in the Blocks reference. - Note the hero video variant and the form search variant. - Add a Page themes section documenting the metadata-driven body.map theme. - Link the cruise-ships-architecture.html companion deep-dive. Co-Authored-By: Claude Opus 4.8 --- docs/index.html | 45 ++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 40 insertions(+), 5 deletions(-) diff --git a/docs/index.html b/docs/index.html index 24c90dd..a494045 100644 --- a/docs/index.html +++ b/docs/index.html @@ -430,6 +430,7 @@ .tag-js { background: #fff8d6; color: #8a5e00; } .tag-css { background: #e9f1fc; color: #0d51b5; } .tag-da { background: #f3edfb; color: #5b2d99; } + .tag-hal { background: #fdeee4; color: #b4531a; } .skill-card-name { font-size: 13px; font-weight: 700; color: var(--spectrum-gray-900); } .skill-card-desc { font-size: 12px; color: var(--spectrum-gray-600); line-height: 1.5; } @@ -562,6 +563,10 @@ Blocks reference + + + Page themes +
Localization
@@ -836,11 +841,18 @@

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:

+

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 ships the standard boilerplate blocks plus a set of HAL-custom cruise blocks:

+

HAL cruise blocks

+
+
HALcruise-ships

Responsive fleet grid mirroring hollandamerica.com/cruise-ships — ship image, name, class, and detail link. Fetches from a configurable feed endpoint (defaults to a bundled sample).

+
HALfind-a-cruise

Cruise finder with destination / ship / port / duration filters, result cards, and load-more paging. Backed by a configurable endpoint (bundled sample of the Fusion search response).

+
HALhero-search

Home hero with a cruise-search widget; the Search button routes to the find-a-cruise page.

+
+

Standard blocks

-
BLOCKheader

Site navigation, styled to match the Holland America Line brand.

+
BLOCKheader

Site navigation, rebuilt to match the Holland America Line brand.

BLOCKfooter

Global footer authored from a DA fragment.

-
BLOCKhero

Branded hero with imagery and headline, imported from poc-adobe-eds.

+
BLOCKhero

Variant-driven: default image hero, plus a video variant where the image is the LCP poster and a muted autoplay video is layered on top (LCP-gated, reduced-motion aware).

BLOCKcards

Responsive card grid using the brand palette.

BLOCKcarousel

Rotating slides for featured content.

BLOCKcolumns

Multi-column layout for mixed content.

@@ -851,16 +863,39 @@

BLOCKembed

Third-party embeds (video, social, etc.).

BLOCKvideo

Inline and modal video playback.

BLOCKmodal

Overlay dialogs triggered from content.

-
BLOCKform

Author-configurable forms.

+
BLOCKform

Author-configurable forms, including a search variant used for the cruise search bar.

BLOCKsearch

On-site search experience.

BLOCKfragment

Reuse content authored elsewhere in DA.

-
+
+ + Deep dive: Cruise Ships Page — How It's Built & Connected walks through how the cruise-ships block wires DA authoring, the ship feed, and the search API together on EDS. +
+
Coding standards, block conventions, and the publishing workflow live in AGENTS.md at the repository root.
+ +
+

+ + + + Page themes +

+
+

Beyond global brand styles, individual pages can opt into a page-level theme via the page metadata theme field. The theme value becomes a class on <body>, which CSS targets.

+
+
THEMEmap

Paints an authored map image as a full-page navy wallpaper (#022658) that scrolls with the content; text, headings, and plain links lift to white for contrast. Defined in styles/lazy-styles.css as it's decorative, not LCP-critical.

+
+
+ + Set theme to map in a page's metadata to apply body.map. Add new themes by defining a matching body.{theme} rule. +
+
+

From 26ad9c13d25367d86a80ab1f6280e074e4267f45 Mon Sep 17 00:00:00 2001 From: Lamont Crook Date: Wed, 8 Jul 2026 18:22:09 -0600 Subject: [PATCH 2/4] Document the default translate.json reference in the localization section Align the translation write-up to DA's canonical multi-sheet translate.json: config (conflict behaviors + Google service settings), languages (7 default locales + /path convention), and the custom-doc / dnt rule sheets. Link the docs.da.live default translate.json reference. Co-Authored-By: Claude Opus 4.8 --- docs/index.html | 90 ++++++++++++++++++++++++++++++++----------------- 1 file changed, 59 insertions(+), 31 deletions(-) diff --git a/docs/index.html b/docs/index.html index a494045..8a8ce1a 100644 --- a/docs/index.html +++ b/docs/index.html @@ -905,13 +905,13 @@

Translation & localization

-

Document Authoring ships with a built-in Translate app for producing localized versions of pages. Before translating, decide on a localization strategy (which languages, and whether locales are variants of a source or independent). Translation behavior is controlled by a small config sheet in the site's hidden .da configuration folder.

+

Document Authoring ships with a built-in Translate app for producing localized versions of pages. Behavior is driven by a translate.json config — a multi-sheet workbook in the site's hidden .da configuration folder. DA seeds a sensible default translate.json; copy it into this site and adjust the languages and rules for HAL.

- Full reference: docs.da.live — Set up translation. Setup requires DA administrator access. + References: Set up translation (guide) and the default translate.json (config reference). Setup requires DA administrator access.
-

Configure translation for this site

+

Set it up

@@ -924,49 +924,77 @@

Configure translation for this site

-
Set up the sheets
-

Inside .da, create a new sheet named translate, and rename the default data sheet to config.

+
Add the translate.json config
+

Create a translate.json multi-sheet workbook seeded from the DA default. It carries five sheets: config, languages, custom-doc-rules, dnt-content-rules, and dnt-sheet-rules (documented below).

-
Add key/value headers
-

On the config sheet, make the first row a two-column structure with headers key and value. Add one row per option below.

+
Tune the sheets for HAL
+

Edit the config conflict behaviors, prune the languages list to the locales HAL ships, and add any brand terms / URL patterns to the do-not-translate rules.

-
Set the translation options
- - - - - - - -
keyvalueWhat it does
translate.behavioroverwrite · mergeHow returned content is applied. Overwrite replaces old content (no-touch translation); merge keeps existing content you want to retain.
translate.stagingon · offOn copies the source to a separate folder before translating; off sends it directly to the translation service.
rollout.behavioroverwrite · mergeSame overwrite/merge choice, applied to hybrid and locale-based rollout strategies.
-
-
-
-
-
-
Publish the config
-

Click Publish and confirm to activate the settings.

-
-
-
-
-
-
Create a translation project
-

Open the Translate app and create a new project. Your configured options now appear in the project's confirmation dialog.

+
Publish, then create a project
+

Publish the config, then open the Translate app and create a new project — your settings appear in the project's confirmation options.

+ +

The default translate.json

+

The reference config is a :type: multi-sheet workbook. Each sheet below maps directly to the default DA ships.

+ +

config — service & conflict behavior

+ + + + + + + + + + + + +
keydefault valueWhat it controls
sync.conflict.behavioroverwrite, mergeOld content when it is pulled into the "send for translation" folder.
translate.conflict.behavioroverwrite, mergeOld content when new content returns from translation.
rollout.conflict.behavioroverwrite, mergeOld content when new content is rolled out to the locale.
copy.conflict.behavioroverwrite, mergeWhen source content is copied into a region.
translation.service.nameGoogleThe translation service.
translation.service.all.envprodOrder of service endpoints; the first is the default.
translation.service.prod.linkcloud.google.com/translate/docs/overviewService documentation link.
translation.service.prod.originhttps://translate.da.live/googleService endpoint origin.
- Choose merge when localized pages carry market-specific content you don't want a re-translation to clobber; choose overwrite for fully automated, no-touch translation. + The *.conflict.behavior values list the choices; pick merge when localized pages carry market-specific content you don't want re-translation to clobber, and overwrite for fully automated, no-touch translation. +
+ +

languages — locales & path convention

+

Each language maps to a URL location (the locale folder). The default ships seven; keep only what HAL needs.

+ + + + + + + + + + + +
namecodelocationtranslate typeactions
Englishen/enMachine TranslationSkip, Translate
Germande/deMachine TranslationSkip, Translate
Frenchfr/frMachine TranslationSkip, Translate
Spanishes/esMachine TranslationSkip, Translate
Chinesezh/zhMachine TranslationSkip, Translate
Japaneseja/jaMachine TranslationSkip, Translate
Hindihi/hiMachine TranslationSkip, Translate
+ +

rules — what not to translate

+

Three rule sheets keep structural and brand content intact:

+ + + + + + + + +
sheetentryeffect
custom-doc-rulesmetadataTranslate column 2 only when column 1 is title or description.
custom-doc-rulessection-metadataDo not translate.
dnt-content-rules"do not translate me"Literal content strings left untranslated.
dnt-sheet-rulesbeginsWith(http:// || https://)Action dnt — leave URLs untouched in sheets.
+
+ + Add HAL-specific do-not-translate entries — brand names (e.g. "Holland America Line", ship names like "Koningsdam"), trademarked phrases, and campaign slugs — to dnt-content-rules so machine translation leaves them intact.

From be24a612d1054767f8010c781e92515af3c8ed1a Mon Sep 17 00:00:00 2001 From: Lamont Crook Date: Wed, 8 Jul 2026 18:24:51 -0600 Subject: [PATCH 3/4] Add AI tooling section: Document Authoring MCP and EDS skill Reference the two Adobe extensions used to build the project with Claude Code: the Document Authoring MCP (DA Admin API content ops, with a tool capability table) and the Edge Delivery Services skill (content-driven development, block building, import, testing). Link aem.live AI-coding-agents. Co-Authored-By: Claude Opus 4.8 --- docs/index.html | 61 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 61 insertions(+) diff --git a/docs/index.html b/docs/index.html index 8a8ce1a..5aea347 100644 --- a/docs/index.html +++ b/docs/index.html @@ -575,6 +575,13 @@ Translation & localization
+
+
Tooling
+ + + AI tooling + +
@@ -998,6 +1005,60 @@

rules — what not to translate

+ +
+

+ + + + AI tooling +

+
+

This project is built and maintained with Claude Code using two Adobe extensions: the Document Authoring MCP for content operations, and the Edge Delivery Services skill for development. Both target this project's org/site, AdobeDevXSC/hal.

+ +
+
+
MCPDocument Authoring MCP
+

An MCP server that reads and writes DA content programmatically over the DA Admin API (admin.da.live) — list, get, create, update, copy, move, delete sources, plus versions, fragment/media lookup, and media upload.

+
+
+
SKILLEdge Delivery Services skill
+

A Claude Code plugin of EDS skills — content-driven development, block building & content modeling, page import/migration, block testing, and docs search — grounded in the aem.live documentation.

+
+
+ +

Document Authoring MCP — capabilities

+

The MCP surfaces the DA Admin API as tools scoped to AdobeDevXSC/hal:

+ + + + + + + + + + + + +
ToolWhat it does
da_list_sourcesList content sources (pages, sheets, media) under a path.
da_get_sourceRead the HTML/JSON of a specific source.
da_create_source · da_update_sourceCreate or update a page or sheet.
da_copy_content · da_move_contentCopy or move content between paths.
da_delete_sourceDelete a source.
da_get_versionsInspect version history for a source.
da_lookup_fragment · da_lookup_mediaResolve fragments and referenced media.
da_upload_mediaUpload an image or asset into the DA media library.
+ +

Edge Delivery Services skill — what it covers

+

The skill encodes the conventions in AGENTS.md and the practices below, so generated code follows EDS standards:

+
    +
  • Content-driven development — decide the block's content model before writing code.
    • +
  • Building blocks & content modeling — block JS/CSS conventions, initial structure as the author contract.
    • +
  • Page import / migration — scrape a source page and map it onto existing blocks.
    • +
  • Testing blocks — lint, local preview, and performance validation before a PR.
    • +
  • Docs search — grounded lookups against the aem.live documentation.
    • +
+ +
+ + For guidance on working effectively with these AI tools, see aem.live — AI coding agents. +
+
+
AdobeDevXSC / hal  ·  Holland America Line on AEM Edge Delivery Services From 3882bbcc7e4e80a0775e914fd6f700c25f1f97de Mon Sep 17 00:00:00 2001 From: Lamont Crook Date: Wed, 8 Jul 2026 18:29:54 -0600 Subject: [PATCH 4/4] Add Document Authoring MCP endpoint URL and connect snippet Surface the DA MCP server URL (https://mcp.adobeaemcloud.com/adobe/mcp/da) on the tooling card and add a claude mcp add connection example. Co-Authored-By: Claude Opus 4.8 --- docs/index.html | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/index.html b/docs/index.html index 5aea347..5078c2b 100644 --- a/docs/index.html +++ b/docs/index.html @@ -1020,6 +1020,7 @@

MCPDocument Authoring MCP

An MCP server that reads and writes DA content programmatically over the DA Admin API (admin.da.live) — list, get, create, update, copy, move, delete sources, plus versions, fragment/media lookup, and media upload.

+

Endpoint: mcp.adobeaemcloud.com/adobe/mcp/da

SKILLEdge Delivery Services skill
@@ -1028,7 +1029,10 @@

Document Authoring MCP — capabilities

-

The MCP surfaces the DA Admin API as tools scoped to AdobeDevXSC/hal:

+

The server runs at https://mcp.adobeaemcloud.com/adobe/mcp/da. Register it with your MCP client, for example:

+
# Claude Code +claude mcp add --transport http da https://mcp.adobeaemcloud.com/adobe/mcp/da
+

Once connected, the MCP surfaces the DA Admin API as tools scoped to AdobeDevXSC/hal:

ToolWhat it does