Knowledge Transfer

[rwcsrichardspencer]

-With "Go Live" coming soon, we'd like to go through some things to understand how we will be able to update them in the future, as well as benchmarking, and a rollout plan for going live and what post-launch support looks like.

• Schema
• Sitemap control
• Search indexing control
• Hreflang
• Dynamic Media/Images
• Modals/popups (outside of forms)
• Forms + Modal forms
• Redirects/CDN
• Placeholders
• Site search working
• Resources pagination
• Crawlable site (robots which one takes precedent, sheet, metadata, configs from current site? index-noindex, sitesearch)
• Locations
• Content updates
• Languages set-up
• Content migration - what do we need to do to keep things in sync
• Analytics / GTM implementation
• A/B testing
• content fragments should not be indexed?
• recaptcha, tolerances
• Header/nav updates, compare with .CA which has icons.
• how do autoblocks work
• img alt texts
• accessibility
• hide/show content on desktop/mobile

[rwcsrichardspencer]

• Schema -> need more information from @kronnox on where/how it all works

• Sitemap control -> order of magnitude on page meta vs raw-index, depends on what was published last, editing raw index discouraged, @MarquiseRosier for more info

• Search indexing control -> with @MarquiseRosier, similar to above

• Hreflang -> with @kronnox

• Dynamic Media/Images -> @MarquiseRosier How can we ensure images that are loaded are using the closest render/output size rather than original size (for example if image is in a 400px column, it would serve the image the closest 400px or higher resolution, but not the full original size) **** Answer Fastly can optimize the images already in the backend and AEM also optimizes images. Follow the suggestions @ https://www.aem.live/developer/block-collection/images ****

• Redirects/CDN -> 410s, how/when will we manage the CDN and EDS within our Adobe suite of products?
  @MarquiseRosier

• Placeholders -> @MarquiseRosier for further information for localization - https://www.aem.live/developer/placeholders
  *** Answer Placeholders are purely to globalize recurring text content that is reused; and provides an easy way to globally update said content. ***

• Site search working -> @MarquiseRosier finalizing it - ** search submits a searchQuery string to query parameters to https://main--stericycle-shared--aemsites.aem.page/en-us/search; this page needs to then take query parameter and query index sheet and search. Functionality half done. **

• Resources pagination -> @rwcsrichardspencer to create ticket, reference : https://stage-us.shredit.com/en-us/resource-center, will also check with HD for estimate

• Crawlable site -> @MarquiseRosier for further info -> ** Pending Response **

• Languages set-up -> @MarquiseRosier for further info, including nav and slight variations such as icons

• Content migration - what do we need to do to keep things in sync -> @MarquiseRosier for further info -> ** Context can there be a tool to update imported content? **

• Analytics / GTM implementation -> @kronnox for more, needs to be authorable, scalable, individualized, and be able to be localized for various countries/languages. Need to ensure tracking clicks, pageviews, events, triggers, etc... for both AA and GTM.

• A/B testing -> Sample here: https://adobe.sharepoint.com/:w:/r/sites/HelixProjects/Shared%20Documents/sites/shredit/[en-us1.docx](https://adobe.sharepoint.com/:w:/r/sites/HelixProjects/Shared%20Documents/sites/shredit/en-us1.docx?d=w138909ee89b341c287c6c808b8fb7202&csf=1&web=1&e=tvRSKK)?d=w138909ee89b341c287c6c808b8fb7202&csf=1&web=1&e=tvRSKK still need to know where to see data, info, percentages, tracking. @MarquiseRosier for more ** Awaiting response from aem-data-desk for access to dashboard to examine experiments **

• content fragments should not be indexed, seeing .html when crawling the site. Needs to be "nofollow" or "noindex" without affecting the indexing of the rest of the site. Essentially should not be crawlable. @MarquiseRosier ** ANSWER: Mark all fragments as nofollow, noindex in metadata.xlsx **

• Accessibility -> @MarquiseRosier & @rwcsrichardspencer to check

• hide/show content on desktop/mobile -> build into all existing components (Hide on Desktop, Hide on Mobile) @MarquiseRosier ** ANSWER: Show is default and if an element needs to be hidden we specify this in section metadata **

TBD:

• how do autoblocks work -> @MarquiseRosier
• Locations
• Content updates
• recaptcha, tolerances

[rwcsrichardspencer]

Hi @MarquiseRosier here's some responses:

• Dynamic Media/Images -> You're linking to some documentation I don't understand. Is this already in place? Is our EDS site already coded for this?
• Placeholders -> If placeholders are simply for re-usable text, is there something for languages/translations table?
• content fragments -> Will marking all as noindex, nofollow, have any impact on the rest of the site?
• Accessibility: https://www.accessibilitychecker.org/audit/?website=https%3A%2F%2Fmain--shredit--stericycle.aem.live%2Fen-us&flag=us

[rwcsrichardspencer]

Ensure that not to block Fragments within Robots.txt, should be marked as noindex/nofollow within their own page/structure. Again, will there be any impact to the rest of the site doing this? @MarquiseRosier

[kronnox]

Schema -> need more information from @kronnox on where/how it all works

There are 3 ways how a schema can be added to the page:

1. Automatically by scripts. Some blocks or page templates have code that will automatically turn their metadata or content into the corresponding schema and add it to the page. Examples can be found in the FAQ block and location templates. This is also done in the scripts.js for all pages with their WebPage schema.
2. As defined in the schemas.xlsx. Looking at the examples in there this should be self-explanatory. I've also added a basic wildcard notation for the paths if a path is ending with /* to apply the schema to all subpages in that directory.
3. Within the document itself as a ld+json metadata field. Look at the document of this page as an example.

Details on how this is done on the technical side can be found in #363 and the code changes in #411.

Analytics / GTM implementation

Already shared the basics in #365.
If you have more specific questions, I'm happy to answer those. I don't know your setup for this, yet.

Hreflang

I provided an example in #354 (comment). Everything else is probably easier to explain in a live-demo. Since I'm not a SEO expert, it would be helpful if your team has any concrete questions on this, so I can prepare and find the correct solutions for your needs.

[rwcsrichardspencer]

@kronnox not seeing any Schema on this page: https://main--shredit--stericycle.aem.page/drafts/janlucaa/schema-test

[kronnox]

@kronnox not seeing any Schema on this page: https://main--shredit--stericycle.aem.page/drafts/janlucaa/schema-test

@rwcsrichardspencer It's there 😉 Just search for it:

[MarquiseRosier]

Adding a comment that we should discuss bulk publishing in the authoring and general EDS operations knowledge transfer.