Streamlining Website Production Processes with Storyblok

Fortnox AB migrated from WordPress to Storyblok. The result — a minimal learning curve, efficient workflows and streamlined editor independence. As Sweden's leading business platform, Fortnox needed a website that could handle its goals. With Storyblok as its CMS, its developers and editors are empowered with a simple and easy-to-use system.

Section titled Monolithic roadblocks that hinder growth Monolithic roadblocks that hinder growth

Before Fortnox started using Storyblok as their CMS, they were using WordPress — a monolithic CMS. This led to several roadblocks that made it difficult to run their website, based on:

• Increased workload on the development team: This made it hard to launch campaigns on time and caused them to miss out on opportunities.
• The outdated and inflexible setup: Causing technical issues along the way to predict which parts of the site might be accidentally altered by edits
• The monolithic infrastructure: Making it too rigid for the teams to use effectively and efficiently in the long run.

Section titled Finding Storyblok and making the switch Finding Storyblok and making the switch

Fortnox began their search for a new CMS solution and contacted a consultant firm for help in the decision-making process. The firm offered several options that met Fortnox's requirements for a headless CMS.

Their exhaustive search ended with Storyblok as the best fit thanks to:

• The ease of use for all teams in terms of the user-experience with the Visual Editor
• Being a simple and powerful system to centralize all content in one system
• The streamlined workflows for developers, editors, and designers to work closely yet independently within an interface that supported their shared goals

Section titled Settling into the new system Settling into the new system

Fortnox uses Storyblok to power its main marketing website and the content within, some fetched via API from other platforms. This includes:

• Product data used in the checkout process, such as descriptions and images
• Company-specific metrics are provided to users upon login
• Curated blog articles organized by Storyblok’s tagging system

Another Storyblok feature that Fortnox is using actively are Content Types. Content Types allow developers to provide editors with a standardized format to create pages. For example, the developer team can set up a template product page that uses the exact same component every time. Then editors can use this structure to create customized yet consistent content. This makes production easier and faster, while also presenting a polished result.

Moreover, Storyblok is able to support new users, with a minimal learning curve. In fact, Fortnox found that users were mostly able to adjust to the CMS just by using it and exploring themselves. As a result, they found that new team members only required a brief introduction instead of a formalized training session.