Writing a fair review
This page is for creators and journalists who review Exponential: in a video, a post, a newsletter or an episode. A fair review can be critical; it must be accurate, tested and open about how you tested. Nobody at 7x or the Exponential Foundation needs to approve your review, and nothing on this page asks you to be positive.
Contents
- Before you judge: test it yourself
- State your setup
- Separate what you saw from what you read
- Criteria and where to check them
- Limits and gaps worth reporting
- Comparisons
- A review structure and checklist
Before you judge: test it yourself
- Install it yourself, on a machine you control (Setting up a demo installation).
- Do the tasks your audience would do: write and publish, build a page, translate, upgrade, back up.
- Note what failed, with the exact message and the step. If it looks like a bug, report it (When something goes wrong); if it looks like a security problem, report it privately to [email protected] and leave the details out of the review until it is fixed.
- Give yourself enough time; a first impression is a first look, so call it that.
State your setup
Tested: Exponential <6.0.14 | 6.0.15 | main branch, commit or date>
Installed with: <exp:install | setup wizard | kickstarter>, database <SQLite | ...>
Served by: <Apache + PHP-FPM | nginx | Velocity, engine qbix | FrankenPHP>, PHP <version>
Design: <admin4 | ...>; extensions switched on: <list>
Hardware or hosting: <description, without private addresses>
Time spent: <hours or days>
Disclosure: <line>Separate what you saw from what you read
| Kind of statement | How to write it |
|---|---|
| You tested it | "In my test, publishing a folder kept the earlier version." |
| The documentation says it | "The documentation says every record of the audit trail carries the hash of the one before." (link) |
| Someone told you | "<Who> told me ..." - and check it (Claims you must not make) |
| Nobody says | "The sources do not say." |
Numbers belong to the second kind unless you measured them yourself. The speed figures in the README, for example, come with their method; quote them as the README's, and if you measure, publish your method too (Benchmarking).
Criteria and where to check them
| Criterion | Test | Documentation |
|---|---|---|
| Editing and publishing | Drafts, preview, versions, approval | A tour of the administration |
| Page building | Layouts, blocks, shared layouts, mappings | The layouts editor |
| Languages | Translate an item; switch the interface | Languages in Exponential |
| Accessibility | Keyboard only; contrast in light and dark | Keyboard shortcuts |
| Installation | From an empty folder | Installing Exponential |
| Hosting freedom | Databases, operating systems | Database support, Operating systems |
| Security | Two-step sign-in, audit trail, hardening | Security hardening |
| Documentation | Find answers in the built-in help | The help system |
| License | GPL for the code, GNU FDL for the documentation; what passing it on requires | Who is 7x?, Open source licenses; License violations |
| Support and continuity | What is committed, and by whom | The support commitment |
Limits and gaps worth reporting
A fair review reports what the sources themselves admit, with the source:
- Much of what the help describes belongs to the 6.0.15 line, not to 6.0.14 or earlier; say which version you tested
and check its tag with
git tag -l 'v6.0.*' --sort=version:refname(6.0.15 changelog). - All administration translations (the current totals are at the top of Languages in Exponential) are complete (26 October 2026); texts added later show in English until they are translated (Languages in Exponential).
- Velocity's shipped default engine is PHP's built-in server, for development only; the recommended engine must be chosen (Velocity).
- Exponential Platform DXP does not ship a layouts editor (Knowing the product family).
- The sources do not count installations, users or developers.
Comparisons
- Compare like with like: the same task, the same hosting, the same care in setup.
- Describe other products from their own documentation, and date it.
- No multiples ("10x faster") without your own published measurement.
- Be fair to other projects and their people (Respecting other projects and companies, Comparing Exponential factually).
A review structure and checklist
1. Disclosure and setup (version, how installed, how served, time spent)
2. What it is, in two sentences, with the source
3. What I tested, task by task: what worked, what did not
4. Strengths, each with evidence
5. Weaknesses and gaps, each with evidence
6. Who it suits, and who it does not
7. Verdict, labeled as my opinion
8. Sources and corrections policy
[ ] Every fact has a source or is labeled as my own test
[ ] Names right: Exponential, 7x, the Exponential Foundation; eZ Publish only as history
[ ] No unsupported numbers, endorsements, release dates or compliance claims
[ ] Facts sent to 7x for checking, if there is time (not the opinion)
[ ] I know how I will correct mistakesAsking for a fact check is optional. The contact addresses are on the press pages (Press, media and influencers: start here); ask about facts, and keep your opinion yours.
Related pages
- Disclosure and sponsorship ethics
- Claims you must not make
- Correcting a video or post
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.