Key Value: For zero to go-live of your first website - a developer walkthrough to build and launch your first size using Adobe's new Edge Delivery Service. Here's what you will learn -> Step by step walkthrough from the perspective of a project developer -> Setting up the GitHub Repo & document library -> Publish the first content -> Change the sites styling -> Build a custom block
Session Recording
Session Schedule
6th November, 2023 | 09:35-10:05 PST OR 17:35-18:05 UTC OR 18:35-19:05 CET
Speaker(s)
Markus Haack, Sr Software Engineer, Adobe
Moderator(s)
Adobe
Product(s)
Edge Delivery
Session Q&A
Question
Answer
Isn't aem authoring eaasier than document based. ?
"easier" depends on your authors. As you've just seen in the demo with docs authoring, an easy image copy and publish and it's done. Most authors have content in Word already and are used to working with it easier" depending on your authors. As you've just seen in the demo with docs authoring, an easy image copy and publish and it's done. Most authors have content in Word already and are used to working with it
Does EDS have the concept of page templates?
Puneet, I assume you mean document-based authoring. You could create a Word document as a template (.dot). Most of our customers do copy & paste an old document that works as a 'template'.
if you mean create dynamic pages like PDPs based on a template, that can also be done using document templates. if you mean create dynamic pages like PDPs based on a template... that can be done using document templates as well
Writing blocks/components in vanilla JS doesn't look easy to maintain. It reminds me of poorly written JSPs (which was solved by HTL in AEM Sites). Mixing code operating on DOM with HTML chunks looks really hard to maintain and doesn't sound like a good development experience for non-trivial blocks/components. Is there any plan to make it easier or this is a known trade-off of having fast websites?