Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Using the extensibility benefits of EPiServer

285 Aufrufe

Veröffentlicht am

EPiServer provides a lot of functionality that can be used out-of-the-box. In some occasions, like specific project requirements we need to extend the CMS. Learn in this session, some of the options you as a developer have.

Veröffentlicht in: Technologie
  • Loggen Sie sich ein, um Kommentare anzuzeigen.

  • Gehören Sie zu den Ersten, denen das gefällt!

Using the extensibility benefits of EPiServer

  1. 1. Using the extensibility benefits of EPiServer Patrick van Kleef
  2. 2. Patrick van Kleef EMVP • Software Developer • Geta, Amsterdam Netherlands • www.patrickvankleef.com • slideshare.com/patkleef • github.com/patkleef Episerver Page Number
  3. 3. Why extending EPiServer? • Customer requirements • Integrating other systems • Simplify editor experience Episerver
  4. 4. Choose the right solution • Not always choose the easy/fastest way • Don’t abuse the content tree for storing data • Think of good maintainable solution that’s future-proof Episerver
  5. 5. Specifications • Manage contact information • View – contact detail information • Send message • Use contact information on pages • Page/block type • Admin mode Episerver
  6. 6. Custom solution Episerver Extend functionality EPiServer OR
  7. 7. Where save the data? • Dynamic Data Store • Entity Framework (other object-relational mapper) • Save as IContent Episerver
  8. 8. ContactData : IContent • Define properties • Create and edit forms • Store in database • Loading and saving via IContentRepository • Reuse gadgets and views Episerver
  9. 9. - ComponentDefinitionBase - “epi-cms.widget.HierarchicalList” - ContentRepositoryDescriptorBa se - ContainedTypes - Roots
  10. 10. - ViewConfiguration<ContactData > “app/editors/contactinformation” - Contactinformation.js - UIDescriptor<ContactData> DefaultView AddDisabledView
  11. 11. But then… new specifications Episerver
  12. 12. What’s changing? • No need to adjust the custom view • Contact data stays the same • New gadget • Custom content provider Episerver
  13. 13. - ComponentDefinitionBase “epi-cms.widget.HierarchicalList” - ContentRepositoryDescriptorBase ContainedTypes Roots - ContentProvider Entrypoint Capabilities
  14. 14. Summarize • Gadget • Custom view • ContentProvider • Rest store • Module.config • Module initializer Episerver
  15. 15. Episerver Thanks! slideshare.com/patkleef github.com/patkleef/AscendStockholmDemo www.patrickvankleef.com

×