on UAT instance output commented out HTML with objects values
When we render on ENV UAT a page it would be beneficial to see in the <!-- --> tags a sort of JSON.stringify of the object that was used for this particular page to be rendered.
Session sharing between Shopify and Strapi
For logged in user inside Shopify would be great to add ability to get signed in into the Strapi CMS instance in one click.
Bulk files pulled from Gitpod
Create an ability to pull data for build from an uploaded bulk API response file to Gitpod directly
Fetching parameters from URL unified way
Would be great to have a function that will fetch params from URL and then be able to compare fetched strings with data from CMS or eCommerce platform
Define VCL redirects mappings from Strapi
Fastly allow to update VCL files via API and fetch dynamic redirects pairs from DB or via API, it would be great to make redirects freely editable through CMS Admin panel.
Embed code injection directly into source code
in some cases tools like RescueMetrics require that their embed code is served within the source code of a page directly from server, and do not recommend to use Google Tag Manager for it. Would be great to implement a way of injecting code for example using Zaraz via Cloudflare. Thanks!
Add support for upsell options on Product Page
It would be great to be able to simple define upsells and handle logic with adding them to cart when the user buys a single product.
Templates for pages in Strapi
Sometimes we need to make a specific page of a site to look&feel differently from the other page of same type, it can be achieved through custom page classname assigned to it based on page slug however in case we want similar behavior applied to multiple pages it becomes tedious, on top of it usage of a custom JS that affects interaction on the page would also create unnecessary codebase burden. Would be great if we can setup and define Templates which are contain custom CSS and custom JS and then be able to apply template to one or more pages, similar approach with Components, let's say we have a section within the page and multiple instances of this section should look differently but ultimately rendered via same Component, example - Content Grid, for sections we can define Skin, and this way Section would pull CSS and JS required for that specific instance of that section, Templates will be applied as a most high level on top of Sections and Page.
Ability to merge separate products from Shopify via Metafields
I see it the way that on the eCommerce platform side user would be able to configure products as a pair/combo, basically connect to each other and then on the Headless Core side B2storefront will be able to recognize this relation between products and allow developer to build functionality on top of that.