Build the account page with native blocks
This is the visual-editor alternative to the shortcode account example. It provides the same nine account features, but uses real Ultimate Multisite blocks inside WordPress Group, Heading and Paragraph blocks. There are no Shortcode or Custom HTML blocks in either native-block page export.
The optional example canvas and stylesheet are shared between both versions. The page content remains editable block by block: change headings, move account widgets, adjust their settings, or replace the surrounding layout with your own.
The screenshots and verification use the native-block repairs proposed in plugin PR #2086: styled iframe previews, correctly typed settings, and early detection of settings inside Groups/Columns. Use the release containing these fixes on production. The block editor shows sample preview data, not the account of the administrator editing the page. Test the published page as a customer before launch.
1. Insert the native account blocks
Create a published page on the network main site, not a customer-owned subsite. Use + Block Inserter and search for each block by its name below. For example, search Membership and select Ultimate Multisite's Membership block. Do not insert a Shortcode block and paste shortcode text for this version.

| Native block name in the inserter | Block identifier | Shortcode equivalent |
|---|---|---|
| Membership | wp-ultimo/current-membership | [wu_current_membership] |
| My Sites | wp-ultimo/my-sites | [wu_my_sites] |
| Site | wp-ultimo/current-site | [wu_current_site] |
| Account Summary | wp-ultimo/account-summary | [wu_account_summary] |
| Limits & Quotas | wp-ultimo/limits | [wu_limits] |
| Billing Information | wp-ultimo/billing-info | [wu_billing_info] |
| Payment Methods | wp-ultimo/payment-methods | [wu_payment_methods] |
| Invoices | wp-ultimo/invoices | [wu_invoices] |
| Actions | wp-ultimo/site-actions | [wu_site_actions] |
You can start with these nine blocks in a vertical stack in any theme. Put Membership and My Sites near the top. Site, Account Summary and Limits & Quotas refer to a selected site; they do not replace the account-wide membership card.
For the styled layout, use the page export in step 4. To build your own layout, add Heading blocks for Membership, Sites, Billing and Settings, and wrap related widgets in Group or Columns blocks. List View lets you select nested blocks and move whole sections without editing code.

2. Configure the block inspector
Select a widget, open Settings → Block, and use its controls. These are the same widget options exposed by shortcode attributes, presented as form controls.
- Membership: leave Title blank when your layout already has a membership heading. Turn Display Product Images off for the text-first example.
- My Sites: choose Same Page for Site Manage Type, Owned for Which sites to show, 2 columns, and turn Display Site Screenshot off. The native Manage links then select the site on this account page.
- Site: turn the screenshot off if you do not have useful site previews. Keep breadcrumbs and the admin link if customers should have those routes.
- Billing Information, Payment Methods, Invoices, Account Summary and Limits & Quotas: edit their titles as needed. Invoice count limits how many payment records are shown; it does not create example invoices.
- Actions: choose whether to expose password, email, default-site and payment-method links. Visibility options do not grant authorization.

If you choose Custom Page in My Sites, search for a published main-site management page in Manage Redirect Page. That destination needs the relevant Site, Account Summary, Limits and Actions blocks. For this combined-page layout, leave Same Page selected. Save, reload and check the settings remain selected.
Editor previews are not live customer operations. Some preview information is fictional, and empty states depend on the widget. Do not use editor-preview links to cancel, delete or manage a real customer. Use a separate customer browser for the published-page checks below.
3. Create the matching native Checkout page
Create a second main-site page for membership changes. Insert the Checkout
block (wp-ultimo/checkout) and select your published checkout form in its
inspector. This example uses the form slug wu-checkout; replace it with the
form actually configured on your network.

Publish the page, then select it as Network Admin → Ultimate Multisite → Settings → Memberships → Default Membership Update Page. There is one shared default for the network, not a separate default for each account example. Choosing the block Checkout page changes the destination of native membership Change links on both account pages. Keep the membership query generated by those links; a bare navigation link to checkout is not equivalent.
The examples use /account-blocks/ and /membership-blocks/. Select the block
Checkout page to demonstrate the complete all-block journey. You can keep the
original /account/ and /membership/ shortcode pages for comparison; both
account pages' Change links always use the one shared membership-update setting.
4. Reproduce the styled example without writing layout code
Download the example plugin and both page variants
Use the shared installation steps for the optional canvas plugin and Ollie theme. Then:
- Create the Account page and switch the editor to Options → Code editor.
- Paste the entire contents of
account-blocks.htmlfrom the ZIP, including the block comments. Switch back to Visual editor. WordPress recognizes the saved blocks; this is a one-time import, not a Code block. - Choose Account workspace (example) as the page template, then save.
- Repeat for the plans page using
plans-blocks.htmlfrom the ZIP and the same template. Change its Back to your account link if your account slug or WordPress installation directory differs. - Configure the Checkout block's form and the shared membership-update setting.
The exported pages were saved and reloaded in the real WordPress editor. No Python tool, generation script, build command or page-builder plugin is needed. All seven files, including both native page exports, are displayed in full in the shared source reference.