feat: prepare the launch of UK version of www.petplace.com

Use case

The customer wants to start a new website for the UK market based on their existing www.petplace.com.

The localized version should:

run on www.petplace.com/en-gb/
run a curated subset of the main content (customer will handle that part) from the /en-gb/ folder in Sharepoint
run a separate category index and search
run a separate sitemap
have separated SEO meta tags (canonical, hreflang, etc.)
have the same design as the main site
invite the user to browse the en-gb site when they are in the UK, and the regular site otherwise
~have separated martech stack~ (deferred)

🚧 Technical

As part of this initiative, we'll cover:

content structuring in Sharepoint
code-level adjustments to support multiple geos and locales
martech customizations per geo
infra work to set up the new DNS and properly map to the en-gb sub-folder

🧑‍💻 Tasks

🧱 Header/footer and common fragments

Localize the generic fragments:
- [x] Create folders for each locale at the root in Sharepoint and copy over the /fragments folder
- [x] Introduce window.hlx.contentBasePath and set it to the active locale https://github.com/hlxsites/petplace/pull/371
- [x] Update the header block to use the contentBasePath in the URL when fetching nav.docx and sidenav.docx
- [x] Update the footer block to use the contentBasePath in the URL when fetching footer.docx
- [x] Update the popular-articles block to use the contentBasePath in the URL when fetching popular-posts.docx
- [x] Update the popular-tags block to use the contentBasePath in the URL when fetching popular-tags.docx
- [x] Update the article-signup template and scripts.js to use the contentBasePath in the URL when fetching newsletter-footer.docx and newsletter-popup.docx
- [x] Update the searchresults template to use the locale in the URL when fetching 404.docx
Localize static strings:
- [x] Refactor the project to leverage the placeholders.xslx
  https://github.com/hlxsites/petplace/pull/365
- [x] Set up a placeholders.xslx sheet in each locale to handle hardcoded strings that need to be translated.
- [x] Set the placeholders prefix according to the active locale (i.e. contentBasePath)
Localize the 404 page
- [x] 404 page: The content is mostly handled by the searchresults template and the 404.docx fragment, but page metadata need to be updated https://github.com/hlxsites/petplace/pull/372
Localize the newsletter signup
- [x] Use the contentBasePath in the newsletter blocks
- [x] Adjust the iterable submission per locale https://github.com/hlxsites/petplace/pull/400
Localize author pages https://github.com/hlxsites/petplace/pull/374
- [x] Copy over authors query index sheet and index page to the locale folder
- [x] Update the article-author template to use the contentbasePath

📰 Articles

https://github.com/hlxsites/petplace/pull/376
- [x] create a new article/query-index.xslx for each locale
- [x] update helix-query.yaml to include the new article indexes

📊 SEO

sitemap (see: https://www.aem.live/developer/sitemap) https://github.com/hlxsites/petplace/pull/373
- [x] create a new /query-index.xslx for each locale
- [x] update helix-query.yaml to include the new sitemap indexes
- [x] update helix-sitemap.yaml to list the sitemaps for each geo. See: https://www.aem.live/developer/sitemap#multiple-sitemaps

SEO meta tags

[x] Ensure HTML lang and canonical URLs are set properly on localized pages

<html lang="en-GB">
<head>
<link rel="canonical" href="https://www.petplace.com/en-gb/">

<html lang="en-US">
<head>
<link rel="canonical" href="https://www.petplace.com">

~Add proper meta links~ (likely redundant with sitemap changes, see: https://developers.google.com/search/docs/specialty/international/localized-versions):

<html lang="en-GB">
<head>
<link rel="alternate" hreflang="en-US" href="https://www.petplace.com/">
<link rel="alternate" hreflang="en-GB" href="https://www.petplace.com/en-gb/">

[x] validate with https://technicalseo.com/tools/hreflang/

🤖 CI for search & XML feeds

[x] .github/ci/build-search-index.js
- https://github.com/hlxsites/petplace/pull/397
- [x] Add support for a new locale argument
- [x] Set the argument based on the source document locale (i.e. path in sharepoint)
- [x] Create separate search index files for each locale
- [x] Adjust the search worker to load the right index for the current locale
- [x] Update the index only for the locale of the page that triggered the workflow

[x] .github/ci/generate-news-feed.js

https://github.com/hlxsites/petplace/pull/398
[x] Add support for a new locale argument
[x] Set the argument based on the source document locale (i.e. path in sharepoint)
[x] Create separate XML feed files for each locale

[x] Adjust the head.html to reference the feeds with the right locale

<link rel="alternate" hreflang="en-US" type="application/rss+xml" href="https://www.petplace.com/rss.xml">
<link rel="alternate" hreflang="en-US" type="application/atom+xml" href="https://www.petplace.com/atom.xml">
<link rel="alternate" hreflang="en-GB" type="application/rss+xml" href="https://www.petplace.com/rss-en-gb.xml">
<link rel="alternate" hreflang="en-GB" type="application/atom+xml" href="https://www.petplace.com/atom-en-gb.xml">

[x] Update the feed only for the locale of the page that triggered the workflow

📝 Content Migration

petplace.com_-_post-migration_optimizations_and_additions.xlsx

[x] copy breed pages
[x] copy over selected article pages
[x] create metatada.xlsx copy for primary language tag
[x] copy over selected authors pages
[x] copy over selected tags pages
[x] copy over selected root pages

💰 Martech

[x] adjust martech instrumentation per locale
[x] introduce cookie consent dialog and tie the 3rd party dependencies to the selection, https://github.com/hlxsites/petplace/pull/401

📝 Authoring

[ ] restrict sharepoint write access for each authoring team, per locale
- [x] global authoring team can access everything
- [ ] create a new group in sharepoint for the local team
- [ ] local authoring team can only modify their content in /en-gb/

🌐 Infra

https://github.com/hlxsites/petplace/pull/395

[x] We can leverage x-served-by headers to detect the Fastly pop location
[x] ~Introduce geo service to detect where user is coming from: https://git.corp.adobe.com/experience-platform/franklin-delivery-cdn/issues/138~
[x] Introduce a popup with suggested redirection if ending on the wrong site (i.e. UK on petplace.com is asked if they want to go to petplace.co.uk, non-UK on petplace.com/en-gb/ is asked if they want to go to petplace.com)
- [x] Re-use the existing popup block
- [x] Popup should show 1 + n buttons, 1 for the current region (i.e. "Stay on …"), and then 1 for each other region available (only 1 for now, but should plan for an array down the road)

🚀 Go-live

[ ] Merge https://github.com/hlxsites/petplace/pull/424
[ ] Remove robots noindex from en-gb pages
[x] preview/publish all en-gb pages
[ ] publish main footer with region selector
[x] adjust clarity config to support consent: https://learn.microsoft.com/en-us/clarity/setup-and-installation/cookie-consent

hlxsites / petplace

feat: prepare the launch of UK version of www.petplace.com #364