Block development basics in Wordpress

Introduction

Blocks let you build content pieces easily in WordPress. They make editing simple and flexible without coding every time.

You want to add custom content layouts in WordPress posts or pages.

You need reusable content sections that users can edit visually.

You want to create interactive or styled content without writing HTML each time.

You want to extend WordPress editor with your own content types.

You want to improve user experience by making content editing intuitive.

Syntax

Wordpress

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

registerBlockType is the main function to create a block.

edit defines what shows in the editor, save defines what is saved in the post content.

Examples

A basic block that shows static text in editor and saved content.

Wordpress

wp.blocks.registerBlockType('myplugin/simple-text', {
  title: 'Simple Text',
  icon: 'editor-paragraph',
  category: 'formatting',
  edit: () => wp.element.createElement('p', null, 'Type your text here'),
  save: () => wp.element.createElement('p', null, 'Type your text here'),
});

This block shows a message that is defined inside the edit function and saved as static content.

Wordpress

wp.blocks.registerBlockType('myplugin/dynamic-message', {
  title: 'Dynamic Message',
  icon: 'megaphone',
  category: 'widgets',
  edit: () => {
    const message = 'Hello, WordPress!';
    return wp.element.createElement('p', null, message);
  },
  save: () => {
    return wp.element.createElement('p', null, 'Hello, WordPress!');
  },
});

Sample Program

This block shows a friendly greeting both in the editor and on the published page. It uses the basic block structure with edit and save functions returning simple paragraphs.

Wordpress

wp.blocks.registerBlockType('myplugin/greeting-block', {
  title: 'Greeting Block',
  icon: 'smiley',
  category: 'widgets',
  edit: () => {
    return wp.element.createElement('p', null, 'Welcome to your custom block!');
  },
  save: () => {
    return wp.element.createElement('p', null, 'Welcome to your custom block!');
  },
});

Important Notes

Always use unique namespaced block names like 'myplugin/block-name' to avoid conflicts.

The edit function runs in the editor and can use React features.

The save function returns the HTML saved in the post content and shown on the site.

Summary

Blocks let you create reusable content pieces in WordPress visually.

Use registerBlockType with edit and save functions to define blocks.

Blocks improve editing experience and make content flexible without coding each time.

Practice

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

easy

A. To create reusable content pieces that users can add visually

B. To write PHP code for custom themes

C. To manage user roles and permissions

D. To optimize database queries

Solution

1. Step 1: Understand the role of blocks in WordPress

   Blocks are designed to let users add content pieces easily without coding each time.

2. Step 2: Identify the main benefit of blocks

   Blocks are reusable and visually manageable content units improving editing experience.

3. Final Answer:

   To create reusable content pieces that users can add visually -> Option A

4. Quick Check:

   Blocks = reusable visual content [OK]

Hint: Blocks are for reusable visual content pieces [OK]

Common Mistakes:

• Confusing blocks with PHP theme coding
• Thinking blocks manage users or database
• Assuming blocks are only for styling

2. Which function is used to register a new block type in WordPress block development?

easy

A. createBlockType()

B. initBlock()

C. addBlock()

D. registerBlockType()

Solution

1. Step 1: Recall the standard WordPress block registration function

   The official function to register blocks is registerBlockType.

2. Step 2: Verify other options are incorrect

   Functions like createBlockType, addBlock, and initBlock do not exist in WordPress block API.

3. Final Answer:

   registerBlockType() -> Option D

4. Quick Check:

   Register blocks = registerBlockType() [OK]

Hint: Remember: registerBlockType() registers blocks [OK]

Common Mistakes:

• Using createBlockType() which is not a WordPress function
• Confusing with addBlock() or initBlock() which don't exist
• Misspelling the function name

3. Given this block registration code snippet, what will the block display in the editor?

registerBlockType('myplugin/example', {
  edit: () => {
    return 
Hello, WordPress!
;
  },
  save: () => {
    return 
Hello, WordPress!
;
  }
});

medium

A. A paragraph with text 'Hello, WordPress!' in both editor and saved content

B. An empty block with no content

C. A syntax error preventing block registration

D. A block showing 'edit' text only

Solution

1. Step 1: Analyze the edit function output

   The edit function returns a paragraph with 'Hello, WordPress!' which shows in the editor.

2. Step 2: Analyze the save function output

   The save function returns the same paragraph, so saved content also shows 'Hello, WordPress!'.

3. Final Answer:

   A paragraph with text 'Hello, WordPress!' in both editor and saved content -> Option A

4. Quick Check:

   Edit and save return same paragraph = A paragraph with text 'Hello, WordPress!' in both editor and saved content [OK]

Hint: Edit and save return same JSX content means same display [OK]

Common Mistakes:

• Thinking edit content differs from saved content
• Assuming syntax error due to JSX
• Confusing block output with empty or error

4. Identify the error in this block registration code:

registerBlockType('myplugin/test', {
  edit: () => {
    return 
Test Block
;
  },
  save: () => {
    return div>Test Block;
  }
});

medium

A. edit function missing return statement

B. Missing opening < in save function JSX

C. registerBlockType function name is incorrect

D. Block name 'myplugin/test' is invalid

Solution

1. Step 1: Check the save function JSX syntax

   The save function returns div>Test Block; which is missing the opening < for the div tag.

2. Step 2: Verify other parts are correct

   The edit function correctly returns JSX with <div>, the function name is correct, and block name format is valid.

3. Final Answer:

   Missing opening < in save function JSX -> Option B

4. Quick Check:

   JSX tags must start with < [OK]

Hint: Check JSX tags start with < and end with > [OK]

Common Mistakes:

• Ignoring missing < in JSX tags
• Thinking function names or block names are wrong
• Overlooking return statements

5. You want to create a block that shows a dynamic greeting with a user name passed as an attribute. Which approach correctly uses attributes in block development?

hard

A. Hardcode the user name inside the save function JSX

B. Use a global variable for the name inside edit and save functions

C. Define attributes in registerBlockType and use props.attributes.name in edit and save

D. Only define attributes in edit function, ignore save function

Solution

1. Step 1: Understand attribute usage in blocks

   Attributes must be declared in registerBlockType and accessed via props.attributes in both edit and save functions.

2. Step 2: Evaluate other options

   Using global variables or hardcoding breaks reusability and dynamic behavior; ignoring attributes in save causes data loss.

3. Final Answer:

   Define attributes in registerBlockType and use props.attributes.name in edit and save -> Option C

4. Quick Check:

   Attributes declared and used properly = Define attributes in registerBlockType and use props.attributes.name in edit and save [OK]

Hint: Declare and use attributes via props in edit and save [OK]

Common Mistakes:

• Using global variables instead of attributes
• Hardcoding values losing flexibility
• Not using attributes in save function