---
title: "Introducing WP Block Suite: Premium Blocks for Content, Tables, Galleries, Sliders & More"
date: 2025-12-28
author: "Istiak Rayhan"
featured_image: "https://wpblocksuite.com/wp-content/uploads/2026/08/featured-introducing-wp-block-suite.png"
categories:
  - name: "WP Block Suite"
    url: "/blog/category/wp-block-suite.md"
---

# Introducing WP Block Suite: Premium Blocks for Content, Tables, Galleries, Sliders & More

We started with one plugin and a simple plan: build useful Gutenberg blocks for WordPress.

That plugin was [Ultimate Blocks](https://ultimateblocks.com/). It launched with about a dozen blocks. Content toggles, tabbed content, a table of contents, star ratings, testimonials, call-to-action buttons, and more. People liked it. We kept adding blocks. A review block with schema markup. A countdown timer. An image slider. A post grid. A how-to block.

Before long, Ultimate Blocks had 25+ blocks covering everything from social sharing to progress bars. On paper, that sounds like success. In practice, we’d built ourselves a problem.

## The Quality Ceiling

Here’s the thing nobody in the block plugin space talks about openly. Maintain 25+ blocks in a single plugin and most of them stay mediocre.

Not broken. Not bad. Just… adequate. Good enough to ship. Never deep enough to be the best tool for the job.

Take our gallery block. It needed masonry layouts, filtering and responsive breakpoint controls. We couldn’t build those without neglecting the other 25 blocks. Same with tables. Cell-level styling, merge support and responsive behavior would have eaten our roadmap for months. Everything else would sit untouched.

Every sprint we spent deepening one block meant two dozen others stayed shallow. That’s the math every multi-block plugin faces, whether they admit it or not.

## The Decision to Break Things Apart

So we made a counterintuitive choice for a plugin company. We stopped adding blocks to Ultimate Blocks.

Instead, we pulled out the blocks that deserved to be products. Each got a dedicated plugin. Its own roadmap, its own development cycle, room to grow. No more competing for resources against 25 other features.

**[Tableberg](https://tableberg.com/)** became its own plugin. A serious table solution isn’t just “a table block”. It’s cell-level styling, header and footer designation, merge support, responsive controls, and styling presets. And the roadmap goes further: WooCommerce product tables, post tables, comparison tables. You can’t stuff all of that into one block of a 25-block plugin. The whole thing becomes unwieldy.

**[Galleryberg](https://galleryberg.com/)** became its own plugin too. Done right, a gallery means grid layouts, masonry, lightbox, filtering and caption overlays. Add lazy loading and fine-grained responsive controls. That’s a product, not a feature.

**[Sliderberg](https://sliderberg.com/)** became its own plugin — and this one is worth explaining. Ultimate Blocks already had an image slider. It works fine for sliding images. But Sliderberg is a *content* slider. You can slide anything — testimonials, feature cards, mixed content, whatever your layout needs. That’s only possible when the concept gets its own plugin and architecture.

And **Ultimate Blocks** itself got better too. Freed from being everything, it could focus. The best essential content blocks: toggles, tabs, table of contents, reviews, ratings, CTAs, countdowns. The blocks content creators reach for every day.

## One Suite, One Payment

The obvious question. If you break one plugin into four, do users buy four things? The answer is in [when not to buy a plugin bundle](https://wpblocksuite.com/blog/when-not-buy-wordpress-plugin-bundle/).

No. That’s where WP Block Suite comes in.

![](https://wpblocksuite.com/wp-content/uploads/2025/12/WP-Block-Suite-1024x822.png)WP Block Suite bundles Ultimate Blocks, Tableberg, Galleryberg and Sliderberg under one licence. One purchase, full access to every plugin, every premium feature unlocked. We took that apart in [installing and activating WP Block Suite](https://wpblocksuite.com/blog/install-activate-wp-block-suite/).

You install only the plugins you actually need. If you just need advanced tables, install Tableberg. If you need content blocks and a gallery, install Ultimate Blocks and Galleryberg. You never carry the weight of blocks you don’t use. And the full suite is always there when you need it.

That’s the core idea: **specialist depth with bundle simplicity.**

## What is coming next

Productberg: Coming soon, included free.

Current purchase decisions should use the four available Pro plugins.

## Why This Approach Beats All-in-One Block Libraries

The WordPress ecosystem is full of plugins shipping 50, 80, even 100+ blocks. We understand the appeal — one install, everything included. The full walkthrough is in [our block plugin roundup for 2026](https://wpblocksuite.com/blog/best-gutenberg-block-plugins/).

But we’ve been on the other side of that equation. We know what happens when you try to maintain dozens of blocks under one roof. Quality spreads thin. Each block gets just enough attention to function but never enough to excel. And your site loads assets for blocks you’ll never use.

WP Block Suite takes the opposite approach. Each plugin is a specialist. Tableberg competes with dedicated table plugins. Not with a table block buried in an 80-block library. Galleryberg competes with dedicated gallery plugins. That’s our standard. Every plugin in the suite should be best-in-class for its category. We wrote that up in [standardising WP Block Suite across sites](https://wpblocksuite.com/blog/standardise-wp-block-suite-agency-sites/).

You get the convenience of one licence with the quality of purpose-built tools.

## The current offer

WP Block Suite costs $299 once. The purchase covers four current Pro plugin packages.

- Lifetime use.
- Lifetime updates.
- Unlimited sites.
- Priority support.
- A 30-day money-back guarantee.

Confirm current terms before purchasing. The guarantee supports evaluation but does not replace testing.

## Four packages, not one suite shell

The suite does not add a required wrapper plugin. Each product remains separately installable and operable.

- Download the required product ZIP.
- Upload it through WordPress.
- Activate that plugin.
- Enter its licence details.
- Configure approved capabilities.
- Test representative content.

Install only products needed by the site. Unused software cannot create realised bundle value.

## Ultimate Blocks Pro

Ultimate Blocks Pro serves broader content-building requirements. Use it for approved editorial outcomes and patterns.

- Name the required content job.
- Choose approved blocks.
- Set style boundaries.
- Create reusable examples.
- Test editor roles.
- Inspect frontend output.
- Document ownership.

A broad toolkit still needs curation. More visible blocks can increase editor confusion.

## Tableberg Pro

Tableberg Pro serves table requirements. Use tables for meaningful relationships, not arbitrary page layout.

- Define the table’s purpose.
- Use clear headers.
- Keep structure understandable.
- Test responsive behaviour.
- Test keyboard use.
- Review expected data volume.
- Document migration needs.

Large or complex data may need another system. Match the tool to the complete requirement.

## Galleryberg Pro

Galleryberg Pro serves gallery requirements. Media preparation remains part of the publishing workflow.

- Choose suitable source images.
- Prepare efficient dimensions.
- Compress media responsibly.
- Make alternative text decisions.
- Add useful captions.
- Test responsive layouts.
- Measure realistic page weight.

A gallery plugin cannot repair poor media [governance](https://wpblocksuite.com/blog/block-editor-governance-teams-agencies/). Assign ownership for uploads and cleanup.

## Sliderberg Pro

Sliderberg Pro serves accepted slider requirements. A static layout can remain the stronger choice.

- Define the communication purpose.
- Limit hidden important content.
- Test keyboard controls.
- Check focus order.
- Review motion behaviour.
- Test narrow layouts.
- Measure frontend performance.

Do not add a slider from habit. Confirm users can reach every required message.

## When the bundle makes sense

The bundle becomes relevant when several products meet proven requirements. Compare complete accepted alternatives.

- Several categories have current demand.
- Teams can adopt the products.
- Required capabilities pass testing.
- One account simplifies real operations.
- Unlimited sites support planned deployment.
- Complete costs beat acceptable alternatives.
- Exit and recovery remain manageable.

Count only used components in the value case. Shelfware should receive no realised savings.

## When standalone makes sense

Buy one standalone product when one category meets the complete need. The suite is not automatic.

- Ultimate Blocks Pro costs $199.
- Tableberg Pro costs $149.
- Galleryberg Pro costs $149.
- Sliderberg Pro costs $49.

Those current prices total $546. Pair comparisons can still favour standalone purchases. The full breakdown lives in [the suite versus buying separately](https://wpblocksuite.com/wp-block-suite-vs-buying-separately/).

Never add unused list prices to invented savings. Start from requirements and likely adoption.

## How delivery works

Freemius handles checkout and delivery. Downloads and licence details appear in the customer account.

1. Complete the authorised purchase.
2. Open the Freemius account.
3. Locate all four products.
4. Download required ZIP packages.
5. Store purchase evidence.
6. Protect licence details.
7. Assign organisational access.

Avoid personal account dependence for agency operations. Keep authorised recovery contacts current.

## How to evaluate the suite

1. Define required publishing outcomes.
2. Separate mandatory and optional capability.
3. Choose representative content.
4. Install required packages on staging.
5. Enter assigned licence details.
6. Apply approved configuration.
7. Test intended editor roles.
8. Inspect public output.
9. Test responsive behaviour.
10. Test accessibility.
11. Measure performance.
12. Review data and integrations.
13. Test updates and recovery.
14. Estimate complete ownership costs.
15. Choose suite or standalone deliberately.

Use the 30-day guarantee within current terms. Record the deadline and highest-risk tests.

## Operating the suite after launch

- Record installed products and versions.
- Assign update ownership.
- Maintain suitable backups.
- Test important releases.
- Monitor licence access.
- Preserve configuration records.
- Train editors on approved blocks.
- Review accessibility and performance.
- Remove unused components.
- Maintain replacement routes.

Lifetime updates still require operations. Unlimited sites still require installation records and client ownership.

## The honest limitation

No bundle guarantees fit across every project. Specialist alternatives can outperform one included product.

Use that specialist when evidence supports it. Standardisation should never override a critical requirement.

## Record every suite installation

- Client and site.
- Production URL.
- Staging URL.
- Installed suite products.
- Installed versions.
- Package source.
- Installation date.
- Installation operator.
- Licence state.
- Account owner.
- Recovery contacts.
- Configuration profile.
- Enabled capabilities.
- Required blocks.
- Approved patterns.
- Theme and version.
- WordPress version.
- PHP version.
- Important integrations.
- Remote services.
- Stored data.
- Content dependencies.
- Accessibility evidence.
- Performance evidence.
- Responsive evidence.
- Editor roles tested.
- Update group.
- Update owner.
- Support owner.
- Backup route.
- Restoration route.
- Monitoring owner.
- Known limitations.
- Accepted exceptions.
- Replacement option.
- Client handoff state.
- Next review date.

## Ask the right purchase questions

- Which products have immediate use?
- Which workflows will they improve?
- Who owns adoption?
- Who owns configuration?
- Who owns updates?
- Who owns support?
- Who owns recovery?
- Will editors receive training?
- Do required blocks pass testing?
- Does responsive output remain acceptable?
- Does accessibility remain acceptable?
- Does performance remain acceptable?
- Are data flows understood?
- Are services understood?
- Is account ownership organisational?
- Are client terms clear?
- Does standalone cost less?
- Does the suite reduce real work?
- Are unused products valued at zero?
- Is the exit route credible?
- Is the guarantee window sufficient?
- Can highest-risk tests finish promptly?
- Does cash timing remain acceptable?
- Are current terms recorded?
- Is approval independent from urgency?

Good answers turn a bundle into an operating decision. Weak answers suggest deferral or standalone purchase.

## Use the suite readiness checklist

1. Define the publishing outcomes that need additional block capability.
2. Identify which of the four products serves each outcome.
3. Remove products without a current or approved near-term use.
4. Compare required standalone prices against the $299 suite price.
5. Value unused products at zero throughout the purchase decision.
6. Confirm lifetime use matches the expected ownership period.
7. Confirm unlimited sites match actual agency or portfolio demand.
8. Confirm the team can operate four separate plugin packages.
9. Choose an organisational owner for the Freemius customer account.
10. Protect downloads, licence details, authentication, and recovery contacts.
11. Record the current 30-day guarantee deadline after purchase.
12. Schedule highest-risk tests early inside the guarantee window.
13. Create a suitable backup before installing any package.
14. Use staging when production consequence warrants controlled evaluation.
15. Install only the packages required by the intended site.
16. Enter the licence details assigned to each installed product.
17. Configure approved capabilities without enabling every possible choice.
18. Create realistic content using every required suite component.
19. Test normal editor tasks using the intended WordPress roles.
20. Inspect public output across expected themes and templates.
21. Test keyboard completion, focus, labels, contrast, and reading order.
22. Test responsive behaviour with realistic content and media sizes.
23. Measure page and editor performance under matching conditions.
24. Inspect local data, remote services, integrations, and deactivation effects.
25. Verify update availability and add products to normal operations.
26. Document support, backup, recovery, and replacement responsibilities.
27. Train editors on approved blocks, patterns, and content standards.
28. Record client ownership and future handoff responsibilities.
29. Review adoption after launch and remove unnecessary components.
30. Keep standalone products when one category meets the complete need.
31. Use specialist alternatives when an included product fails acceptance.
32. Review the suite after meaningful product or portfolio changes.

Suite value comes from used capability and controlled operations. A large entitlement alone creates neither.

## Review the operating promise

The suite simplifies purchasing across four products. It does not remove implementation, testing, or ownership.

Lifetime updates require an active operating process. Unlimited sites require accurate deployment and client records.

Priority support works best with reproducible evidence. Suitable backups and recovery remain the site’s responsibility.

Use the four products where they pass acceptance. Keep WordPress core or specialists elsewhere.

That boundary protects outcomes while preserving the suite’s practical value.

## Get Started

WP Block Suite is available now at [WPBlockSuite.com](https://wpblocksuite.com/).

Already using Ultimate Blocks? You’re halfway there. The suite unlocks the premium features you’ve been missing. Tableberg, Galleryberg and Sliderberg come with it.

We built these plugins because one plugin couldn’t deliver the quality we wanted. We think you’ll notice the difference.