The pro-code environment extends the platform's capabilities by offering pro-coders to add custom functionalities. In this article, we will find out how to create your own custom component to use later while working with the page builder.

Before you start working with the pro-code environment, let’s ensure you know the requirements. For creating pro-code components they are next:

Following this, let’s take a look at what kind of tools we will be using:

1) The first requirement for creating a component set is Node.js as a custom component is a Node project. Go to http://nodejs.dev to download the latest version of Node.js.

2) The following tool is an optional tool called Yarn. You can use this or NPM which is automatically installed when you install Node.js The link for download is here: https://classic.yarnpkg.com/lang/en/docs/install/

3) Of course, you would also need a code editor. We recommend you use Visual Studio Code as the code editor for creating your custom components as this is the one we will use in this guide. Download the latest version by this link:

https://code.visualstudio.com/. Some of the extensions used for VS Code in this guide are Prettier & ESLint.

4) Lastly required tool is Betty Blocks CLI - the command line interface of our platform that is used while creating new component sets, setting up a local development environment, serving a component set to multiple people, and publishing a component set to the Block Store.

In order to install the Betty Blocks CLI, open your command line tool - Command Prompt or Terminal (later in the text referred to as just “terminal”) and type in:

npm install -g @betty-blocks/cli

Note: To check if the CLI is installed correctly, type bb -v and you’ll be able to see the version installed. Also, if you run into multiple errors while installing Betty CLI, try using 'sudo' before each command:

sudo npm install -g @betty-blocks/cli

In this part, we are going to use CLI to create a new empty project for our components, then use NMP to install all dependencies that are needed to run the components, and lastly, run a development server in order to add the component to the page builder. Let’s get started!

1) Open your terminal and use the following command to create a new component set. Each step will be supported by a real example with a project called 'cardview'.

bb components create <project name>

Note: You can also use the command bb --help that will display all the commands of the CLI. In order to check if this folder exists now, use cd <project name> command.

2) Now that we have our new empty project, let’s set the dependencies by installing Node Package Manager (NPM).

npm install

When installed, the node_modules folder will appear in the file explorer.

Basically, everything mentioned here can also be found in Betty Blocks CLI documentation on GitHub.

3) Within the next step, we are going to run a development server so we can use the component in the page builder.

4) As you can see our component set is live in our page builder, with only the 'hello world component present, let's change this and add our own custom component in the next section.

The first thing we need to do in order to make a new component from scratch is to create a new file in our ‘cardview’ folder. We will call it ‘text.js’. Copy and paste the component code snippet from our GitHub page and then we proceed with the following changes to the code:

What we have now is a default snippet for a component. Let's add some stuff to it so you can see how you can make changes to your own components. The first we'll do for this example is change the jsx to its most basic form. I'll add a div in there with the text 'Hello world'.

1) Remove this bit:

jsx: (() => {

const value ='Example';

return <div className={classes.root}>{value}</div>;

})(),

And replace it with:

jsx: <div>Hello world!</div>,

2) Let's also add a bit of styling, in the root part of the styles we'll simply add:

root: {

color: '#E9004E',

},

This will give the component the Betty Blocks red color. Now to apply the root class to the div we made; we do this as follows:

jsx: <div className={classes.root}>Hello world!</div>,

Eventually, here's how our code looks like.

In order for us to be able to use this component in the page builder, we also need to create a prefab - the element we see in the overview of all components.

1) Create a new file in the prefabs folder. It will be called ‘text.js’ in our case. Usually, it’s better to call both the component and prefab by the same name. Use the prefab code snippet copied from our GitHub page.

{() => ({

name: '',

icon: 'ParagraphIcon',

category: 'CONTENT',

structure: [

{

name: '',

options: [],

descendants: [],

},

],

}))();

2) Name the prefab (‘My custom Component’ in our example), then choose the icon for it (for instance, ‘ParagraphIcon’) and choose the category (like ‘CONTENT’).

Just like a component, a prefab is an object immediately returned by an arrow function. The properties set in this step are descriptive information.

3) Next, we have a prefab structure. It’s an array of component configurations while this configuration is an object itself. That object needs to point to a specific component by name. Therefore, we type the following into ‘structure’:

name ‘text’,

That will point to the component name defined in our component file.

4) Now you just need to make this component available through the terminal. Let's open it and type:

npm run dev

5) After you create a new page and copy-paste the localhost into the settings there, you'll see the text component we created in the list of components! Let’s drag it onto our canvas.

6) Lastly, you can compile the page to test it out. As you can see, the component is right there.

For more discussions on creating custom components, we recommend visiting the community, where developers discuss options and new components together!