Try our conversational search powered by Generative AI!
AI OnAI Off
Root Content Folder for Custom Navigation Component
It'd be great if I could have items within my custom component that can be used globally across the catalog UI that commerce offers and then also within CMS.
Nov 13, 2017 17:47
Hi! Check out this old blog post: https://world.episerver.com/blogs/Per-Magne-Skuseth/Dates/2014/11/content-providers-101--part-i-introduction-initialization-ui--identity-mapping/
In the content repository descriptor, you'll need to specify a root folder. This folder can be created programmatically in an initializable module.
On a side note, my old blog posts sure don't very appealing after the sites UI update. Yikes!
Nov 14, 2017 7:46
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
I'm creating a custom navigation component next to "Media", and "Blocks" per this blog post: https://www.epinova.no/en/blog/custom-icontent-with-its-own-navigation-pane/.
I've got that all working, but I really need a root content folder created for global assets within that component. It currently works great for localized pages and whatnot, but I need to add items that are used across the entire EPiServer instance.
I'm looking to add a folder similar to "For All Sites", or "SysGlobalAssets" to my navigation component. I've done some digging and can't really find anything that indicates how to do this.
You can see what I mean in the below pictures. My custom component only has an option for "For This Product". I want something that can be used globally across everything, and I would like to create this programatically.