A comprehensive test post that exercises every Gutenberg-style block available in the editor — headings, formatting, lists, tables, blockquotes, checklists, code, and horizontal rules.

Heading 1 — Full Width Title Block

Heading 2 — Section Divider

Heading 3 — Sub-section Title

#### Heading 4 — Deep Dive Label

---

Inline Text Formatting

Normal paragraph text here. This is what a plain paragraph looks like in the editor — no formatting, just clean readable text at body size.

This paragraph tests **bold text**, *italic text*, __underlined text__, and ~~strikethrough text~~ all inside one block.

This one combines: ***bold and italic together*** — the format flag adds up to 3 (bold=1 + italic=2).

Inline code looks like this: `npm install payload` — useful for tool names, commands, and variable references.

---

Blockquote Block

> "Automation is not about replacing people. It's about freeing them to do the work only humans can do."

> This is a longer blockquote spanning multiple sentences. Blockquotes are perfect for client testimonials, key insights, or pulling out an important line that deserves visual emphasis from the rest of the content.

---

Unordered List — Bullet Points

  • Notion for project management and SOPs
  • Zapier for no-code automation workflows
  • Loom for async video communication
  • HubSpot for CRM and lead tracking
  • Canva for social graphics and presentations
  • Slack for team and client communication

    • ---

    Ordered List — Numbered Steps

    1. Set up your Notion workspace with client folders

    2. Install Zapier and connect your primary tools

    3. Build your first onboarding automation trigger

    4. Test the full flow with a dummy lead submission

    5. Monitor for 48 hours and fix edge cases

    6. Document the SOP and hand off to the client

    ---

    Checklist Block

  • [x] Configure Lexical editor with all features
  • [x] Add FixedToolbarFeature for persistent toolbar
  • [x] Enable HeadingFeature for H1 through H4
  • [x] Enable BoldFeature, ItalicFeature, UnderlineFeature
  • [x] Enable ChecklistFeature
  • [ ] Test all blocks on the frontend render
  • [ ] Confirm table renders correctly with header row
  • [ ] Verify inline code styling matches design

    • ---

    Table Block

    | Feature | Status | Notes |

    | --- | --- | --- |

    | **Headings H1–H4** | Working | Configured via HeadingFeature |

    | **Bold / Italic** | Working | Format flags 1 and 2 |

    | **Underline** | Working | Format flag 8 |

    | **Strikethrough** | Working | Format flag 4 |

    | **Inline Code** | Working | Format flag 16 |

    | **Bullet List** | Working | UnorderedListFeature |

    | **Numbered List** | Working | OrderedListFeature |

    | **Checklist** | Working | ChecklistFeature |

    | **Blockquote** | Working | BlockquoteFeature |

    | **Table** | Working | EXPERIMENTAL_TableFeature |

    | **Horizontal Rule** | Working | HorizontalRuleFeature |

    ---

    Horizontal Rule

    The line above and below this paragraph are both horizontal rules — inserted via `---` in markdown or the toolbar button.

    ---

    Mixed Formatting Paragraph

    A **Tech VA** is not just someone who handles tasks — they *build systems*. The difference between a good VA and a great one is whether they use tools like `n8n`, `Make`, or `Zapier` to eliminate ~~manual repetitive work~~ and replace it with __automated workflows__ that run 24/7 without supervision. That's ***the real value proposition***.

    ---

    Final Notes

    This post was created programmatically via the Payload MCP tool using a full markdown-to-Lexical converter. Every block type above corresponds to a Lexical node type stored in the `content` field as JSON. Switch to the **{ } Source** tab in the editor to inspect the raw Lexical JSON output for any block.