Recommended
More Related Content
More from VarunNehra
More from VarunNehra (9)
Recently uploaded
Recently uploaded (20)
Sitecore Experience Edge, A short story (Intro to Sitecore Experience Edge)
- 1. Sitecore Experience Edge Comes to Sitecoreville A short story Pictures brought to you by Varun Nehra Sitecore Technology MVP @sitecorevarun
- 2. Once upon a time, … in Dec 2020 an announcement was made to the people of Sitecoreville
- 4. The townspeople of Sitecoreville wanted to know what is this Experience Edge? The What!
- 6. As they looked closer…
- 8. They started to imagine…
- 9. CDN
- 10. People wondered why would they need it? The Why!
- 12. Everyone wanted to know how will it work… The How!
- 13. 13
- 14. The crowd started buzzing with questions…
- 17. 17
- 19. Finally, the townspeople started preparing for the barn raising with Experience Edge for Content Hub
- 20. 20
- 21. THE END Credits A Varun Nehra production Courtesy of Altudo, Sitecore, Konabos
- 22. Special thanks to Pieter Brinkman Mark van Aalst Akshay Sura Sitecore’s communications team Sitecore’s production team Google YouTube Sitecore VDD Coming soon to a partner near you (early 2021)!
Editor's Notes
- In the effort to expand it’s SaaS portfolio Sitecore was going to offer something called EE and it would be available for CH and XM
- This was a SaaS solution that sat in between where content is managed and where content is consumed
- They found that this was a GraphQL endpoint that would deliver content from CH and XM to all the channels
- That this being a SaaS solution, the graphQL endpoint could scale regionally in the cloud and bring structured data to the edge and make it globally available via CDN. However, this is not the same CDN they would use for SSG and serving HTML.
- It would eliminate the need for architecting and maintenance of expensive content delivery and devops and bring with it the scalability, reliability of the cloud And get them ready for JAMStack approach for delivering blazing fast performance and faster user experience
- You would have content delivery coupled with blob storage on one end and SSG/SSR (static site generation), client side querying happening on the other, The EE CDN would link the delivery platform to both static and dynamic sites and help cache queries to and from delivery platform. There would be events/trigger for publishing changes to schema and content. Speaking of scaling, for larger sites you may want to look into Incremental Static Regeneration (ISR) with next.js which is a newly released feature that allows the regeneration of static pages during runtime. It’s a hybrid solution of SSG and SSR.
- Someone asked how do I choose between the two products? They were told EE for CH is when you need full headless capability and the focus is on delivering structure content and media assets and when you don’t necessarily need WYSIWYIG style editing. and EE for XM is when you want WYSIWYIG style editing and control over presentation
- Can I bring my own CDN when working with EE for CH? You can implement SSG using your own CDN but you will need a querying and caching layer for Content and Data which Experience Edge basically does for you. You can however export media files from experience edge and host on 3rd party CDN.
- How can I use EE for XM and what are it’s benefits? Use it for static publishing of Sitecore JSS sites and runtime content delivery for headless sites. No need to worry about hosting and devops of content delivery With EE for XM both presentation and content are available for static site generation, Does EE for XM replace JSS and headless services in XM? EE for XM was primarily built to be used with JSS. The presentation layer can call experience edge directly and replace the need for calling Sitecore Headless Services (formerly Sitecore JSS server components) on content delivery. In the future it would support personalization as well. Eliminate CD for Layout Service for static content (no personalization or user session management). XM GraphQL endpoint can fetch data for rendering page HTML in response to a page load request, Fetch data to dynamically change sections of a page with AJAX
- Where does Sitecore XP fit in all of this? CH connector for XP creates Sitecore items that allows layout editing and personalization which can then be published to content delivery. Since content is delivered directly using GraphQL endpoint over CDN, devs will need to manage front-end changes. This being a SaaS platform, XP installation is not required. In fact, XP is not in the race at all when it comes to Experience Edge as EE is not intended to compete with XP, it simply is an alternative for customers not looking for full blown DXP.
- Configure schema and field level publishing settings in the delivery platform Setup evaluation filters for what govern what can be published and when Use Preview API to validate and develop against the unpublished schema and content and test against the Delivery API as it uses the evaluation filters to filter out what makes it to the public web and when And manage access to APIs using API Keys All you need is Sitecore, GraphQL over HTTPS with JWT for authorization and build amazing experience What is the job of a Sitecore developer in this? Build custom data definitions, schemas, relationships, meta data properties in CH to extend default Experience Edge GraphQL