This methodology explains how CodeStap should evaluate products before presenting them as recommendations or detailed reviews.
Research sources
Research may include the official product listing, developer documentation, changelog, live demonstration, support information, license, technical requirements, customer-facing policies, and credible information about known limitations.
Evaluation criteria
- Intended audience and use case
- Feature completeness and clarity
- Responsive design and accessibility considerations
- Compatibility and stated technical requirements
- Documentation, setup process, updates, and support
- Performance and code-quality indicators when they can be assessed
- License, price, renewal terms, and overall value
- Important limitations, dependencies, and alternatives
Hands-on testing
A page should claim hands-on testing only when an editor has actually installed, used, or directly examined the relevant product. Otherwise, the page should clearly rely on documentation, demonstrations, and provider information.
Rankings and “best” lists
Rankings should be based on the needs of the stated audience rather than a universal score. A strong product for one project may be inappropriate for another. Lists should explain selection criteria and include meaningful differences between options.
Re-evaluation
Products may be reviewed again after major releases, price or license changes, discontinued support, broken links, or credible reports of significant problems.