Useful guidance. Clear boundaries.
How to read the directory, interpret its sources, and contribute a precise correction.
Separate discovery from endorsement.
Directory entries identify places to investigate plugins, modules, apps, and integrations. The resource type and official destination are shown so that readers can distinguish a catalog from a protocol reference or a help article. These resources are not interchangeable products.
Inclusion is not a claim that a tool is suitable, secure, free, or compatible with every environment. The site does not display invented product ratings, customer reviews, or download counts. It does not represent its directory links as commercial partnerships.
Use official sources for product-specific facts.
The directory points to platform-operated catalogs, registries, and documentation. Those destinations support resource identification and provide the next place to check current capabilities, requirements, and availability. Technical guidance in the Lab includes a directly relevant editorial source link.
Practical checklists are evaluation methods, not reports that every named product has been tested in every configuration. Readers should distinguish an observed or documented capability from a question the guide recommends asking. Missing information should remain a question until an applicable source or test resolves it.
Keep decisions specific to the project.
The guides encourage a clear requirement, representative tests, and a record of responsibilities. They do not promise performance improvements, search rankings, complete security, or accessibility certification. An attractive interface or a successful installation is not the same as a verified end-to-end workflow.
Check current publisher documentation for version requirements, permissions, plans, pricing, and removal procedures before acting. A resource can change independently of this site, and a product’s broad category does not establish the exact capabilities of an individual listing.
Make corrections actionable.
Send the affected page, the specific statement or link, the proposed change, and an authoritative supporting source through the Contact page. Do not include private credentials or customer information. For account or product support, contact the relevant publisher directly.
Read by platform or by question.
Start from the directory overview to choose an ecosystem, or use the Lab’s categories and topic archives to investigate a workflow. The purpose is to make the next question easier to ask—not to make a project-specific decision on the reader’s behalf.