@storyblok/react

@storyblok/react

The React plugin you need to interact with Storyblok API and enable the Real-time Visual Editing Experience. This package helps you integrate Storyblok with React along with all types of React based frameworks like Next.js, Remix etc. This SDK also includes the support for React Server Side Components.

🚀 Usage

If you are first-time user of Storyblok, read the Getting Started guide to get a project ready in less than 5 minutes.

Installation

Install @storyblok/react:

npm install @storyblok/react
// yarn add @storyblok/react

⚠️ This SDK uses the Fetch API under the hood. If your environment doesn't support it, you need to install a polyfill like isomorphic-fetch. More info on storyblok-js-client docs.

From a CDN

Install the file from the CDN:

<script src="https://unpkg.com/@storyblok/react"></script>

Initialization

Register the plugin on your application and add the access token of your Storyblok space. You can also add the apiPlugin in case that you want to use the Storyblok API Client:

import { storyblokInit, apiPlugin } from "@storyblok/react";

/** Import your components */
import Page from "./components/Page";
import Teaser from "./components/Teaser";

storyblokInit({
  accessToken: "YOUR_ACCESS_TOKEN",
  use: [apiPlugin],
  // bridge: false,
  // apiOptions: {},
  components: {
    page: Page,
    teaser: Teaser,
  },
});

Note: This is the general way for initalizing the SDK, the initialization might be a little different depending upon the framework. You can see how everything works according to the framework in their respective sections below.

Add all your components to the components object in the storyblokInit function.

That's it! All the features are enabled for you: the Api Client for interacting with Storyblok CDN API, and Storyblok Bridge for real-time visual editing experience.

You can enable/disable some of these features if you don't need them, so you save some KB. Please read the "Features and API" section

Region parameter

Possible values:

• eu (default): For spaces created in the EU
• us: For spaces created in the US
• cn: For spaces created in China

Full example for a space created in the US:

import { storyblokInit, apiPlugin } from "@storyblok/react";

storyblokInit({
  accessToken: "YOUR_ACCESS_TOKEN",
  use: [apiPlugin],
  apiOptions: {
    region: "us",
  },
  components: {},
});

Note: For spaces created in the United States or China, the region parameter must be specified.

@storyblok/react does three actions when you initialize it:

• Provides a getStoryblokApi object in your app, which is an instance of storyblok-js-client.
• Loads the Storyblok Bridge for real-time visual updates.
• Provides a storyblokEditable function to link editable components to the Storyblok Visual Editor.

For every component you've defined in your Storyblok space, call the storyblokEditable function with the blok content:

import { storyblokEditable } from "@storyblok/react";

const Feature = ({ blok }) => {
  return (
    <div {...storyblokEditable(blok)} key={blok._uid} data-test="feature">
      <div>
        <div>{blok.name}</div>
        <p>{blok.description}</p>
      </div>
    </div>
  );
};

export default Feature;

Where blok is the actual blok data coming from Storyblok's Content Delivery API.

Note: The storyblokEditable function works the same way for all the frameworks and components created.

Getting Started

This SDK provides you the support to work with React and all React Frameworks such as Next.js, Remix etc. Depending upon these different frameworks and versions, the way to use the SDK and the functionalities it provides differ.

Below is the guide and examples on how to use it with different frameworks -

React

The initalization remains the same when you work with React. You can intialze the SDK in the index.js file. Please refer to the 'Initialization' section above to read more.

Fetching Content and Listening to Storyblok Visual Editor events

Use useStoryblok to fetch the content as well as enable live editing. You need to pass the slug as the first parameter, apiOptions as the second parameter, and bridgeOptions as the third parameter, which is optional if you want to set the options for the bridge by yourself. Check the available apiOptions (passed to storyblok-js-client) and bridgeOptions (passed to the Storyblok Bridge).

import { useStoryblok, StoryblokComponent } from "@storyblok/react";

function App() {
  const story = useStoryblok("react", { version: "draft" });

  if (!story?.content) {
    return <div>Loading...</div>;
  }

  return <StoryblokComponent blok={story.content} />;
}

export default App;

StoryblokComponent renders the route components dynamically, using the list of components loaded during the initialization inside the storyblokInit function.

This is how you can pass the Bridge options as a third parameter to useStoryblok:

useStoryblok(
  story.id,
  { version: "draft", resolveRelations: ["Article.author"] },
  {
    resolveRelations: ["Article.author"],
    preventClicks: true,
  }
);

Check out our React Boilerplate here, or read on how to add Storyblok to React in 5 mins here You can also take a look at the React Playground in this repo.

Next.js using App Router - Live Editing support

The components in the app directory are by default React Server Side Components, which limits the reactivity. You can enable Storyblok Visual Editor's live editing with React Server Components by rendering them inside a wrapper (StoryblokPovider) on the client. The SDK allows you to take full advantage of the Live Editing, but the use of Server Side Components is partial, which will be still better than the older Next.js approach performance-wise. The next section explains about how to use complete server side approach.

The SDK has a special module for RSC. Always import @storyblok/react/rsc while using Server Components.

1. Initialize

In app/layout.jsx, call the storyblokInit function, but without loading the component list (we will do that on the client). Wrap your whole app using a StoryblokProvider component (this provider is created in the next step) :

import { storyblokInit, apiPlugin } from "@storyblok/react/rsc";
import StoryblokProvider from "../components/StoryblokProvider";

storyblokInit({
  accessToken: "YOUR_ACCESS_TOKEN",
  use: [apiPlugin],
});

export default function RootLayout({ children }) {
  return (
    <StoryblokProvider>
      <html lang="en">
        <body>{children}</body>
      </html>
    </StoryblokProvider>
  );
}

2. Create StoryblokProvider and Import your Storyblok Components

Create the components/StoryblokProvider.jsx file. Re-initalize the connection with Storyblok (this time, on the client) using storyblokInit, and import your Storyblok components:

/** 1. Tag it as a client component */
"use client";
import { storyblokInit, apiPlugin } from "@storyblok/react/rsc";

/** 2. Import your components */
import Page from "../components/Page";
import Teaser from "../components/Teaser";

/** 3. Initialize it as usual */
storyblokInit({
  accessToken: "YOUR_ACCESS_TOKEN",
  use: [apiPlugin],
  components: {
    teaser: Teaser,
    page: Page,
  },
});

export default function StoryblokProvider({ children }) {
  return children;
}

Note: it's necessary to re-initialize here as well, as to enable the live editing experience inside the Visual Editor you need to initialize the lib universally (client + server).

3. Fetch Content and Render Components

The getStoryblokApi function, which is an instance of storyblok-js-client can be used to fetch the data from the Storyblok API. This should be imported from @storyblok/react/rsc. You can render the content of your route with the StoryblokStory component, which will automatically handle the Visual Editor live events when editing the story. In app/page.jsx, use them as follows:

import { getStoryblokApi } from "@storyblok/react/rsc";
import StoryblokStory from "@storyblok/react/story";

export default async function Home() {
  const { data } = await fetchData();

  return (
    <div>
      <StoryblokStory story={data.story} />
    </div>
  );
}

export async function fetchData() {
  const storyblokApi = getStoryblokApi();
  return storyblokApi.get(`cdn/stories/home`, { version: "draft" });
}

StoryblokStory keeps the state for thet story behind the scenes and uses StoryblokComponent to render the route components dynamically, using the list of components loaded during the initialization inside the storyblokInit function. You can use the StoryblokComponent inside the components to redner the nested components dynamically.

Note: To use this approach (with getStoryblokApi), you need to include the apiPlugin module when calling storyblokInit function. If you don't use apiPlugin, you can use your preferred method or function to fetch your data.

To try this setup, take a look at the Next 13 Live Editing Playground in this repo.

Next.js using App Router - Full React Server Components

If you want to use the Next.js app directory approach, and React Server Components exclusively with everything on the server side, follow this approach.

The SDK has a special module for RSC. Always import @storyblok/react/rsc while using Server Components.

Limitation - Real-time editing won't work if all the components are rendered on the server. Although, you can see the changes applied in the Visual Editor whenever you save or publish the changes applied to the story.

1. Initialize and Import your Storyblok Components

The initialzation remains the same here as well. Please refer to the above section about "Initialization" for more information about storyblokInit function. In app/layout.jsx, call the storyblokInit function and use the new StoryblokBridgeLoader component to set up the Storyblok bridge. This Bridge Loader can be imported from @storyblok/react/bridge-loader:

import { storyblokInit, apiPlugin } from "@storyblok/react/rsc";
import StoryblokBridgeLoader from "@storyblok/react/bridge-loader";

import Page from "../components/Page";
import Teaser from "../components/Teaser";

storyblokInit({
  accessToken: "YOUR_ACCESS_TOKEN",
  use: [apiPlugin],
  components: {
    teaser: Teaser,
    page: Page,
  },
});

export default RootLayout({ children }) =>{
  return (
    <html lang="en">
      <body>{children}</body>
      <StoryblokBridgeLoader options={bridgeOptions} />
    </html>
  );
}

As the name says, StoryblokBridgeLoader loads the bridge on the client. It helps you see the dotted lines and allows you to still click on the components inside the Visual Editor to open their schema. You can pass the bridge options using the options prop.

2. Fetch Content and Render Components

The getStoryblokApi function, is an instance of storyblok-js-client can be used to fetch the data from the Storyblok API. This is imported from @storyblok/react/rsc. Go to the route you want to fetch data from and use it as follows:

import { getStoryblokApi, StoryblokComponent } from "@storyblok/react/rsc";

export default async function Home() {
  const { data } = await fetchData();

  return (
    <div>
      <h1>Story: {data.story.id}</h1>
      <StoryblokComponent blok={data.story.content} />
    </div>
  );
}

export async function fetchData() {
  const storyblokApi = getStoryblokApi();
  return storyblokApi.get(`cdn/stories/home`, { version: "draft" });
}

Note: To use this approach (with getStoryblokApi), you need to include the apiPlugin module when calling storyblokInit function. If you don't use apiPlugin, you can use your preferred method or function to fetch your data.

StoryblokComponent renders the route components dynamically, using the list of components loaded during the initialization inside the storyblokInit function. To try it, take a look at the Next 13 RSC Playground in this repo.

Next.js using Pages Router

In this section, we'll see how to use the React SDK with the pages directory approach.

The initalization remains the same when you work with Next.js. You can intialze the SDK in the _app.js file. Please refer to the 'Initialization' section above to read more.

1. Fetching Content

The SDK provides a getStoryblokApi object in your app, which is an instance of storyblok-js-client. This can be used to fetch the content from Storyblok. You can use it in functions like getStaticProps, getStaticPaths, getServerSideProps etc.

import { getStoryblokApi } from "@storyblok/react";

// At the required place
const storyblokApi = getStoryblokApi();
const { data } = await storyblokApi.get("cdn/stories", { version: "draft" });

Note: To use this approach, you need to include the apiPlugin module when calling storyblokInit function. If you don't use apiPlugin, you can use your preferred method or function to fetch your data.

2. Listening to Storyblok Visual Editor events

The SDK also provides you with the useStoryblokState hook. It works similarly to useStoryblok for live editing, but it doesn't fetch the content. Instead, it receives a story object as the first parameter. You can also pass the Bridge Options as the second parameter.

import { useStoryblokState, StoryblokComponent } from "@storyblok/react";

export default function Home({ story: initialStory }) {
  const story = useStoryblokState(initialStory);

  if (!story.content) {
    return <div>Loading...</div>;
  }

  return <StoryblokComponent blok={story.content} />;
}

In this case, the story is being passed as a prop that can be coming from where the story is being fetched. A complete example would look like this-

import {
  useStoryblokState,
  getStoryblokApi,
  StoryblokComponent,
} from "@storyblok/react";

export default function Home({ story: initialStory }) {
  const story = useStoryblokState(initialStory);

  if (!story.content) {
    return <div>Loading...</div>;
  }

  return <StoryblokComponent blok={story.content} />;
}

export async function getStaticProps({ preview = false }) {
  const storyblokApi = getStoryblokApi();
  let { data } = await storyblokApi.get(`cdn/stories/react`, {
    version: "draft",
  });

  return {
    props: {
      story: data ? data.story : false,
      preview,
    },
    revalidate: 3600, // revalidate every hour
  };
}

StoryblokComponent renders the route components dynamically, using the list of components loaded during the initialization inside the storyblokInit function.

Check out the code for the first part of our Next.js + Storyblok Ultimate Tutorial. Or you can also read on how to add Storyblok to a Next.js project in 5 minutes here

Features and API

You can choose the features to use when you initialize the plugin. In that way, you can improve Web Performance by optimizing your page load and save some bytes.

Storyblok API

You can use an apiOptions object. This is passed down to the storyblok-js-client config object:

storyblokInit({
  accessToken: "YOUR_ACCESS_TOKEN",
  apiOptions: {
    // storyblok-js-client config object
    cache: { type: "memory" },
  },
  use: [apiPlugin],
  components: {
    page: Page,
    teaser: Teaser,
    grid: Grid,
    feature: Feature,
  },
});

If you prefer to use your own fetch method, just remove the apiPlugin and storyblok-js-client won't be added to your application.

storyblokInit({});

Storyblok Bridge

If you don't use registerStoryblokBridge, you still have access to the raw window.StoryblokBridge:

const sbBridge = new window.StoryblokBridge(options);

sbBridge.on(["input", "published", "change"], (event) => {
  // ...
});

Rendering Rich Text

You can easily render rich text by using the renderRichText function that comes with @storyblok/react:

import { renderRichText } from "@storyblok/react";

const renderedRichText = renderRichText(blok.richtext);

You can set a custom Schema and component resolver globally at init time by using the richText init option:

import { RichTextSchema, storyblokInit } from "@storyblok/react";
import cloneDeep from "clone-deep";

const mySchema = cloneDeep(RichTextSchema); // you can make a copy of the default RichTextSchema
// ... and edit the nodes and marks, or add your own.
// Check the base RichTextSchema source here https://github.com/storyblok/storyblok-js-client/blob/master/source/schema.js

storyblokInit({
  accessToken: "<your-token>",
  richText: {
    schema: mySchema,
    resolver: (component, blok) => {
      switch (component) {
        case "my-custom-component":
          return `<div class="my-component-class">${blok.text}</div>`;
        default:
          return "Resolver not defined";
      }
    },
  },
});

You can also set a custom Schema and component resolver only once by passing the options as the second parameter to renderRichText function:

import { renderRichText } from "@storyblok/react";

renderRichText(blok.richTextField, {
  schema: mySchema,
  resolver: (component, blok) => {
    switch (component) {
      case "my-custom-component":
        return `<div class="my-component-class">${blok.text}</div>`;
        break;
      default:
        return `Component ${component} not found`;
    }
  },
});

We also recommend using the Storyblok Rich Text Renderer for React by Claus for rendering your Storyblok rich text content to React elements and Next.js applications.

The Storyblok JavaScript SDK Ecosystem

🔗 Related Links

• Storyblok Technology Hub: Storyblok integrates with every framework so that you are free to choose the best fit for your project. We prepared the technology hub so that you can find selected beginner tutorials, videos, boilerplates, and even cheatsheets all in one place.
• Getting Started: Get a project ready in less than 5 minutes.
• Storyblok CLI: A simple CLI for scaffolding Storyblok projects and fieldtypes.
• Storyblok Next.js Technology Hub: Learn how to develop your own Next.js applications that use Storyblok APIs to retrieve and manage content.
• Storyblok React.js example demo: See and try how React SDK works with React.js projects
• Storyblok Next.js example demo: See and try how React SDK works with Next.js projects

ℹ️ More Resources

Support

• Bugs or Feature Requests? Submit an issue.
• Do you have questions about Storyblok or you need help? Join our Discord Community.

Contributing

Please see our contributing guidelines and our code of conduct. This project use semantic-release for generate new versions by using commit messages and we use the Angular Convention to naming the commits. Check this question about it in semantic-release FAQ.