Connect with us


How To Migrate From WordPress To A Headless CMS — Smashing Journal

Fast abstract ↬

On this article, we’ll take a look at when it is sensible emigrate from a monolithic undertaking to a headless setup and the advantages that include it. Along with a step-by-step information on the way to migrate WordPress to Storyblok Headless CMS, the issues that can come up in the course of the course of and the way to cope with them.

WordPress is probably the most used web site builder on the earth; nearly half of the net has used WordPress to create their web site. It is sensible, as a result of it means that you can shortly create web sites and has a wealthy plugin’s ecosystem that can assist you scale your website.

However expertise is evolving, and there are increasingly more choices that make it simpler to create web sites. Furthermore, they offer us the likelihood to enhance the web site’s efficiency and to have extra management and safety over the appliance.

The preliminary WordPress structure is monolithic, so the consumer interface and knowledge entry are mixed on the identical platform.

Monolithic, Common CMS structure (Giant preview)

For the reason that introduction of the REST API on WordPress, it may be utilized in a headless method, permitting builders to make use of it as a backend and having the front-end in a distinct undertaking.

On this decoupled method, fashions and controllers are bundled on the WordPress facet, dealing with knowledge manipulation and database interplay. In the meantime, the front-end solely interacts with the REST API through an HTTP shopper.

However this additionally has some disadvantages, you continue to have to configure and replace WordPress, make it safe and are depending on their expertise for the event of latest functionalities.

Associated Studying on SmashingMag

For these of you who’re simply beginning within the headless world, these articles will enable you perceive the ins and outs behind it and why everyone seems to be beginning to migrate.

However Why Migrate To A Headless CMS?

Bearing in mind that this text will showcase the way to migrate from WordPress to a Headless CMS, WordPress might be your present setup.

A Headless CMS will give us the liberty to focus solely on the front-end undertaking, with the ability to select the expertise we’re acquainted with, and on the construction of our knowledge. Ultimately, it takes care of the content material administration and the content material supply, in order that we will handle the rendering half.

“A Headless CMS is a system that gives the identical options as a Content material Administration System (CMS) and extra, all uncovered by means of an API.”

Headless CMS architecture

Headless CMS structure (Giant preview)

This kind of setup is very helpful for firms which have a number of websites and wish to scale back prices or simplify processes. A headless structure permits these firms to centralize content material administration in a single administration interface, offering the APIs that might be consumed by the corporate’s totally different net pages.

One other widespread use of a headless structure is to create a front-end undertaking that represents the corporate model. On this method, all of the merchandise that the corporate launches may have the identical feel and look, however each may have its personal content material, managed in the identical administration panel.

Word: This instance might be simply seen on convention web sites reminiscent of JSWorld Convention and VueJS Amsterdam which, being from the identical creators, the front-end undertaking is identical, solely the content material modifications.

Totally different to a CMS like WordPress, in a Headless CMS you might have an administration panel already configured and maintained, and typically additionally hosted, for you. To start out creating content material, you simply have to create an account, log in, and it is possible for you to to create, edit, duplicate and delete your content material, handle customers, translate content material and work with publication workflows, amongst different issues.

A headless CMS will make it simpler for the folks in your staff to know the workflow, whether or not they’re content material creators or entrepreneurs, one thing to remember in case you aren’t the one one who will edit the content material.

Visual editor of a headless CMS

Visible editor of a headless CMS (Giant preview)

It’s value noting that some Headless CMS, not solely focuses on providing you the companies already supplied by a CMS like WordPress. It additionally offers companies reminiscent of picture CDNs to resize or reformat your pictures on the fly, or further safety by means of S3 backups.

Having this setup won’t solely provide you with freedom, safety and luxury, however will even enhance the efficiency of your utility with out third-party companies. Simply by connecting your front-end undertaking through an HTTP shopper and getting the elements and knowledge, you’ll be up and working.

The Advantages Of Going Headless And When It Makes Sense

WordPress’ structure usually doesn’t supply the probabilities we typically want when engaged on a web site, particularly on the subject of optimizing efficiency, probably the most necessary factors when rating our website in a search engine like Google and particularly now that Net Vitals is up and working.

However it’s clear that if now we have a private website that solely we ourselves work on, then it’s not essential to migrate it to a headless setup. Nevertheless, if extra persons are concerned in that undertaking (not simply builders however content material creators or advertising and marketing groups), then we must always think about adopting Headless CMS.

How Can A Headless CMS Assist Us Enhance The Efficiency Of Our Web site And The High quality Of Our Entrance-Finish Venture?

  • By permitting you to develop the front-end in a method that’s fully impartial of the platform the place you edit your content material.

    The expertise you select is your personal selection, in case you wished to improve your undertaking to the newest front-end framework, you wouldn’t be depending on a back-end and will achieve this with out having to rethink migrations.

  • Permitting you to create multiplatform tasks with out having to depend upon totally different administration panels.

    Ultimately, if for an app you want a shorter description than the principle web site, you possibly can at all times make use of a brand new “short_description” discipline and simply symbolize it on the front-end of that particular app.

  • It’s meant to make improvement simpler and simplify the method of making a website, in addition to scaling it.

    By having the front-end fully remoted we will change the visible look of our total utility with out modifying the construction of our content material.

  • All the time providing companies that can enable us to optimize our belongings and the pace of response with which they’re served to us.
    In the end all our knowledge might be delivered by means of CDN networks.

A content material supply community (CDN), is a geographically distributed community of proxy servers and their knowledge facilities. The aim is to supply excessive availability and efficiency by distributing the service spatially relative to end-users.

What If We Are Involved About How It Will Work With Our Model’s Or Firm’s Construction?

  • In addition to supporting cross-platform purposes, it additionally permits us to keep up model consistency.

    Having the front-end as a base undertaking and having multiples areas in a Headless CMS, means that you can have consistency between your merchandise and makes the scalability simpler as a result of now we have much less code to keep up.

  • Though not all headless CMS have this profit, the headless CMS we’re migrating to, Storyblok, has a Visible Editor, which permits creating independence amongst groups.
    The editors or content material creators can entry the panel to edit present content material or create new content material, with the ability to see a preview of the way it will look earlier than publishing. In order that they received’t should contain the event staff on this course of and may do their work extra effectively.

  • It additionally streamlines content material administration by permitting you to arrange your personal content material workflow.
    You may outline the phases {that a} piece of content material should undergo earlier than being printed and, solely when it passes the method efficiently, will probably be printed.

How Can A Headless CMS Save Time In contrast To A Conventional CMS?

  • Caring for sustaining the safety of the platform and updating it in your behalf.
    At any time when there’s a bug or customers require a brand new characteristic, the staff behind your Headless CMS will develop it for you, you simply have to start out utilizing it!
  • Continually enhancing the consumer expertise (UX) and design (UI) for you, in order that content material creators and builders really feel snug creating new fields, elements or pages.
    However not solely on the visible side, however they will even be trying to enhance the efficiency of the database, so that you get your content material immediately and neglect about all of the work that’s concerned.
Monolithic vs Headless
Function Monolithic Headless
Structure Coupled: linked back-end front-end Decoupled: impartial front-end undertaking
Expertise You’ll have to use the one through which the undertaking is developed Freedom to decide on your front-end expertise
Cross-platform Restricted to 1 front-end at a time Connects to any front-end tasks
Content material workflow Restrictive Customized
Safety and updates You are taking care It takes take care of you

Having seen the benefits {that a} headless setup can carry to our undertaking and the individuals who work on it, I feel it’s time to take a look at the steps we have to migrate our undertaking.

What You Want To Hold In Thoughts When Going Headless

As now we have already talked about, Headless CMS enable for a clear separation of considerations between content material creators and builders. On this method (in a Headless CMS), the developer focuses on creating the content material construction, which might be represented within the front-end undertaking, and the editor might be in command of utilizing the elements and filling them with content material within the admin panel.

Kind Of Content material We Can Create In A Headless CMS

1. Varieties of entry or template

Just like Customized Submit Sorts in WordPress however with extra freedom and extensibility on the subject of knowledge sorts and editors.

While you go to create a brand new content material entry in your dashboard, you anticipate to have the ability to select what kind it is determined by the state of affairs. For instance, if in case you have a web site with a weblog you’ll want to have a number of forms of templates, one for pages with listings or dynamic content material known as “web page” and one for every weblog entry “submit”.

Relying on the headless CMS you might have chosen, the identify will differ however the idea is identical. In Storyblok these kind of entities are known as Content material Kind. “Content material Sorts” outline the kind of content material entry and may maintain the fundamental fields in your content material entries. By default, now we have a “Web page” content material kind.

2. Reusable elements

In a Headless CMS, you possibly can create, along with Content material Sorts, nested elements and reuse them between content material sorts and different elements. In Storyblok, one of these element — as you could have observed from its identify — is known as Blok.

To make use of them in a Content material Kind reminiscent of a web page, you’ll need to create a discipline within the schema of kind blocks. This discipline means that you can add nested elements to your web page whereas including content material.

However, in precept, we won’t want such elements in the course of the migration. It merely offers you the pliability to create sturdy and dynamic purposes with out having to contain the developer.

For instance, when a member of the advertising and marketing staff needs so as to add a brand new Hero to the About us web page, if the Hero element was created as nested and the web page had a Blocks discipline, the advertising and marketing particular person may add the Hero with out having to contain the developer.

Rendering The Information Coming From The Headless CMS

As we’re defining the construction of our content material within the Headless CMS panel, now we have to think about which framework we wish to create our front-end undertaking with and which HTTP shopper we’ll use.

When selecting a framework now we have to take a number of elements under consideration:

Are my staff and I’m acquainted with this expertise?

Does it enable me to render my content material in the kind of rendering my undertaking wants?

Does it have plugins or modules that facilitate integration with the Headless CMS I’m utilizing?

Normally, a static website might be adequate and can at all times be probably the most economical and high-performance reply. So, you simply should search for a static website generator for the expertise you might be acquainted with, for instance, Nuxt for Vue or Subsequent for the React library.

Connecting these two issues, a Headless CMS and a static website builder are thought of as a set of net improvement finest practices targeted on offering the best efficiency, safety and lowest value. This structure is also called Jamstack. It’s an structure designed to make the net quicker, safer and simpler to scale. It builds on lots of the instruments and workflows which builders love, and which carry most productiveness.

By making use of the stylish frameworks, you’ll be assured of an integration information with the Headless CMS you’re going to work with, and most of them have already a module or bundle that means that you can get hold of info from the API and in lots of instances lengthen it.

The one factor left so that you can do is to outline the construction of your elements regarding how you might have structured the info in your Headless CMS and automate the content material publishing course of. For instance, utilizing the Webhooks that the Headless CMS offers you with, it is possible for you to to start out a construct course of in your favorite internet hosting by its construct hooks as soon as the content material has been printed.

Quantity Of Time You’ll Want

As with all migration, the time required will at all times rely proportionally on the complexity of your undertaking. If we’re speaking a few widespread WordPress website you’ll solely have to migrate the Submit sorts that you’ve got outlined or that comes by default in it, reminiscent of Pages, Posts and Classes, and their content material.

If, however, you might have custom-made your undertaking with a number of plugins, you’ll have to develop them by means of the front-end undertaking or utilizing those supplied by your Headless CMS. For instance, if we’re web optimization aware and subsequently make use of Yoast web optimization on WordPress, we may have the Area-Kind web optimization plugin in Storyblok to assist us within the transition, however we’ll nonetheless should develop our sitemap within the front-end with a information to assist us.

Ultimately, all of the burden of improvement will fall on the front-end undertaking, as organising the Headless CMS won’t take that a lot time.

However let’s cease speaking and let’s check out it!

Steps To Migrate Our Content material From WordPress To Storyblok

The migration will consist of 4 steps, from the creation of an area in our new Headless CMS Storyblok to the illustration of the migrated content material in our front-end undertaking, which we’ll see intimately beneath and through which I’ll depart you sources to make the migration simpler for you.

Let’s get began!

1. Creating A House In Storyblok

With a purpose to create an area in Storyblok, you first have to have an account. To do that, you’ll need to pick the plan that fits you finest.

Go to the Pricing web page and begin with the plan that most closely fits your wants or strive the free plan for testing.

Create your account, and it is possible for you to to entry the panel.

Create an account form in Storyblok

Create an account type in Storyblok (Giant preview)

Select ‘Create a brand new house’ and let’s get began!

Creating a new space in Storyblok

Creating a brand new house in Storyblok (Giant preview)

House is a content material repository. Consider it as a spot to maintain all of the content material associated to 1 undertaking. Every house has its personal elements, knowledge sources, belongings, environments, domains, collaborators and permissions.

Take a while to discover the sections on the left sidebar. Begin by searching the next:

  • Content material, this would be the folder the place the content material might be saved, the place the advertising and marketing staff will spend most of their time.
  • Belongings, the place all the photographs might be saved, which you’ll be able to then get by means of the CDN service, optimized and of any dimension.
  • Parts, the place you’ll create the Content material sorts and Nested elements.
  • Settings, the part the place it is possible for you to to configure the info of your house in addition to the languages of your utility, the workflows you need your content material to observe earlier than being printed, consumer permissions, and so on. Let’s say that this space would be the one associated to the IT staff of the undertaking.

Components section in the Storyblok space

Parts part within the Storyblok house (Giant preview)

In case you nonetheless wish to discover each possibility on the dashboard earlier than diving into the migration, I like to recommend looking at Understanding the UI by Storyblok.

Now that you already know a bit concerning the Storyblok ecosystem, it’s time to outline what the content material of our utility will appear to be.

2. Defining Fashions

Emigrate WordPress content material to Storyblok, the following step is to create the schemas that outline the WP knowledge construction by creating Submit Sorts within the Storyblok house.

Let’s begin with pages and posts (the principle Submit Sorts in any WP website), which we’ll name web page and submit in Storyblok.

The schema of pages in WP accommodates the fields: title, slug, featured picture, date, and content material.

Word: To see all of the fields contained in a Submit Kind go to the schema at WP REST API schema references.

What it is advisable know is that, by default, any Content material Kind in Storyblok may have some fields already outlined for you, reminiscent of Identify, Slug, Tags, First printed date, and so forth.

Default fields for Content Type in Storyblok

Default fields for Content material Kind in Storyblok (Giant preview)

These fields may very well be used emigrate the content material from WP. You’ll solely want to increase it by including featured_image and content material within the Web page Content material Kind.

Go to the Parts part in your house, click on on the web page created by default, take away the physique discipline and add featured_image as kind Belongings > Pictures and content material as Wealthy-text.

Content Type Page fields definition in Storyblok Components section.

Content material Kind Web page fields definition in Storyblok Parts part. (Giant preview)

As soon as the web page schema is prepared, let’s transfer on to the submit. For the Submit Content material Kind, it’s mandatory to incorporate extra info, reminiscent of featured_image, excerpt, content material, and relationships to different sorts reminiscent of Authors or Classes.

Content Type Post fields definition in Storyblok Components section

Content material Kind Submit fields definition in Storyblok Parts part (Giant preview)

Since Authors and Classes will even have their very own content material, go to the Content material part within the sidebar and create a few folders known as authors and classes.

Every of the folders will need to have a default Content material Kind related. To do that, within the Parts part, create Creator and Class as new Content material Sorts, after which affiliate the Content material Kind relative to every folder by clicking on the three dots on the correct of the folder and choosing Settings.

Selecting a Content Type by default for the Categories folder in the Storyblok space.

Choosing a Content material Kind by default for the Classes folder within the Storyblok house. (Giant preview)

On this method, within the Submit Content material Kind you possibly can add a Single-Possibility or Multi-Choices discipline with supply Tales and level to the folder created for every discipline:

  • Authors
    This specifies the folder the place they’re situated authors/.
  • Classes
    This specifies the folder the place they’re situated classes/.

Multi-Options categories field for Content type Post

Multi-Choices classes discipline for Content material kind Submit (Giant preview)

Word: If you wish to know extra about this relationship, take a look on the article Authors and Articles Relationship.

Now that you’ve got seen the way to create a few Content material Sorts and the way to create relationships between them, you’ll have to outline the remainder of the fashions following the identical steps.

Including A Content material Kind: International

And also you ask your self, what concerning the content material that every one my pages will share? Just like the navigation menu, footer, and different widespread parts?

Don’t fear, Storyblok has already thought of that and gives us a easy information to outline our international parts dynamically. It exhibits us the way to create a international Content material Kind and the way to use it within the Content material part.

3. Migrating The Content material

Now it’s time to start out migrating the content material you might have saved. To entry WP content material it is advisable entry the REST JSON API. Entry the trail /wp-json, if the undertaking is deployed, or ?rest_route=/ if native.

In case neither of the 2 routes works, examine the HTML of your web page for a hyperlink within the head with rel="", as indicated within the WP discovery information, and get the proper one.

<hyperlink rel="" href="https://localhost/your-site/index.php?rest_route=/">

To assist us in the course of the migration, the Storyblok builders have supplied us with a plugin that can save us a whole lot of work. This plugin is known as wordpress-importer, on it, it’s attainable to outline the equal Content material Kind in Storyblok for the WP Submit kind to be migrated, and it’ll push it to our house and migrate the photographs to our Belongings part for us.

Word: Utilizing this script requires node ≥14.0.0 as a result of it’s utilizing optionally available chaining.

Creating The Migration Script

The very first thing to do is to clone the repository. Then, set up the NPM packages, utilizing npm set up or yarn, and create a file within the root of the undertaking as migrateWPtoStoryblok.js. With a purpose to run the script you want a script in bundle.json to run it, add:

"migrate": "node ./migrateWPtoStoryblok.js"

As soon as every thing is prepared, it’s time to start out defining the script following the README specs. And, as you possibly can see, the following factor that might be wanted is to seek out the Space_id and the OAuth token to connect with the Storyblok house.

  • The Space_id is within the Settings part of the sidebar, as quickly as you click on on it, you will note it on the correct facet.
  • To generate the OAuth token, it is advisable go to the highest of the sidebar, click on on the little arrow proper subsequent to the Storyblok brand, and go to My Account. If we scroll down we’ll see the Private entry tokens part, generate one, and replica it.

When you might have obtained each secrets and techniques, you possibly can add them to the start of the script together with the URL of the JSON API of your undertaking:

import { Wp2Storyblok } from './index.js'

const wp2storyblok = new Wp2Storyblok('', {
  token: 'storyblok-oauth-token', // My Account > Private entry tokens
  space_id: 'space-id', // Settings

As described in earlier sections, the Web page Content material Kind in Storyblok is the equal of the Submit Kind in WP pages. Within the code block beneath, you’ll see the place you’ll have to specify every.

And, as soon as the Submit Kind and Content material Kind are outlined, it’s time to specify the identify of the fields used on this entity kind in WP and the equal identify in Storyblok, within the schema_mapping possibility.

import { Wp2Storyblok } from './index.js'

const wp2storyblok = new Wp2Storyblok('', {
  // ... Secrets and techniques
  content_types: [
      name: 'pages', // Post type in WP
      new_content_type: 'page', // Equivalent Content type in Storyblok
      folder: '', // OPTIONAL: To save all the content of the same type in a specific folder
      schema_mapping: {
        "title": "name", // "Field in WP": "Field in Storyblok"

Word: For the migration to work accurately, be sure that the permalinks are chosen by the identify of the entry and never as easy. In any other case, the script won’t create the parent-child relationship between pages.

Inside the schema_mapping you possibly can outline a number of forms of fields, these might be:

  • A easy discipline, reminiscent of title.
  • A sub-property of a discipline, like on this case the URL of the characteristic picture.
    Word: The plugin itself takes care of migrating the photographs to the Storyblok house through the related URL in hyperlinks.wp:featuredmedia.0.
  • A discipline migrated to a nested block in Storyblok.

    Think about you wish to create a element in Storyblok to outline your website’s wealthy textual content so that every one submit sorts utilizing it have the identical type and choices.

    For that, you should use the object format and specify the identify of the sector within the Storyblok mannequin beneath the discipline property, the identify of the element you wish to retailer inside that discipline, and the identify of the discipline contained in the element the place the content material might be migrated.

import { Wp2Storyblok } from './index.js'

const wp2storyblok = new Wp2Storyblok('', {
  // ... Secrets and techniques
  content_types: [
      // ... Post type WP:Storyblok
      schema_mapping: {
        "title": "name", // "Field in WP": "Field in Storyblok"
        "_links.wp:featuredmedia.0": "content.preview_image", // Using the dot notation you can define subproperties.
        // Using nested blocks in Storyblok
        "content": {
          field: 'content.body_items', // Field name in Storyblok
          component: "rich-text", // Component name inside the above field
          component_field: "content" // Field name inside the component where you want to migrate the content

Entry Kind Web page

Now that you know the way to outline the sector sorts, for the web page schema, it could appear to be within the code block beneath.

The plugin will handle the parent-child relationship between pages by making a folder in Storyblok beneath the mum or dad’s slug and associating the mum or dad as the house of that folder.

Moreover, if the content material discipline accommodates pictures, the plugin will even migrate it for you!

  identify: 'pages', // Identify of the submit kind in WP
  new_content_type: 'web page', // Identify of the Content material Kind in Storyblok
  schema_mapping: {
    "date": "first_published_at",
    "title": "identify",
    "slug": "slug",
    "_links.wp:featuredmedia.0": "content material.featured_image",
    "content material": "content material.content material",

Entry Kind Submit

Posts have a schema much like pages however, on this case, to retailer them in a folder you could outline the identify of the folder beneath the entry kind:

  identify: 'posts', // Submit kind identify in WP
  new_content_type: 'submit', // Content material Kind identify in Storyblok
  folder: 'articles', // Vacation spot folder identify in Storyblok
  schema_mapping: {
    "date": "first_published_at",
    "title": "identify",
    "slug": "slug",
    "_links.wp:featuredmedia.0": "content material.featured_image",
    "excerpt": "content material.excerpt",
    "content material": "content material.content material",
Entry Kind Class

And as soon as the schema for posts has been outlined, it is sensible to outline the schema for the classes in order that they are often related as described within the earlier part.

With a purpose to outline the folder that accommodates them as classes and never as class, their default identify, you could go to the Permalinks possibility within the WordPress admin and alter the Classes base choice to classes. Then the multi-option discipline of the Submit entries would be the one which has the connection with the corresponding classes.

Word: These steps are the identical as these to be adopted for migrating authors and linking them to articles.

  identify: 'classes', // Identify of the submit kind in WP
  new_content_type: 'class', // Identify of the Content material Kind in Storyblok
  // By default might be contained by a folder known as Class (change it within the Permalinks possibility in WP)
  schema_mapping: {
    "identify": "identify",
    "slug": "slug",
    "description": "content material.description",
    "mum or dad": "content material.mum or dad",
Full Remaining Script

The code beneath would be the ensuing migration script from a WP undertaking with the fundamental sorts to the Storyblok house we had created.

import { Wp2Storyblok } from './index.js'

const wp2storyblok = new Wp2Storyblok('', {
  token: '',
  space_id: 34234,
  content_types: [
      name: 'pages', // Name of the post type in WP
      new_content_type: 'page', // Name of the Content Type in Storyblok
      schema_mapping: {
        "date": "first_published_at",
        "title": "name",
        "slug": "slug",
        "_links.wp:featuredmedia.0": "content.featured_image",
        "content": "content.content",
      name: 'categories', // Name of the post type in WP
      new_content_type: 'category', // Name of the Content Type in Storyblok
      // By default will be contained by a folder called Category (change it in the Permalinks option in WP)
      schema_mapping: {
        "name": "name",
        "slug": "slug",
        "description": "content.description",
        "parent": "content.parent",
    // Add authors as categories.
      name: 'posts', // Name of the post type in WP
      new_content_type: 'post', // Name of the Content Type in Storyblok
      folder: 'articles', // Name of the destination folder in Storyblok
      schema_mapping: {
        "date": "first_published_at",
        "title": "name",
        "slug": "slug",
        "_links.wp:featuredmedia.0": "content.featured_image",
        "excerpt": "content.excerpt",
        "content": "content.content",
    // More schemas...


4. Create A Entrance-Finish Venture

Now that the content material is already saved within the Storyblok dashboard, it’s time to attach the Entrance-end undertaking to Storyblok.

No matter your framework or JS library, Storyblok offers the JavaScript shopper that can enable you with the combination. As well as, in case you might be utilizing a selected framework, you’ll discover different packages that can ease the way in which, like in Nuxt the storyblok-nuxt module.

This JavaScript API will even embrace a bridge between Storyblok and your Entrance-end utility. The bridge is answerable for speaking through iframe with Storyblok to inform the enhancing interface which element to open when the consumer clicks on it.

Here’s a checklist of tutorials you will discover on Storyblok to attach your Entrance-end undertaking.

Word: In case you don’t discover your expertise amongst them, don’t fear there are lots of different tutorials on the Storyblok web site, seek for yours within the search engine, and in case you don’t discover one I encourage you to contact them, and you’ll assist many extra folks!

5. Host Your Entrance-Finish Venture And Automate Deploy

As soon as your undertaking is prepared to enter manufacturing, you select a internet hosting supplier and hyperlink your repository for simple deployment, then you definitely ask your self:

How do I redeploy my static website if I publish an entry on Storyblok?

The reply could be very easy: through the use of the webhooks supplied by Storyblok and the construct hooks of your internet hosting.

To present you an actual instance, you possibly can create construct hooks URLs in Netlify throughout the deployment part; the URL created for Storyblok within the construct hooks will go within the Settings → Webhooks → Story printed & unpublished discipline within the Storyblok house.

Storyblok webhooks field

Storyblok webhooks discipline (Giant preview)

Guides And Instruments We Have Used Throughout Migration

Let’s recap the hyperlinks which have helped within the migration of the content material and those who helped to know the functioning of the REST API and the headless CMS to which you might be migrating.

WP REST API Documentation Wanted


Migrating To Storyblok

Basic Data
International Parts
Webhooks And Construct Hooks
Scripts And Packages



After studying this text you should have what it is advisable perceive why a headless setup will enhance your undertaking, the way to migrate out of your WordPress undertaking to a headless CMS like Storyblok and the way to maintain enhancing and lengthening your undertaking.

As you might have seen, the probabilities of a headless setup are limitless. After the migration, you should have monumental flexibility to scale your undertaking, enhance its efficiency and web optimization, enhance the productiveness of the event staff and keep on high of the newest tendencies.

Everyone seems to be beginning to migrate and there’s increasingly more content material and scripts that make it simpler. What are you ready for emigrate your WordPress?

Smashing Editorial
(vf, il)

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *