Magento Open Source Adobe Commerce Storefront design & front-end Independent · not affiliated with Adobe
Magento Themes Store Storefront Lab

Editorial policy

How guides here are sourced, which Magento version each one is checked against, and how errors are corrected once they are found.

Sources, in order of preference

For anything about what the software requires, supports or includes, the primary source is Adobe’s own documentation: the release and lifecycle pages for versions and support windows, and the installation requirements pages for the supported stack.

For a commercial product that is not Adobe’s — a theme, a module, a hosting plan — the primary source is the vendor’s own licence or documentation page. Where a vendor’s own pages disagree with each other, the page says so rather than picking the convenient one.

Agency blogs, roundups and vendor marketing are read, and are not cited as fact. They are the single largest source of wrong version numbers and invented statistics in this topic.

Version checking

Every guide is written against a specific Magento release and says which one. A requirement, a support date or a deprecation is only published after it has been checked against Adobe’s documentation for that release.

Where a release has changed what it supports — a PHP version, a search engine, a cache — the change is stated plainly, because that is the part a store upgrading from an older release will hit first.

Figures this site does not publish

The following are excluded unless they come from a primary source and can be attributed to it: performance or Core Web Vitals scores attributed to a named theme, market-share percentages, counts of merchants or live stores, extension prices, agency day rates, and hosting prices.

These numbers are repeated constantly in Magento content and are usually either a vendor’s own marketing claim, a figure from a survey nobody can locate, or a number that was true for one store once. A guide is more useful without them.

What is never on this site

No sponsored placement, no paid review, no affiliate relationship that decides what gets recommended, and no link exchange. If that changes, it will be disclosed on the page where it applies and on this one, before it applies.

No invented case studies, no invented quotes, and no composite “client” used to illustrate a point.

Reviews and corrections

Guides are reviewed when the thing they describe changes — a new release, a change to the supported stack, a licence change — rather than on a calendar.

When a page is wrong, it is corrected on the page. A correction that changes the substance of the advice is noted in the text, not buried; a typographical fix is not. The review date shown on the page reflects the last time its claims were checked, not the last time a word changed.

Errors can be reported through the contact page. A report that names the page and the specific claim is actionable; one that says a page is wrong in general usually is not.

Questions this page answers

Which sources are preferred for Magento software requirements?
Adobe's own documentation is primary, including release and lifecycle pages and installation requirements pages for the supported stack.
Which sources are preferred for commercial themes, modules and hosting plans?
The vendor's own licence or documentation page is primary. Disagreements between vendor pages are stated rather than resolved conveniently.
Which figures does the editorial policy exclude?
Performance scores, market-share percentages, merchant and store counts, extension prices, agency day rates and hosting prices are excluded unless primary-source attribution is available.
How are errors and corrections handled?
Errors are corrected on the page. Substantive changes to advice are noted in the text, while typographical fixes are not.
Editorial & corrections: [email protected]