The Magento 2 knowledge centre

With the “Magento 2 from the ground up” path at the top of this page. The first step explains what the platform is and which processes it serves; the third and fourth take you into the open demo, where you can walk the storefront and the admin panel yourself. Costs and how a build runs are worth reading after that.

Magento 2 is an e‑commerce platform on which a store is built along with its catalogue, prices, cart, orders and integrations with the company's systems. It fits complex catalogues, B2C and B2B sales on one instance, and serving several markets. The full explanation is in Magento 2 – what it is and what it is for.

They are two lines of the same platform. Magento Open Source is free and holds the core of a store's features. Adobe Commerce is commercial and adds, among other things, the B2B extension, marketing tools and vendor support. The differences are set out in the article's section on the platform versions.

Yes. We run an open Magento 2 demo — a storefront and an admin panel, with no account and no contact with us. The login details are on that page, and the environment resets every 6 hours.

Yes. In standard Magento Open Source, B2B selling rests on customer groups, price rules and the store view configuration; the B2B extension is part of Adobe Commerce. The scope of such a project is described under a B2B build on Magento 2, and a live B2B platform is shown by the Hulajnogi Micro case study further down this page.

Yes, and it is one of the platform's stronger points. One instance serves several websites, stores and store views, and with them separate languages, currencies, taxes and catalogues. What that looks like in practice is shown by the Diablo Chairs case study.

Adobe publishes security patch releases several times a year, and new version lines less often. Security patches go in as they come; moving to a new version line is a project of its own, because it touches modules and custom work. The rhythm is agreed with the maintenance scope rather than fixed once and for all.

In the Adobe Experience League documentation (opens in a new tab). The old devdocs.magento.com address is dead and is not worth citing — Adobe moved the whole of the Commerce documentation to Experience League.

Yes — it is one of the six areas of this centre (“Running a Magento 2 store”). We publish material on working in the panel: the catalogue, categories, customers, orders, promotions and CMS content. Some of it is still in preparation; we do not put out empty cards, so the list shows only what can already be read.

The centre is for people accountable for choosing, implementing, maintaining or growing an e‑commerce platform. The material is meant to show the business consequences CEOs and E‑commerce Managers need, and the technical context IT teams need.

The centre gathers ordered material about Magento 2 that is meant to be grown and kept current. The Aurora Creation blog (opens in a new tab) is the place for commentary, events, current changes and content about the company itself.

Each publication states its scope next to its title. Where the difference between platform variants changes the answer, the article describes them separately.

No. They help you understand the dependencies and prepare your questions. The scope of a specific project still depends on the sales model, the quality of the data, the integrations, the current code and how the team works.

Every article carries the date it was last verified and the name of its author. We re-check the copy whenever something changes that would change the answer, and move the date to the day of that review.

The scope of implementation, migration, maintenance and growth is on the Magento 2 services page. The knowledge centre remains the educational part of the site.