# About EditorStack

*Source: https://www.editorstack.cc/about — last updated 2026-09-17. Licensed CC BY 4.0 with attribution to EditorStack.*

- EditorStack exists because choosing an embeddable editor means comparing dozens of products whose vendors all describe themselves differently, and no neutral, machine-readable dataset existed.
- Everything on the site is generated from one dataset: the comparison table, the individual profiles, the markdown mirrors, the JSON and CSV downloads and the structured data.
- The site is funded by GJS.Market, which is disclosed on every page and constrained by the rules on the disclosure page.

## What this site is

EditorStack is a reference for one decision: which library, SDK or platform you should use when your
product needs a visual editor inside it.

That decision is unusually hard to research. The products call themselves different things — page
builder, visual editor, experience platform, content SDK — and their marketing pages are not
comparable. Half of them cannot do the job you have at all, but you only discover that after
reading the documentation. The measurements you actually need, such as what the library costs your
bundle, are published by nobody in a comparable form.

So the site does four things:

1. **A structured dataset of 34 products**, where every field means the same thing across every
   entry, and every fact carries a source and a date.
2. **First-party measurements** — bundle sizes and time-to-first-editor — run under identical
   conditions with published scripts.
3. **Written analysis** that says who each product is wrong for, not only who it is right for.
4. **Open data**: the whole dataset as JSON and CSV under CC BY 4.0, plus a markdown twin of every
   page for machines that do not run JavaScript.

## How it is made

One YAML file per product is the single source of truth. The comparison table, the individual
profiles, the category pages, the structured data, the markdown mirrors and the downloads are all
generated from it, which is why the table can never disagree with a profile page.

A schema validates the data on every build. It refuses incomplete records, refuses a score without a
written rationale, and refuses a bundle size that does not match the measurement run that produced
it. A build that would publish an unsupported number fails instead.

The site is a static export with no server, no cookies and no tracking scripts beyond privacy-
preserving, cookie-free analytics.

## Who writes it

Editorial work is produced by the EditorStack Research Team, funded and operated by the team behind
GJS.Market. Named author profiles will appear here as contributors are added; until then, the
attribution is collective rather than a fabricated byline, because inventing an author with a
photograph and a LinkedIn profile would be the exact kind of trust signal this site is supposed to
be an antidote to.

## Funding

EditorStack is funded by [GJS.Market](https://gjs.market), which sells plugins and templates for
GrapesJS. Three entries in the dataset are affected by that relationship and each says so above the
fold. The full statement, including the specific rules that constrain it, is on the
[disclosure page](/disclosure).

## Contact and corrections

Corrections are welcome and are published with a date in the [changelog](/changelog). Open an issue
on [the repository](https://github.com/GoodPHP/gjs-comparison), including the source for the fact
you are correcting. Vendors may submit corrections about their own products under the same rule as
everyone else: we check the claim against a source before it goes in.