Key Value: A crucial aspect of every project is the structure of the content documents. An author should be able to navigate through the documents intuitively without any problems. We will provide guidelines and tips and tricks on how to structure your content documents. Content: When structuring a document for Franklin, it is essential for authors who will contribute content to make it simple and intuitive. This session will explain how to structure content documents in a content first approach letting authors drive the content structure. We will explain best practices, how and when to use sections and blocks and show common project pitfalls to avoid.
23rd May, 2023 | 09:45-10:30 PST OR 17:45-18:30 UTC OR 18:45-19:30 CET
Markus Haack, Sr Software Engineer, Adobe
Edge Publish & Authoring Services
Please use this thread to ask the question related to this Session.
Question about the Franklin Library
Most if not all example pages here (Helix Live Site), load the Tag Managers (Launch or GTM) in the delayed.js. Actually, I see in delayed.js almost any logic beyond the above-the-fold content rendering to help achieving LCP 100 scores (Page Speed Insights - Web Core Vitals).
Reviewing the Franklin Library, it looks as the delayed.js will be executed after 2-3 seconds in every page load, which will delay the deployment of dependencies carried by Tag Managers, including built-in Cookie Consent, Analytics, Social Media pixels, Personalization (Target) and any other 3rd parties.
Historically, Data Layers and Tag managers have been loaded at the top of <head> (even if using the async parameter to avoid render blocking). Also, with a large percentage of the web using frontend frameworks (e.g. React/Bootstrap) to render their sites, how do you recommend managing this tech topic with customers and their vendors when promoting this disrupting paradigm and not failing in the process?.
Anecdotally, I've tried migrating an existing site using Helix and not loading Tag Managers and frontend frameworks in the delayed.js and it totally failed in the Page Speed Insights scores.
Awesome @mhaack! thanks for sharing.
TL;DR. Few takeaways from the video above:
- Martech stack (Analytics, Tracking, Personalization, Experimentation) will drag you down.
- There's work in progress from Adobe and other partners (Google included) to make the Martech stack part of the Web platform in order to solve some of these use cases.
In the meantime, it's recommended:
- Start with a 100 Performance score and not the other way.
- Find generic approaches for what is really needed, or adds business value, and prioritize JS load based on that.
- Continuously test to keep 100 score from being impacted after every decision made.