Unlock the potential of Adobe Commerce and BigCommerce for seamless content management

In this article, we discuss the differences between Adobe Commerce (formerly Magento 2) and BigCommerce in relation to the content management . You will see how each system behaves so you can determine which is a better fit for your needs.

Content Management

Blocks

These represent common pieces of content. For example, a Hubspot contact form or shipping information may be stored here and injected into any Page Builder-enabled location.

Adobe Commerce

Administrators can utilize Static Blocks for this purpose. These blocks, themselves, are PageBuilder-enabled. Additionally, they can be injected into common locations (extendable by a developer) through the Widgets interface.

BigCommerce

This capability does not exist out of the box. We are not aware of any 3rd-party modules to handle this. Ultimately, we would recommend considering a headless storefront if this is a critical need.

Pages and Hierarchy

While no ecommerce platform would espouse being great at content, most do try their best. Being able to create pages and order them is critical if a merchant is trying to avoid going down the headless route.

Adobe Commerce

Adobe Commerce is backend-powered. Another way to say this is all changes occur in the admin panel. Here, the administrator builds and arranges content, sets page meta information and configures the hierarchy. Pages are assigned to the global scope or to a store view (domain name).

BigCommerce

BigCommerce's Page Builder capabilities are well-integrated into the frontend. When on the front end, administrators can click "Design this page in Page Builder", and many sections are immediately editable. This capability extends to product pages (for descriptions), category pages, and many other, even utility, pages. Note that you cannot edit metadata from the Page Builder area. Instead, go to Channels > [Select Channel], Edit storefront settings > Web pages.

Page Templates

Merchants often create landing pages. Replicating these is made quicker using a template.

Adobe Commerce

Templates can be created, but not edited. Templates simply copy its data to a CMS page—thus, there are no "editable" regions.

BigCommerce

This capability does not exist in BigCommerce. We are not aware of 3rd-party extensions to handle this capability.

Widgets

Wouldn't it be nice to target specific pages (in bulk) and add content?

Adobe Commerce

Adobe Commerce has a powerful editor to select pages and inject content. Administrators can choose from a robust library of content, and developers can create more. This is a rarely-used but capable feature.

BigCommerce

This capability does not exist in BigCommerce. We are not aware of 3rd-party extensions to handle this capability.