FAQ

Product / Use Cases

• What is exactly the use case Styla Frontend covers?
  To deliver a full e-commerce website frontend using product data from a “headless“ shop’s API.

• Where is the line between Styla Frontend and a “headless“ shop, for instance, BigCommerce?
  BigCommerce delivers product data, shopping capabilities and handles orders. Styla renders and hosts any content on the website and provides a tool to create non-product pages.

• What’s the difference between Styla Frontend and Styla CMS?
  Styla Frontend is the product that lets you build your complete frontend for a “headless” e-commerce application. An older product, Styla CMS, covers a different use case (including external content on a non-Styla website) and you can find its documentation here.

• How fast Styla Frontend is?
  Most pages score higher than 90 in Google Lighthouse tests. It depends on the amount and type of content. A page with just some HTML and an image or two will usually score close to 98.

• Where is Styla Frontend hosted?
  In AWS, Frankfurt, Germany.

• Is Styla Frontend served over a CDN?
  Yes, it uses AWS' CloudFront.

• What if I need to cover store fronts in multiple languages with Styla Frontend?
  You need a separate BigCommerce and Styla account for each of the languages/locales.

• Is styla Frontend a Progressive Web App?
  Yes, as long as you provide the data needed to configure its manifest.

• Can I use tracking scripts from Google/Hubspot/LinkedIn?
  Yes, you can include them as on any other website.

• How is European GDPR covered?
  Styla on its own only receives the IP and the user-agent which end-users accessing the website use. Styla does not store this data after having processed the request. This changes if you include third-party content like tracking scripts. All the data is hosted in Germany.

• I love the selection of plugins BigCommerce / Shopify offers? Can I use all of them with Styla Frontend?
  Styla Frontend only uses the data it gets over the API. All website content is rendered by Styla only. So if your plugin directly influences the appearance, it won’t be included by Styla. If it influences the product data used by Styla to render pages, it will be included.

• Can Styla push content to external (native) web/mobile apps?
  This is not possible at the moment. But Styla Frontend, being responsive and a PWA, works perfectly fine on different view ports/devices.

• Styla doesn't have built-in blog feature. So what can we do about our blog?
  You can create a page mocking a blog feed with banner modules linking to your blog entries and then recreate each blog entry as a separate page.

Setting your Frontend up

• What do I need to do to serve my website with Styla Frontend?

• How much does it take to launch a Styla Frontend?

• Do I need to write code to create my Styla Frontend?

• Can Styla configure my CSS or build custom modules for me?

• What kind of trainings do you offer?

• What support does Styla provide?

• How do I point another domain to my Styla Frontend?

• How long is the downtime when switching from a previous storefront to Styla Frontend?

Content creation

• How do I manage my page content?

• How do you import existing pages?

• How should I build my website navigation?

• How do I manage my website’s header and footer?

• How do I update my product details or category content in Styla Frontend?

• What is the delay between hitting the “Publish“ button and having a page re-rendered?

• How much freedom do I have in setting URLs?

• How can I display different content on pages using the same templates like product details or category pages?

Appearance

• How to I change my Styla Frontend appearance?

• Is Styla Frontend responsive?

• What web browsers does Styla Frontend support?

• What are the limitations for my layouts on Styla Frontend?

Shopping flow / journey

• Where do orders from Styla Frontend go?

• Can I adapt BigCommerce’s cart and checkout?

• How will look our out-of-stock products on the storefront?

• Can I log in as a BigCommerce client?