Finally we are going to put everything together. And share our verdict.
In this post we dive deeper into the `RelationRepository`, `CatalogContentStructureProvider`, `IInventoryService` and `IPriceService`. 4 items you need to be aware of before putting everything together.
As explained in the introduction of this series implementing a custom Catalog is not only overriding / replacing the `CatalogContentProvider`. In this chapter we are dive deeper into the the realted classes which do need some attention.
When you have written a content provider before you are aware that you have to have to point it to a location where to ‘start’ from. For a `CatalogContentProvider` we have to add some code to support this way of working as well. In this chapter we dive deeper into whats needed for this.
Episerver Commerce is a very flexible product that can be customized to suit every e-commerce business needs. Almost every aspect can be customized though the way IOC is implemented in the product. But because everything can be customized to suit your needs does not mean that it’s good at everything, the UI of Episerver Commerce, and mainly the Catalogue part of it is not a walk in the park to work with for everyone.
Controlling Episerver Find by determining which catalogs and how many items to be indexed.
About how to send context related data or other complex data to an external endpoint using Episerver Forms with valid JSON.
Containers seems to be a nice solutions, but it doesn’t always feel right to use this practice. I am going to share the considerations of using a container and share other features which maybe fits a “container use-case” better.
Sometimes I see blobstorages growing at customers side. It can be the result of a job, or because the storage is used by a couple of developers or because Develop and Test are using the same storage. For all these cases I have created this small script. Which does easily create a clean new container for you.
The CMS is not the only place where content is served from. A modern website does present content from different sources like; Video platforms, DAM systems, PIM systems or even other “content networks”. We do consult on a couple of integrations where we have the need to deliver from these kind of sources. Content Providers to the rescue. In this post I am going to share some challenges we have experienced down the road, especially in relation to the IdentityMappingService.