Web design
Storyblok in SIDECUBE digital projects
Storyblok is useful when the team wants visual editing, reusable components and quick frontend separated from CMS.
Match
When we use Storyblok
The technology is chosen after we understand the objective, the rhythm of the team, the level of administration and how much the project needs to increase.
- Embarkable websitesWe define what can change the editor and what must be kept consistent in the structure of the page.
- Marketing teamsWe prepare pages and components that can be updated at the pace of offers and campaigns.
- Landing pagesWe concentrate the message, evidence and form around a single action required of the visitor.
- Modular contentWe build pages from reusable sections, with rules that maintain hierarchy and consistency.
Uses
What can we build with Storyblok
We only use technology where it helps the project to be faster, easier to manage or safer to expand.
Deliverables
What goes into implementation
Accurate delivery depends on the project, but we keep every documented, tested and prepared implementation for maintenance.
- Modes of content
- Connected components
- Editorial Workflow
- Preview
- Administration documentation
Connected services
Storyblok usually appears in these projects
Choose the service that best describes your need, then determine if this technology is the right choice.
Recommended pages
Services, technologies and guides related to this technology and its use in projects.
Specialised services
Close technologies
Industries
Guides
Frequently Asked Questions
Before you choose technology
Uses, integration and costs for Storyblok.
01 / Match
When that choice makes sense
What projects do you consider Storyblok for?
Suitable situations: Administrative websites; Marketing teams; Landing pages; Modular content. The choice shall be confirmed after analysis of existing requirements, team and solutions.
What uses do you propose for Storyblok?
Relevant examples are: Visual editor; Content blocks; Commercial pages; CMS for marketing. We determine what serves your objective and what would add complexity without a clear benefit.
02 / Implementation
Integration and deliverables
Can the solution be integrated into an existing project?
We're checking page structure, editing and integration. If we replace an existing solution, we inventory the content and URLs to be kept before migration.
What could include implementation?
For Storyblok, we can define in the offer: Content Models; Connected Components; Editorial Workflow; Preview; Administration Documentation. We confirm the deliverables after verification of compatibility and available access.
03 / Operation
Verification and costs
How do you check that implementation works?
We're testing the pages and editing the content, where there's administration, on the mobile and desktop. We are checking forms, resources and speed in the context of the site, not just in an isolated demonstration.
What costs should be foreseen in the long term?
We separate the development of hosting, licenses, editorial services and maintenance. The mode of administration and the pace of change matter as much as the initial implementation.