Editorial policy and testing methods

Responsibility and purpose

The photocraft.tools maintainer is responsible for the guides and website content. Our purpose is to help readers complete useful tasks with a clearly identified version of PhotoCraft and understand where it may not meet their needs. We do not invent professional credentials, named reviewers or a larger editorial team. Questions and corrections go to hi@photocraft.tools.

Three kinds of evidence

An observed result describes an operation actually performed in the stated environment. It should identify the software version, input, procedure and output. A statement based on upstream documentation identifies that source and relevant version. An unverified capability is explicitly described as unverified rather than implied by a related feature or a successful startup screenshot.

For example, our small PNG-to-PSD round trip checks the exported appearance of one synthetic image after saving and reopening in PhotoCraft. It does not establish complex layer preservation, Photoshop reopening or professional color fidelity. The PSD guide publishes the sample and limits. Performance numbers require actual measurement; a software-rendered browser test is not a benchmark for physical devices.

Sources, versions and attribution

Prefer upstream source, release artifacts and official documentation for software claims. Guides identify the pinned v0.12.0 browser editor separately from desktop applications and ArtCraft Launcher. Links to sources help readers inspect the basis of a statement. Quoting or paraphrasing upstream material does not make it a first-party test.

We retain licenses, notices and provenance for the self-hosted editor. Original sample images and workflow screenshots are identified as demonstrations rather than user submissions. Third-party images or text need appropriate permission or license. We do not present this independent website as ArtCraft or Adobe.

AI assistance and translation

AI tools can assist with drafting, translation, organization and code. Automated translation may be used to create a first localization draft. Such output is not treated as a factual source, a test result or proof of native-language review. Technical tokens, commands, URLs, versions and limitations must remain accurate across English, Chinese and Brazilian Portuguese.

Translations should preserve the substance of the guide. We do not add invented regional facts to make language variants look different. If a local interface label differs from the upstream English-only editor, the guide should explain that distinction. Readers can report an awkward translation or a technical mismatch through Contact.

Updates and corrections

Dates identify substantive content changes, not a claim that every linked release was freshly installed on that date. Test records carry their own scope and environment. When a result is rerun, its published evidence must match the accompanying explanation. A change in the upstream repository does not silently update the hosted editor.

The changelog records material website revisions. A correction should remove or qualify the inaccurate claim and update affected language versions. We do not erase a known limitation by replacing it with a vague statement that the software is improving. The page should explain what the current evidence supports.

Advertising and independence

No AdSense advertising is currently integrated. If advertising is introduced, it should be labeled and kept separate from editing controls, download actions and judgments about software. Ad placement is not evidence that an article or product has been endorsed by Google. Future vendor and consent disclosures must match what is actually deployed.

This site currently has no public comments, forum or submission publishing workflow. Sending an email does not authorize public publication of its content or attachments. Any future public contribution feature needs its own moderation and rights process before launch.