Almost EVERYONE who tried headless systems said they saw benefits. Download the state of CMS now!

Storyblok now on AWS Marketplace: Read more

O’Reilly Report: Decoupled Applications and Composable Web Architectures - Download Now

Empower your teams & get a 582% ROI: See Storyblok's CMS in action

Skip to main content
Retail

How Panini frees its teams and reduces time to market with Storyblok

  • Headquarters: Modena, Italy 
  • Technology Stack: Nuxt.js

Panini used to work with a traditional and limited PHP-based CMS, making their projects more complicated. Using Storyblok, Panini can manage many landing pages for their products and companies globally. Panini's team is able to reduce the time it takes to bring their products to market from days to just a few hours. This saved them not only time but also budget in the long run and made it easier for their team to work together. Panini now uses Storyblok for 7 main websites. This includes Calciatori Panini, Panini Adrenalyn, Panini Comics, Panini Digital, Panini Sports Academy, Panini Euro 2020, and their global Panini Group website, available in over 20 languages.

Days to Hours
To Market
Saved
time and cost
Improved
Collaboration
  • Quote from Nicola Cerchiari, Technical Development Manager - Full-Stack Developer at Panini

    I will always struggle to find the one technology that fits all, and I think I found it with Storyblok.

    Nicola Cerchiari
    Nicola Cerchiari
    Technical Development Manager - Full-Stack Developer at Panini

Section titled Main Challenges Found Using a Traditional PHP CMS Main Challenges Found Using a Traditional PHP CMS

Panini previously used a traditional PHP 'Kubernetes-based' CMS infrastructure. They realized over time that this workflow constrained them due to their requirements and website configuration. The CMS was unable to handle more complex projects and the increasing complexity of workflows. Panini's main challenges with their previous CMS included:

  • Complications faced by developers: Entire frameworks had to be built before editors could make any changes
  • Problems with workflow and content production: Annual updates for new product versions required substantial developer effort. This involved complete restyling and the addition of new features or modifications to the site.
  • Difficulty in collaboration: Each new project had to start with an old code base, creating a heavy reliance on developers.
  • A ‘Kubernetes-based’ infrastructure: Projects usually contained around three containers per instance. This made it complicated to manage over time.

Section titled Managing Multiple Global Projects with Storyblok Managing Multiple Global Projects with Storyblok

Panini saw significant improvements in overall optimization and faster performance after implementing Storyblok. This was because fewer complicated technologies were involved. Additionally, Storyblok provided Panini with a range of features to manage their global websites. Some of the benefits Panini found in Storyblok include:

  • Duplicating content from existing projects to new website projects
  • Team collaboration to work all in one place asynchronously
  • Directing website visitors to the appropriate landing page, depending on where they come from, and managing content in one place. For example, one change for twenty versions of the website)
  • A one-container infrastructure reduces the traffic and resources needed

Panini uses Storyblok to support the following sites in over 20 languages: Panini Group, Calciatori Panini, Panini Adrenalyn, Panini Comics, Panini Digital, and Panini Sports Academy.

  • Quote from Nicola Cerchiari, Technical Development Manager - Full-Stack Developer at Panini

    We manage a lot of websites in different languages. Storyblok gives our content editors the power to work easily and move content efficiently.

    Nicola Cerchiari
    Nicola Cerchiari
    Technical Development Manager - Full-Stack Developer at Panini

Section titled Streamlining for Global Content Management Streamlining for Global Content Management

  • Quote from Nicola Cerchiari, Technical Development Manager - Full-Stack Developer at Panini

    This is the biggest benefit: Storyblok separates the content from the presentation layer, which is a big advantage. You can work with two teams at the same time. Whenever you have anything ready, you can just glue them together, and you will be ready to go live.

    Nicola Cerchiari
    Nicola Cerchiari
    Technical Development Manager - Full-Stack Developer at Panini

Storyblok’s lean project structures help speed up their entire workflow and releases. With the shorter technology stack, there is no direct database involvement. This allows the team a hands-off database optimization approach without needing caching optimization.

A screenshot of the Panini Group website

Section titled Cutting Down on Time to Market Cutting Down on Time to Market

Building a project used to take a few days, whereas now, it takes only half a day to clone git-repos and change some configurations to be ready. Non-technical teams are able to then work with it and publish. This makes it even easier for content editors to open a new project or clone a previous one for new pages and campaigns. Depending on the need, they can then insert the content when ready.

  • Quote from Nicola Cerchiari, Technical Development Manager -</br> Full-Stack Developer at Panini

    The biggest strength is that our content editor can start working way before we start and develop new things or design new websites.

    Nicola Cerchiari
    Nicola Cerchiari
    Technical Development Manager -</br> Full-Stack Developer at Panini

Section titled Saving Time and Resources Saving Time and Resources

Storyblok helped reduce budgetary strains as its infrastructure is hosted in the cloud. There was a decrease in resource-spend and no need for a database to be constantly monitored, updated, and optimized, which meant that developers could focus more on innovation. This also helped to reduce the time it took to complete projects and prevented workflow pile-ups. With a new workflow setup, other teams can work more efficiently and focus on creating quality content.

  • Quote from Nicola Cerchiari, Technical Development Manager - Full-Stack Developer at Panini

    We can also test new features and designs in these staging environments. Once we are ready, we can deploy these new features and designs, and the content editor can use them immediately. This makes the workflow much faster.

    Nicola Cerchiari
    Nicola Cerchiari
    Technical Development Manager - Full-Stack Developer at Panini

A screenshot of Calciatori Panini's website

Choose a better way to
manage your content