Our guides are verified through documentation, source comparison and editorial review. We do not install or run Procreate, test iPads or printers, or create our own benchmarks. This page explains how that research becomes a usable instruction.
Define the reader's task
Begin with the result the reader needs: contain a ColorDrop fill, preserve an editable mask, recover room in a layer stack or prepare a file for a printer. A symptom must be specific enough to distinguish the relevant causes. An escaping fill, a pale edge and a fill following the wrong layer need different checks.
The guide should identify the relevant platform, starting state and destination. Independent tasks stay on their own pages when including them would distract from the current decision.
Check the primary evidence
Official documentation establishes the documented controls, formats and limits. A receiving service's requirements govern that destination. Source notes retain the supported claim, its conditions and the date it was checked; a release number matters when it changes the instruction.
Search results and community discussions help identify competing explanations and unanswered questions. They do not replace primary fact-checking. A forum report is attributed to its source, and an external measurement retains its original setup and author.
Read the sequence as an instruction
Review each step against the documented starting state, control and expected behavior. A path that ends at the right panel can still be incomplete if the active layer, visibility, Alpha Lock or a required format changes what happens next.
The text should tell the reader what to inspect after the action and what to do if the expected state is absent. This is a logical review of the instructions. It does not establish that we performed the workflow or reproduced a reported problem.
Place the risk before the action
Merging, resizing, deleting and converting can remove editing options or data. The relevant guidance must explain that consequence before the action and preserve an appropriate native source or copy.
For a backup, the reader may need to reopen the copied file and inspect its layers. For an export, the saved file and receiving application may need separate checks. Those are verification steps for the reader, not claims that our editorial process produced a tested file.
Keep examples and visuals honest
An example uses stated inputs to explain the reasoning. Calculated dimensions are calculations, and an attributed result belongs to the source that reported it. Neither is described as a measurement made by this site.
A diagram can explain which layer owns an edit. A control view must use labels and states supported by current authoritative references. Images are checked against the guide and cannot prove that an operation was executed or an output passed a device test.
Review the complete page
Before publication, review the facts, the reading experience and the page itself. Check that the title matches the task, links support their adjacent claims, images load and the instructions remain readable on desktop and mobile. Any structured data must describe the same visible article and author.
Keep unresolved material claims out of a recommendation. When a documented product change affects a control, limit or destination, revisit the affected wording and its dependencies rather than treating an old date as proof of continuing accuracy.