Our editorial approach
A useful guide should explain its limits as clearly as its steps.
The Projectear voice
Start with an everyday snag. Explain the relevant idea without assuming specialist knowledge. Offer a short set of checks, then say what those checks cannot establish. That is the pattern behind our practical guides.
Projectear editors is the journal’s house byline. It describes responsibility for the publication, not a claimed professional qualification or a fictional personal biography.
Sources before shortcuts
We prefer original documentation, published standards and first-party records. Links sit alongside the guidance they support. We distinguish a formal requirement from a practical suggestion, and a historical source from current information.
A software setting can change. A statement about a particular version should identify that version or its source. If we have not carried out a hands-on test, we do not describe a product as tested.
Examples and illustrations
Sample scripts and checklists are editorial aids, not quotations from research participants. Diagrams and conceptual illustrations explain a topic; they are not evidence that an event happened. Historical pages identify their archival and other sources, and new illustrations are not presented as historical photographs.
Corrections
Send the page URL, the disputed passage and any supporting source to [email protected]. We check the underlying evidence before changing a factual claim. Substantial corrections should explain what changed; routine spelling or layout fixes need no separate notice.
Dates and history
An update date refers to the current article. It does not make every historical statement current. Our German PRO.ject.EAR history section concerns an earlier organisation and is separate from the present English-language journal.