View configuration
4 min
from pxp 4 0 and builder 0 18, we allow splitting the views json for editing we aim to have a more modular approach in the creation of views in the future in this iteration, the views json is generated from the different, separately created views after upgrading the experience, you can migrate your existing views json to follow the new system note that view names that contain special characters, including "/", may cause problems in the generation of file paths migration with this migration, the views json file will be split into multiple files and will be read only you then will also be able to use 'preset components' which are reusable view components global data is now stored in the experience config json global data will be merged into the experience config json default/storefront/assets/views this folder holds all views and redirects 'path' property is removed and now evaluated based on the folder structure the folder name for dynamic segments (i e \ bundleslug/\ postslug) must be wrapped in square brackets whenever you editm cerate or delete a view / redirect inside this folder, the views json will be updated each current view and redirect will create a folder structure which is identical to the path inside this folder will be the view\ json and / or the redirect json (numbered if multiple exist) a folder with the name 'views' is created if it does not exist yet if it exist, youll need to decide how to handle it default/storefront/assets/presets this folder holds presets presets are components that can be referenced in the views or other components each component can have overridable and default properties create a view to create a new view, create a new folder inside the views folder using the desired path of the new view inside that folder, add a file " view\ json " we currently do not support the creation of a folder structure, so you'll need to create one folder and one file at a time the folder structure is used as the path for any view, which then impacts the url of the content being shown on the website any path segments that you want to use as a variable must be notated with square brackets as follows \[pathsegment]