How to add a Stripe-like feedback system on your Docusaurus documentation website


This is a step by step guide to integrate Feelback with your Docusaurus website. This tutorial assumes you’re using the builtin Docusaurus theme: @docusaurus/theme-classic. However, every Docusaurus setup can be used.

With this guide you will add a feedback system similar to the one included in the Stripe documentation.

At the and of the page each documentation page Stripe asks for a user evaluation:

Stripe documentation user feedback question

When the user clicks Yes or No a set of feedback choices will appear.

Stripe documentation user feedback choices

The form title and the choices are different for the Yes and the No feedback. In addition, for each choice, the user can type an optional message to further detail the feedback.

You can read a deep analysis about the Stripe documentation on the article Case study: Stripe documentation feedback system.

Guide goals

In this tutorial you will:

Step 1: Identify feedback categories

The Stripe feedback system allows the user select a category for the feedback. To incorporate a similar system in your website, first of all, we need to identify all the different feedback categories the user can submit, and pick a unique name for each category.

In this guide, we’ll follow the same categories that Stripe uses.

For the positive feedback:

problem-solvedHelped solve my problem
clearEasy to understand
product-chosenHelped me decide to use the product
yes-otherAnother reason

For the negative ones:

missing-infoCouldn’t find what I was looking for
unclearHard to understand
bad-examplesCode samples errors
no-otherAnother reason

Step 2: Setup the Feelback project

If you don't have already a Feelback account, please signup and create one. It's free and doesn't require a credit card to use.

Access the Feelback panel, and create a project if you don't have any. Feelback panel projects

You can use your website name.

Feelback panel create project

After that, create a ContentSet which will contain your content and feedbacks you will receive.

Feelback panel create content-set

Pick the Tagged Message type to enable this content-set to receive categorized feedback message signals.

Feelback panel content-set type

For the Tag, pick the custom preset which allows you to set custom values to model your feedbacks categories.

Turn on sentiment analysis to associate a positive or negative value to each category.

User feedback sentiment analysis switch

Now, you can insert the values and the relative sentiment:

Stripe feedback sentiment categories

Set the Message optional, so the user not required to fill additional details.

Feedback message options

You will end up with a ContentSet like the following one:

Feelback panel content-set info

Step 3: Install the Feelback plugin

In your Docusaurus project directory, just install the @feelback/react package:

npm install @feelback/react

Step 4: Create the Feelback component

Let’s start creating a dedicated component to encapsulate all feedback logic. Later, we can import the component in the page layout.

export function FeedbackComponent() {
    return (
        <div className="feelback-container">


The @feelback/react package offers many builtin component and presets which helps to build your own feedback UX. You can check the React integration guide for extensive details about all provided components and presets.

For this case, we’ll use the Question component to display the question to the user. Just import it together with the LIKE_DISLIKE preset to show the buttons. Also, let’s include the predefined styling provided by the package.

import { Question, PRESET_YESNO_LIKE_DISLIKE } from "@feelback/react";
import "@feelback/react/styles/feelback.css";

export function FeedbackComponent() {
    return (
        <div className="feelback-container">
            <Question text="Was this page helpful?"

Now we can define the different Tag values, that is, the categories we have identified in first step

Let’s use the FeelbackValueDefinition type to have nice editor autocompletion.

import { FeelbackValueDefinition, Question, PRESET_YESNO_LIKE_DISLIKE } from "@feelback/react";

const YES_TAGS: FeelbackValueDefinition[] = [
    { value: "accurate", title: "Accurate", description: "Accurately describes the product or feature.", },
    { value: "problem-solved", title: "Solved my problem", description: "Helped me resolve an issue.", },
    { value: "clear", title: "Easy to understand", description: "Easy to follow and comprehend.", },
    { value: "product-chosen", title: "Helped me decide to use the product", description: "Convinced me to adopt the product or feature.", },
    { value: "other-yes", title: "Another reason" },

const NO_TAGS: FeelbackValueDefinition[] = [
    { value: "inaccurate", title: "Inaccurate", description: "Doesn't accurately describe the product or feature.", },
    { value: "missing-info", title: "Couldn't find what I was looking for", description: "Missing important information.", },
    { value: "unclear", title: "Hard to understand", description: "Too complicated or unclear.", },
    { value: "bad-examples", title: "Code samples errors", description: "One or more code samples are incorrect.", },
    { value: "other-no", title: "Another reason" },

export function FeedbackComponent() {
    /** omitted */

Finally, we’re introducing the main FeelbackTaggedMessage component responsible to send the actual feedback.

Let’s display the various options when the user presses either the Yes or No button. Then, we can show the relative feedback options.

Here’s the final FeedbackComponent component, which includes the predefined styling provided by the package.

import { useState } from "react";
import { FeelbackTaggedMessage, FeelbackValueDefinition, Question, PRESET_YESNO_LIKE_DISLIKE } from "@feelback/react";
import "@feelback/react/styles/feelback.css";

const YES_TAGS: FeelbackValueDefinition[] = [ /* omitted */ ];
const NO_TAGS: FeelbackValueDefinition[] = [ /* omitted */ ];

const FEEDBACK_CONTENT_SET_ID = "content-set-id-from-the-panel";

export function FeedbackComponent() {
    const [choice, setChoice] = useState();

    return (
        <div className="feelback-container">
                ? <Question text="Was this page helpful?"
                : <FeelbackTaggedMessage contentSetId={FEEDBACK_CONTENT_SET_ID}
                    tags={choice === "y" ? YES_TAGS : NO_TAGS}
                    title={choice === "y" ? "What did you like?" : "What went wrong?"}
                    placeholder="(optional) Please, further detail the feedback"

Step 5: Import the component

Now you are ready to add the component on your website. Let’s suppose you want place it after the article itself, just before the footer.

To edit the default theme @docusaurus/theme-classic, in Docusaurus you have to run a procedure called Swizzling which allows to replace a builtin component with a custom one.

Perform the Docusaurus swizzle on the Doc Article component

We want to wrap the current Article component and append the evaluation form. For the Docusaurus classic theme, the component is called: DocItem/Footer

In the your Docusaurus directory run:

npm run swizzle @docusaurus/theme-classic DocItem/Footer --wrap

This will copy the original component to your source folder at src/theme/DocItem/Footer so you can modify it.

Edit the component and add the Feedback component

Now you can wrap the original component and add the feedback component we just built.


import React from 'react';
import Footer from '@theme-original/DocItem/Footer';
import {FeedbackComponent } from "../../components/FeedbackComponent";

export default function FooterWrapper(props) {
  return (
      <Footer {...props} />
      <hr />
      <FeedbackComponent />

Include the default Feelback style

Append the default style provided by the package at the end of your custom.css file.


 *  Your docusaurus custom css here

@import "@feelback/react/styles/feelback.css";

The result should be something like this:

Docusaurus article footer with question Docusaurus article footer with feedback form

Additional documentation with all properties and customization you can use is available inside the dedicated React integration guide for each Feelback components.

Step 6: (Optional) Customize the component style

You can override the predefined style with additional CSS.

For example, you can add some selector to change the button background and have a rounded textarea.


 *  Your docusaurus custom css here

@import "@feelback/react/styles/feelback.css";

.feelback-container .feelback-btn {
  background-color: #1a8870;
  color: white;

.feelback-container textarea {
  border: 1px solid #ccc;
  border-radius: 4px;
  padding: 0.5rem;

The resulting component will look like:

Docusaurus article footer with feedback form custom style

Full documentation with advanced customization is available inside the React integration guide.

Analyze aggregated feedback data

You can access the Feelback panel and checkout your content performance. A content item is the target object of the user feedback. In this scenario, a content item is the actual page the user is browsing.

In the dashboard, you can quickly see which page performs better.

Stripe top content list

For each page you can analyze aggregated data, which include the feedback count received. You can go back and check historical data and change the aggregation period to week, month or year.

Stripe feedback volume chart

In this guide, we used the TaggedMessage to collect user feedbacks. And, because we configured sentiment values, Feelback creates sentiment aggregations too. For each page you can see the overall evaluation and the per Tag split.

Stripe feedback sentiment chart

In addition to the aggregated view, you can go deep and analyze each single feedback. You can search, filter and check each feedback and see the details.

Stripe feedback example

Each feedback comes with context data to further understand the relevance and specifics.

Stripe feedback context data


The @feelback/react package is open source and available on github. Any contribution is much appreciated. Issues, bug reports and feature requests are welcome. Do not hesitate to reach us or ask for help.

Additional resources

Other guides for Docusaurus