Problem selection
A guide must address a recognizable production-engineering failure with a distinct diagnostic path. The site does not publish separate pages for trivial wording variations of the same error.
Primary sources
Technical claims should link to official project documentation, standards, vendor manuals, or original specifications. Community posts may reveal a symptom, but they do not become the authority for a command or security claim.
Diagnostic value
Each guide must help the reader locate a failure boundary, collect evidence, choose a reversible action, verify recovery, and avoid at least one risky shortcut. Word count alone is not evidence of quality.
Commands and examples
Commands use placeholder domains, users, and paths. They are documented examples, not reports of tests on a reader’s infrastructure. Destructive operations require an explicit backup and scope warning; credentials and personal data are never included.
Software assistance
Software may assist with research organization, drafting, formatting, and automated checks. The responsible editor reviews meaning, sources, command scope, internal consistency, and disclosure before publication. Pages are not generated as search-keyword permutations.
Updates and corrections
An updated date changes only after a meaningful technical or editorial revision. Corrections should preserve enough context to show what changed. Send corrections to editor@fulmemo.com.