Editor Stack Weekly
A weekly digest of what changed in the visual editor ecosystem: new measurements, price changes we caught, products entering and leaving the dataset, and corrections we published.
TL;DR
- Editor Stack Weekly is a short email about changes in the visual editor and page builder ecosystem, sent no more than once a week.
- It exists because the most useful thing this site produces is not the reviews but the diffs: a price that moved, a licence that changed, a benchmark that was re-run.
What you get
Changes to the data, not opinions about it. When a vendor changes a price, when a licence changes, when a product enters or leaves the dataset, when a benchmark is re-run and the numbers move — those are the emails.
Corrections, in full. When we get something wrong and fix it, subscribers hear about it in the same detail as the changelog records it. A reference that only tells you about its successes is not one.
New research when it lands, which is rarely and only when there is a measurement worth reading.
What you do not get
No drip sequence, no "5 tips" filler, no sponsored post pretending to be editorial. The list exists to distribute changes to a dataset, and if there are no changes worth your attention in a given week, nothing is sent.
About the funding, since it applies here too
EditorStack is funded by GJS.Market, which sells plugins and templates for GrapesJS. The digest occasionally mentions their products, and when it does it says so in the same sentence — the same rule the site works under, set out on the disclosure page.
We do not sell, rent or share the list. Unsubscribing is one click and takes effect immediately.
Where the sign-up form is
The form appears at the end of the use case guides and the research pages — the places where somebody has just finished reading something and might plausibly want the follow-up. It does not appear as a pop-up, an interstitial or a scroll trap, because those would cost more in trust than the addresses are worth.
Written by the EditorStack Research Team. How we test and what we refuse to publish is on the methodology page.