How content on this site is meant to stay useful

1. Working page first

Pages should be anchored by a real tool, a clearly useful support page, or a documented project function. We aim not to publish search-only pages that do not provide original utility beyond a title and a short paragraph.

2. Distinct purpose for each tool page

The classic pages are intended to preserve genuinely different creation experiences. When multiple pages exist, each should represent a different style, workflow, or historical tool rather than a trivial duplicate.

3. Visible explanatory content

We try to explain what a page is for, who should use it, what makes it different, and how to get a better result. That content should be readable by humans, not stuffed with unnatural phrases for crawlers.

4. Public site information

About, privacy, terms, contact, and editorial pages are part of the editorial standard because they help visitors and reviewers understand how the site works. We do not consider those pages optional.

5. No invisible claims

We try not to promise features that are unavailable, fabricate authority signals, or imply endorsements that do not exist. If a feature depends on third-party infrastructure or a legacy runtime, that context should be clear.

6. Ongoing cleanup

If a page becomes outdated, too repetitive, or no longer useful, the preferred response is to improve, merge, or remove it rather than keep it as dead weight. Editorial quality is treated as an ongoing maintenance task.