• Syndicated blog - Posted on: Jun 03, 2018

    For a client’s website there was a need to implement EPiServer‘s output cache with different expire times not based on PageType, but rather page instance. After weighing pros and cons we decided on a solution with a number of ContentArea propertie...

  • Syndicated blog - Posted on: Apr 10, 2018

    Lately I spent some time investigating 404 NotFound responses from an EPiServer Content Delivery Api installation. While the SiteDefinition Api URL worked just fine, the problem was that the API returned 404 NotFound for all contents requested. He...

  • Syndicated blog - Posted on: Apr 08, 2018

    If you read my previous article React and EPiServer: Aggregated output with EPiServer.ContentDeliveryApi you saw a way of including your own aggregated data through properties in the content model classes. Since the JOS Content Serializer also has...

  • Syndicated blog - Posted on: Apr 06, 2018

    If you read my previous article on React and EPiServer: Moving to EPiServer Headless (EPiServer.ContentDeliveryApi) with friendly URLs – Quick POC, you’ll know I wanted to output EPiServer Content information by friendly URL to a page rather than...

  • Syndicated blog - Posted on: Mar 23, 2018

    So EPiServer released a beta version of the ContentDeliveryApi. Nice. My current client uses the JOS Content Serializer for creating JSON data from EPiServer pages for view, preview and on-page-editing with React, as described in previous articles...

businessWorkplace: Neoleaf AB
emoji_eventsCommunity Level: Contributing Citizen

Syndication and sharing