ElanoryaEditorial policy
How this site is written
Published because the standard behind a page is usually invisible, and because a site that publishes specifications and comparisons should be checkable on how it produces them.
How facts get onto this site
Anything about an external platform comes from that platform's own documentation. Not from another site's summary, and not from memory — from the source, read on a date that gets recorded and shown. Where a source blocks automated fetching, as Etsy's help centre does, verification is a manual browser step and that is recorded rather than skipped.
Every one of those facts has a review cadence and an owner. Marketplace rules are reviewed monthly because they change without announcement; a specification page that has quietly gone stale is worse than no page, because it carries the authority of a reference and the accuracy of a rumour.
Numbers live in one shared module per source, and pages consume that module. No figure is typed into a page by hand, which is why two pages on this site cannot disagree about the same rule.
The rules, stated plainly
These are enforced by build gates rather than by good intentions, which is the only reason they are worth publishing.
- No invented statistics
- No percentage, benchmark, user count, rating or review appears unless it was actually measured. Pages that would need one simply do without.
- No fabricated authors or reviewers
- Content here is drafted with AI assistance and reviewed by the operator. No page carries an invented human byline, and no page claims a review that did not take place.
- Machine translation stays unindexed until reviewed
- A machine-drafted translation renders for review but carries noindex and is excluded from the sitemap. The system that produced the draft is not permitted to mark it reviewed.
- No competitor claim without first-hand testing
- Comparisons require an account used, images run and outputs kept, with a date. Until then the comparison page publishes the evidence it still needs.
- No product claim without the product
- A page describing a capability that has not shipped is built but held out of the index until the capability actually exists.
- No stock imagery as product evidence
- Every example must be an owned source photograph with its own output. The component that renders examples cannot display an unapproved asset in a production build.
Questions
Is this content written by AI?
It is drafted with AI assistance and reviewed by the operator before publication. We disclose that rather than inventing a human byline, which is the more common approach and the less honest one.
What happens when something here is wrong?
It gets corrected on the page. Editorial notes carry a date and are not silently edited — if a view turns out to be wrong the honest response is a new note, not a quiet rewrite of the old one.
Why do some pages exist but not appear in search?
Because they are held. A page can be finished and still be waiting on real product imagery, a capability that has not shipped, evidence that has not been gathered, data that has not been measured, or a translation that has not been reviewed.
Who reviews the translations?
A native speaker, before a locale is published. Until that happens the translated page renders for review but stays out of the index — and the system that produced the draft cannot promote its own work.