Editorial Policy

Editorial mission

Linix.online aims to publish practical Linux documentation that is accurate, reproducible, security-conscious and useful in real environments. Tutorials should help readers understand the task, complete it safely, verify the result and diagnose common failures.

Topic selection

Topics may be selected according to reader needs, ecosystem coverage, software releases, search demand, internal-linking opportunities and gaps in the existing documentation library.

Publishing order is designed to build coherent technical ecosystems rather than an unrelated collection of posts.

Required tutorial structure

Where appropriate, tutorials follow a consistent sequence that may include:

• Introduction
• Learning objectives
• Prerequisites
• Lab environment
• Installation
• Configuration
• Verification
• Troubleshooting
• Security best practices
• Frequently asked questions
• Conclusion

Not every page requires every section, but procedures should remain logically ordered and easy to navigate.

Technical standards

Articles should:

• Identify relevant operating-system and software versions
• Use real package names, service units, file paths and commands
• Avoid obsolete or unsafe methods where a supported alternative exists
• Separate commands from explanatory text
• State when elevated privileges are required
• Protect credentials and private information
• Prefer least privilege and limited network exposure
• Include verification evidence
• Include rollback, restore or recovery guidance where material

Sources and verification

Technical details may be checked against official documentation, release notes, package repositories, standards, source projects and reproducible testing. Primary sources are preferred for commands, supported versions, repository configuration and compatibility claims.

Where a procedure cannot be verified directly, the limitation should be considered during editorial review and the article should avoid overstating certainty.

AI-assisted workflow

Artificial intelligence may assist with planning, drafting, restructuring, language improvement and metadata. AI output is subject to structured validation and should not be treated as authoritative merely because it is fluent.

Our separate AI-Assisted Content Policy explains this process in more detail.

Security-first guidance

Security recommendations should reflect the actual technology and context. Articles should avoid generic advice such as disabling security controls, making files world-writable, exposing administrative services publicly or bypassing certificate verification as a permanent solution.

Clarity and accessibility

Writing should be direct, professional and understandable to the intended audience. Unexplained jargon should be limited. Headings, lists, tables, code blocks, diagrams and navigation should help readers scan long tutorials.

Search optimisation

Titles, descriptions, headings and internal links may be optimised for search visibility. Search optimisation must not justify misleading titles, unsupported claims, excessive keyword repetition or content written primarily for algorithms rather than readers.

Images and diagrams

Featured images and technical diagrams may be generated or processed automatically. Visual assets should accurately reflect the article topic, remain readable and avoid implying unsupported affiliations or endorsements.

Advertising and editorial independence

Advertising, donations or commercial relationships should not determine the technical conclusion of an article. Sponsored content, affiliate relationships or material commercial influence should be disclosed clearly.

Updates and maintenance

Articles may be reviewed when:

• A supported software release changes
• A repository or package source is replaced
• A command becomes obsolete
• A security issue changes recommended practice
• A reader reports a reproducible error
• Broken links or outdated screenshots are found

An updated date may be displayed when material changes are made.

Corrections

Verified errors should be corrected promptly and proportionately. Significant corrections may be documented. Minor spelling, formatting and clarity edits may be made without a separate notice.

Feedback

Editorial and technical feedback can be sent to corrections@linix.online.