Opens in a new tab
mfgatlas

Home / Editorial standards

Editorial standards

How member articles are prepared, reviewed and corrected.

Useful engineering knowledge needs context, traceable evidence and a clear account of what remains uncertain. These standards apply to articles in the MFG Atlas engineering notebook. Forum discussions remain member conversations and are not automatically reviewed articles.

Current stage: we are establishing the editorial workflow. Contributor names are profile display names. We do not currently offer verified expert credentials or independent peer-review certification.

Keep the scope specific

We accept work about hydraulics, injection molding, mold engineering and equipment maintenance. A field note reports an observed case; a technical explainer develops an argument from evidence; a reference guide organizes sources for a defined use. State the equipment, material, operating conditions, versions and limits that matter. Do not turn one successful case into a universal rule.

Show the basis of a claim

Describe the method, measurements or analysis behind a conclusion. Separate direct observations from interpretations. Include uncertainty, exceptions and unresolved questions. Prefer manufacturer documentation, issuing standards bodies and original research over unattributed summaries.

For each reference, a title and HTTPS link are required. Author or issuing organization, edition or version, page or section, access date and the claim it supports are optional details that help readers. Original findings need a stable public methods or data record. A link is a pointer to evidence; it is not proof that the conclusion is correct. Do not upload restricted standards, customer drawings or material you lack permission to share.

Disclose interests and assistance

Declare relevant employment, supplier relationships, funding, sponsorship and AI assistance. State none where applicable. Authors remain responsible for checking facts, quotations, units, calculations and references. AI output is not a primary source or an expert reviewer.

Review before publication

Members can save incomplete drafts. Submission requires a title, article body, engineering topic and at least one source with its title and HTTPS link. Scope, method, limitations, disclosures and other source details are optional fields; they can be added during review. Articles enter a pending queue; an editor must inspect the saved content, sources, applicability, limitations and disclosures before recording a check and publishing through WordPress.

A recorded check identifies the operating account and date. An author checking their own work is labelled as an author self-check. A check by another editor is labelled as an editorial check. Neither label means independent peer review, verified professional qualifications, equipment certification or guaranteed correctness.

Make changes visible

The check is tied to the saved title, body, summary, author, evidence record, engineering topics, tags and cover attachment. Changes to those fields invalidate its current status. Article records can show “No recorded editorial check,” “Changed since the recorded check,” “Editorial recheck due,” or “Editorial check recorded.” Read the status together with the underlying evidence. This version record does not verify the contents of external websites or detect changes to an image file itself.

Editors set a recheck interval of 90, 180 or 365 days. A due date is a maintenance signal; it does not establish that the article is current or correct. Unchanged articles are not automatically removed when the date passes. Review and correction notes remain with the article. Native WordPress revisions support content recovery.

Correct errors openly

Report an error with the article URL, the affected claim and supporting evidence. Editors should assess the report, record a clear correction note, recheck the affected version and explain any unresolved limitation. Where a technical claim cannot be supported, it should be corrected or withdrawn rather than given a stronger label.

Members revise published articles through a separate proposal. The current public version remains available during drafting and review. An editor checks the saved changes and evidence before explicitly applying the revision. The article keeps its URL, original author, first publication date and discussion; the previous content and evidence are retained in the internal revision history. If the public article has changed in the meantime, the proposal must be reconciled with the current version before it can be applied.

Make the record reusable

Each public article links to a machine-readable evidence record with its saved version, sources, check status and recent public correction notes. Article metadata also carries source references and the version identifier. Check the status and dates when reusing a record: a source change or an expired check must not be treated as a current editorial check. Private drafts and internal revision snapshots are excluded from the public record.

Author names identify contributor profiles; employment relationships and professional qualifications are not inferred from membership. Version identifiers describe the saved content and evidence, not a digital signature or proof of correctness.

Contribute an article →   Read the community rules →

Policy version: 27 October 2026. This page describes our process and its current limits, not a promise of professional or regulatory approval.