Editorial policy

Publication states

Resources move through draft, review, published, and needs_update. Drafts are not routed, linked from published pages, or included in the sitemap.

What we will not invent

• Statistics, case studies, or merchant testimonials without sources
• Software pricing, ratings, or adoption claims without verification
• Named authors who are not real contributors
• Hands-on testing labels for products that were only researched

Software research

App profiles require an official website when available, platform support, verified features, a verification date, limitations, and an affiliation disclosure. Elevixa ownership is always disclosed. Comparisons use explicit criteria and are not published as rankings until evidence exists.

Tools

Calculators label outputs as modeled estimates, explain formulas, and keep business-sensitive inputs in the browser by default.

Publishing checklist

Internal editors follow About positioning and the repository publishing checklist before marking a resource published. Every public page should state the intended reader, the problem it solves, the primary search intent, verification status for material claims, and useful related resources.