Block registration in Wordpress

Introduction

Block registration lets you add new blocks to the WordPress editor. This helps you create custom content pieces easily.

You want to add a special content block like a testimonial or a call-to-action.

You need a reusable block with custom settings for your website.

You want to create a block that matches your brand style and layout.

You want to extend the editor with blocks that show dynamic data.

You want to simplify content creation for editors with custom blocks.

Syntax

Wordpress

registerBlockType('namespace/block-name', {
  title: 'Block Title',
  icon: 'smiley',
  category: 'common',
  edit: () => {
    return <p>Hello from the block editor!</p>;
  },
  save: () => {
    return <p>Hello from the saved content!</p>;
  },
});

The first argument is a unique name with a namespace and block name separated by a slash.

The edit function defines what appears in the editor, and save defines what is saved in the post content.

Examples

This example creates a yellow alert box block with a warning icon.

Wordpress

registerBlockType('myplugin/alert', {
  title: 'Alert Box',
  icon: 'warning',
  category: 'widgets',
  edit: () => <div style={{backgroundColor: 'yellow', padding: '10px'}}>Alert in editor</div>,
  save: () => <div style={{backgroundColor: 'yellow', padding: '10px'}}>Alert on page</div>,
});

A simple text block that shows the same text in editor and saved content.

Wordpress

registerBlockType('myplugin/simple-text', {
  title: 'Simple Text',
  icon: 'text',
  category: 'text',
  edit: () => <p>Type your text here</p>,
  save: () => <p>Type your text here</p>,
});

Sample Program

This block shows a button in the editor that counts clicks. The saved content is a simple button text because saved content can't have dynamic state.

Wordpress

import { registerBlockType } from '@wordpress/blocks';
import { useState } from '@wordpress/element';

registerBlockType('myplugin/click-counter', {
  title: 'Click Counter',
  icon: 'smiley',
  category: 'widgets',
  edit: () => {
    const [count, setCount] = useState(0);
    return (
      <button onClick={() => setCount(count + 1)} aria-label="Click counter button">
        Clicked {count} times
      </button>
    );
  },
  save: () => {
    return <button>Click counter saved block</button>;
  },
});

Important Notes

Blocks must have a unique name with a namespace to avoid conflicts.

The edit function can use React hooks like useState for interactivity in the editor.

The save function returns static content that is saved in the post and shown on the site.

Summary

Block registration adds custom blocks to the WordPress editor.

Use registerBlockType with a unique name and provide edit and save functions.

Blocks help create rich, reusable content easily for editors and visitors.

Practice

1. What is the main purpose of registerBlockType in WordPress block development?

easy

A. To add a new custom block to the WordPress editor

B. To register a new theme for WordPress

C. To create a new user role in WordPress

D. To install a plugin automatically

Solution

1. Step 1: Understand the role of registerBlockType

   This function is used specifically to add custom blocks to the WordPress block editor.

2. Step 2: Compare with other WordPress features

   Registering themes, user roles, or plugins are done by different functions, not registerBlockType.

3. Final Answer:

   To add a new custom block to the WordPress editor -> Option A

4. Quick Check:

   Block registration = add custom block [OK]

Hint: Remember: registerBlockType = add custom block [OK]

Common Mistakes:

• Confusing block registration with theme or plugin registration
• Thinking it creates user roles
• Assuming it installs plugins automatically

2. Which of the following is the correct way to start registering a block named "myplugin/example" in JavaScript?

easy

A. registerBlockType('myplugin_example', { edit: () => {}, save: () => {} });

B. registerBlock('myplugin/example', { edit: () => {}, save: () => {} });

C. registerBlockType('myplugin/example', { edit: () => {}, save: () => {} });

D. registerBlockType('myplugin/example');

Solution

1. Step 1: Identify the correct function name and parameters

   The correct function is registerBlockType and it requires a unique block name and an object with edit and save functions.

2. Step 2: Check the block name format and object completeness

   The block name must be a string with a namespace and name separated by a slash, like 'myplugin/example'. The object must include both edit and save functions.

3. Final Answer:

   registerBlockType('myplugin/example', { edit: () => {}, save: () => {} }); -> Option C

4. Quick Check:

   Correct function and full object = registerBlockType('myplugin/example', { edit: () => {}, save: () => {} }); [OK]

Hint: Use registerBlockType with namespace/name and edit/save [OK]

Common Mistakes:

• Using registerBlock instead of registerBlockType
• Using underscore instead of slash in block name
• Omitting edit or save functions

3. Given this block registration code snippet, what will be the saved content output in the post?

registerBlockType('myplugin/simple', {
  edit: () => {
    return wp.element.createElement('p', null, 'Hello Editor');
  },
  save: () => {
    return wp.element.createElement('p', null, 'Hello Saved');
  }
});

medium

A. <p>Hello Editor</p>

B. <p>Hello Saved</p>

C. Hello Editor

D. Hello Saved

Solution

1. Step 1: Understand the difference between edit and save functions

   The edit function controls what the editor shows while editing. The save function controls what HTML is saved and shown on the front end.

2. Step 2: Identify the saved output

   The save function returns a paragraph with text 'Hello Saved', so this is the content saved in the post and shown to visitors.

3. Final Answer:

   <p>Hello Saved</p> -> Option B

4. Quick Check:

   Saved content = save() output = <p>Hello Saved</p> [OK]

Hint: Remember: save() output is what visitors see [OK]

Common Mistakes:

• Confusing edit() output with saved content
• Ignoring that save() returns HTML elements
• Assuming edit() content is saved

4. Identify the error in this block registration code:

registerBlockType('myplugin/test', {
  edit() {
    return <p>Edit Block</p>
  },
  save() {
    return <p>Save Block</p>
  }
});

medium

A. JSX syntax used without React or Babel setup

B. Block name missing namespace

C. Missing semicolons after return statements

D. edit and save functions must be arrow functions

Solution

1. Step 1: Check the syntax used in edit and save functions

   The code uses JSX syntax like <p>Edit Block</p> directly, which requires React and Babel setup to compile.

2. Step 2: Identify environment requirements

   If JSX is used without proper setup, this code will cause syntax errors. The code should use wp.element.createElement or have JSX compiled.

3. Final Answer:

   JSX syntax used without React or Babel setup -> Option A

4. Quick Check:

   JSX needs compilation = JSX syntax used without React or Babel setup [OK]

Hint: JSX needs React/Babel; otherwise use createElement [OK]

Common Mistakes:

• Assuming JSX works without setup
• Thinking semicolons are mandatory after return
• Believing edit/save must be arrow functions

5. You want to register a block that shows a list of items passed as an attribute and saves them as a comma-separated string. Which approach correctly registers this block?

hard

A. Store the list as a string attribute, use edit to split it into an array, and save to output the array directly.

B. Store the list as an object attribute, use edit to convert it to string, and save to output JSON.

C. Use no attributes, hardcode the list in save, and ignore edit.

D. Use attributes to store an array, edit to update it, and save to join array into a string inside a <p> tag.

Solution

1. Step 1: Define attributes properly for data handling

   To handle a list, store it as an array attribute so it can be easily manipulated in edit.

2. Step 2: Implement edit and save functions correctly

   edit updates the array attribute. save joins the array into a comma-separated string inside a paragraph tag for saving as HTML.

3. Final Answer:

   Use attributes to store array, edit to update, save to join as string -> Option D

4. Quick Check:

   Array attribute + join in save = Use attributes to store an array, edit to update it, and save to join array into a string inside a <p> tag. [OK]

Hint: Store list as array attribute, join in save() output [OK]

Common Mistakes:

• Storing list as string and trying to output array directly
• Ignoring attributes and hardcoding data
• Saving data as JSON instead of HTML