Many projects ultimately require a custom user experience to delight the end-user. This is easily accomplished using a website-in-a-bag. As the name indicates, this feature allows you to upload the assets that make up your website into a bag.
🤖 A website-in-a-bag currently doesn't support folders.
For a complete website-in-a-bag example, check out the Book information #2 article.
A website-in-a-bag often needs to display or otherwise interact with the data that's in the bag. Therefore, they are often dynamic websites, created using tools like Vue.js. You can easily load the data using our SDKs:
The Bridge SDK allows you to interact with the currently opened page. You can use this to figure out the view ID.
The ZAZA SDK allows you to interact with bag content. You can use this to access or upload data in the bag.
Often you only want a user to see your website-in-a-bag rather than the standard bag UI. This can be accomplished by uploading an
autorun.json file into the bag with the following content:
All views, except for owner views, will automatically open the website-in-a-bag.
🤖 This feature is subject to change.
For Enterprise projects it is often convenient to put the assets that make up your website in the template bag. This allows you to manage them from a single place.
⭐ This feature is only available to Enterprise bags.