A guide is published when it answers a real task with supported facts and a clear way to act. Accuracy takes priority over the number of pages.
Sources and version checks
WordPress behavior is checked against WordPress.org documentation, Developer Resources, Make WordPress and core source where needed. Third-party product information uses its official listing, documentation, changelog or source repository. Community questions help identify problems; they do not replace technical verification.
A review date means the stated sources were checked on that date. Documentation checked against WordPress 7.1 describes a documentation check, not a live installation test. The launch's current stable release was verified as 7.1.3 on October 7, 2026.
What testing means
Hands-on tests must identify the environment and observed result. A source-code observation is labeled separately from a runtime result. Third-party benchmarks require attribution and their conditions. Launch tutorial pages do not claim hands-on WordPress UI tests.
Original pattern and template markup is structurally validated with WordPress's block parser. That checks block structure and declared core-block attributes. It does not establish identical appearance across themes or compatibility with every plugin. Previews render the supplied markup with a documented neutral baseline.
Theme and plugin research
Selection guides examine the task, core capabilities, documented functionality, free and paid limits, current official source, update activity and declared compatibility. They also consider setup, portability and data processing when relevant.
A directory's tested-up-to declaration is the publisher's declaration. It is not a RoarWP certification. The launch research records the verification date and retains a source ledger. When a source does not establish current compatibility, the guide says so.
Themes and plugins receive no invented numerical score. Marketing performance claims are not repeated as measured results. RoarWP has no paid rankings, sponsorship placements or affiliate links in this launch.
Updates and corrections
Version-sensitive guides need a new review when the relevant interface or documented behavior changes. Sources and metadata should be updated together. A changed review date is recorded only after a substantive check; cosmetic edits do not imply fresh technical verification.
A factual correction should describe the affected URL, disputed instruction and supporting evidence. Contact explains the available reporting route. Major changes should also be recorded in the internal source ledger so the original basis remains traceable.
Content with unresolved material errors should be corrected, merged or withheld. A smaller library of usable guides is preferable to publishing a plausible answer without evidence.