Only Chromium-based browsers such as Google Chrome are officially supported at this time, but other browsers are known to work.

Yes!

Not at this time.

JSX.

Currently, Shogun Frontend does not provide any out of the box integrations or widgets, but documentation is available for several integrations. See Frontend Integrations.

Not at this time, typically PIM providers due provide a connector integration into Shopify or BigCommerce which is preferred type of integration vs integrating a PIM directly with Shogun.

Not at this time, typically PIM providers due provide a connector integration into Shopify or BigCommerce which is preferred type of integration vs integrating a PIM directly with Shogun.

Not at this time.

You can upload and use .jpg, .png, .svg, .gif, .mp4 and .pdf.

200 MB per file.

Not at this time.

Content that will be reused or needs to be strictly defined should live in the CMS (Content Management System). See Key Concepts.

Shogun Frontend's build process is different from a traditional store in that it is a Static Progress Web App, which means that building and publishing a change in the store requires compiling a static version of the entire site. Several factors influence the processing time, but it's roughly proportionate to the number of pages you have on your site.

We aim to make it as easy as building a Shopify theme or quicker. Depending on how large your store is, can take a few seconds up to several minutes. We have lots of features coming soon to help speed this process up even more!

Text, Image, Number, RichText, Boolean, Reference (other content types), Media, and HTML.

This depends on the change made. See Syncing Data.

Yes, you are able to view different breakpoints when viewing a page in the Experience Manager by selecting the icons at the bottom.

You have full control of the CSS and JSX code. We have convenience wrappers for various media queries in the IDE.

We recommend copying the font file URL from a site such as Google Fonts.

You can use our Frontend API to create Content Group, Content Items, and import content in to our CMS. Learn more about our API here.

This will vary from store to store, depending on the volume of data being synced from the platform to Shogun Frontend. See Syncing Data.

There are no rate limits for any of the Shogun Frontend store, however, any headless API calls to the backend commerce platform may have some rate limits.

No. There is a dynamic reference to the "current collection" or "current product". Template Pages are tied to CMS groups and you can tie all the section field values to the dynamic reference rather than a specific content item from that group. Each page will then display data that is specific to the product or collection referenced.

Yes!

Not currently.

Route structure is customizable.

Template Pages have a defined path, such as /products,/collections, or /blogs and the CMS content item would be appended for each generated page.

For static pages that are not tied to a template page, the path is completely customizable, but cannot match the path of an already created page.

Pages will automatically be updated when the section code is saved if the section is on that page. However, those changes are not live until the site is published.

The Shogun Frontend app is rebuilding the entire store every time it is published.

See URL Redirects.

Pages that are not associated with a template can be deleted in the Pages dashboard.

This is done manually in the backend by Shogun.

We will allow users to do this in the future initially only when the section is not associated with a page or template page.

This can be done under Store Settings.

This can be done under Store Settings.

See Finishing Touches.

See Your Homepage.

This is done manually in the backend by Shogun at this time.

We may allow admin users to do this in the future.

This is done in the backend by Shogun at this time.

We will be adding an admin interface in the future.

You should see a toast message with an error log of what failed.

Yes, we do for manual collections.

We don't support ordering based on automated collections yet.

There is a global CSS input in the store settings panel.

See Custom URL Structure.

On both mobile and desktop pages that are in viewport are prefetched with low priority fetch.

When user hovers on desktop and presses on mobile, we do a high priority load if that page is not already in cache from low priority prefetch.

You can use the App component to create your own state management solution or use the Shogun Frontend built-in store if you need a simple store.

We don't support the <> </> shorthand at this time. You need to use <React.Fragment> </React.Fragment>.

To removeItems, variant.id or product.id are not used. When an item is added to the cart, you will get an item.id in the cart which you provide to removeItems.

Currently, all stores are built in production. We do not have a staging environment or the ability to sync stores.

We can configure a local GitHub repo that can be used

The app does not track version control.

You can add it locally, but you still need to notify Shogun which dependency and version you need so that we can add it manually to Frontend, or add them via the Dependency Management interface.

This is not included in the sync and will need to copied and pasted to the Global Styles under the Store Settings panel.

A sections and components folder, and for each section and component, there's a folder with a JSX file (index.jsx), and a CSS file (styles.module.css).

We highly recommend developing locally throughout the build of your store. This allows you to make use of version control and is less error-prone.

It is best to copy/paste to the global styles in the Store Settings panel.

Yes, but this is best avoided when possible as simpler component files will enable us to do automatic upgrades of the dependencies more easily.

Yes.

You can create your own local testing workflow utilizing Storybook and a testing framework of your choosing. At this time we do not have a recommended approach.

We have integrations with both the REST and GraphQL APIs for checkout.

Everything can be handled within Shogun Frontend right up to the point of checkout. Once you click to cart, it hits your platform checkout. There is a domain change.

Yes! Learn more the Frontend API here.

No - We're aware that some API calls we make are to depreciated features, but we're working on our end to update the systems. We plan to have all of these calls updated by end of year, 2022. No action is required on your end.

We recommend launching the Shogun Frontend store alongside your live store and run an A/B test through Google Optimize to split traffic, starting at a low percentage and gradually increasing as you gain confidence in the new site.

When you are ready, Shogun will switch the DNS and all pages and formatting will be controlled using Shogun Frontend moving forward.

This process can take up to 90 seconds to reflect on the product page. See Syncing Data for more information.

See how to code your section to disable the Add to Cart button based on the "live" inventory data here.

Fastly caching and CDN service.

Yes. Fastly has some limits that might affect — among other things — redirects. The limits are the following:

our site will be entirely hosted by a CDN provider, Fastly. Shogun is not in the load path. An e-commerce flash sale, even at a huge scale, is not a huge increase in network volume for a provider like Fastly. If you expect a huge spike, you can notify us, and we'll notify Fastly, but in most cases no action is required.

The way Shopify uses Fastly is different from the way we’re using it. Shopify proxies through Fastly to their data centre in the USA, which adds a long round trip time to APAC. We use Fastly in a way that it goes to Fastly’s edge nodes in APAC and no further, resulting in a much faster response time.

We're running a purge command anytime we publish a new page.

If you want the ability to add random scripts, you can build an "HTML" section that accepts any HTML as an input field.