OpenCraftTools is an independent Craft portal, not the official site for ArtCraft, PhotoCraft, VectorCraft or their launcher. We do not distribute or repackage desktop binaries, and we do not run a cloud version of their apps. Where an upstream static WebAssembly build is published, we may serve that fixed package on the same origin for browser testing. We verify repositories, releases and limits, then document what is available today.
A page goes live here when its facts resolve to a source: a repository file, a release asset, a release note or an upstream document. We do not print star counts as proof of quality, we do not describe an alpha feature as a shipping one, and we do not write that a tool replaces a commercial product. Where the honest answer is "not yet" or "depends on your hardware", that is the answer the page gives.
Repository, licence file and release assets are read before anything is written.
Draft copy describes verified behaviour, with limits named in the same section as the capability.
Commands are checked against the upstream documentation and available release assets. A guide that has not passed its stated evidence check stays out of the published set.
The source bar records the URL and the verification date, and a re-check updates the date rather than silently rewriting history.
If upstream changes or a fact ages out, the page moves to a stale state, leaves the sitemap and says what happened.
If something on a page is wrong, the fastest fix is to tell us which claim, which source you believe is correct and when you checked. Corrections are treated as editorial work, not as a nuisance: a portal that quietly keeps printing an outdated platform list deserves to be ignored.
The portal is maintained as an independent editorial guide. Articles are checked against upstream sources; machine assistance may organise query data or draft structure, but it does not turn an unverifiable claim into a published fact.
No. There are no affiliate download links and no paid placement in the directory, which is why every button on the site points to the upstream release instead of a mirror.
A weekly audit checks the repositories for archive status, licence changes and broken release links. When something fails, the affected page is taken out of the sitemap and marked out of date rather than left to drift.
If it is a real creative tool with a public repository, a stated licence and a build you can install, it can be proposed. It will still go through the same four checks in the directory criteria before it gets a page.
