React Archive

React and EPiServer: Removing properties from output in EPiServer.ContentDeliveryApi

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 a very useful ignore attribute, ContentSerializerIgnoreAttribute, I’d love the EPiServer Content Delivery Api to have one as well. Removing superfluous properties from EPiServer ContentDeliveryApi output Since the EPiServer …

React and EPiServer: Aggregated output with EPiServer.ContentDeliveryApi

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 using the headless API’s own paths. This I did, but what about aggreagated information? You know, the stuff that are using for instance content from other EPiServer …

React and EPiServer: Moving to EPiServer Headless (EPiServer.ContentDeliveryApi) with friendly URLs – Quick POC

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. However, sooner or later it will be neccessary to start using EPiServer’s own methods for this. I had a quick look at the API functionality, and it seems …

React and EPiServer – Generic pass-through property handler for JOS ContentSerializer

In a previous article I wrote about React and EPiServer – Custom rendering of EPiServer block in XhtmlString field without partial block controller, as we’re using the JOS Content Serializer to make JSON of our EPiServer content. This is in order to pass it to React. We were using the version 2.0.1, and it differs a bit on how things are done now (currently latest …

React and EPiServer – Getting friendly URLs in EPiServer’s XHtml fields using JOS.ContentSerializer for React support

So just a follow up on the previous article React and EPiServer – Custom rendering of EPiServer block in XhtmlString field without partial block controller in regards to friendly URLs. We noticed that all our internal EPiServer links in the XHtml field properties remained on the internal form ~/link/{guid}.aspx, even in the view mode. The reason for this was really quite obvious since we had …

React and EPiServer – Custom rendering of EPiServer block in XhtmlString field without partial block controller

For my current client we’re building a component based platform as a common feature hub for serveral large EPiServer websites. For this, we have stripped away the default Razor based rendering that is normally used for the view and edit modes, and replaced it with React all the way through. Having React render blocks through ContentArea properties for the view and on-page-edit modes may not …