Who writes the descriptions
Plugin descriptions on this catalog are written by Alex Morrison, the catalog's lead editor, with assistance from automated content generation tools. Alex has 8+ years of experience evaluating enterprise plugins for Fortune 500 companies across Microsoft 365, Salesforce, and Atlassian platforms.
The process works like this: automated tools extract facts from marketplace listings and vendor documentation, then generate initial description drafts following editorial templates. Alex reviews every draft against the source material, rewrites sections that misrepresent features or add unsupported claims, and approves the final text. All published descriptions have been verified against their sources.
We do not have a team of subject-matter experts writing custom analysis for each plugin. What we have is one editor ensuring the automated drafts accurately reflect what vendors publish, with no embellishment or inference beyond what appears in the source.
What we write and what we do not
Each plugin page contains three types of content, and the boundaries between them are strict.
Factual fields (deployment, pricing, SSO)
These are extracted directly from marketplace listings or vendor documentation. See How We Verify for the full process. We never guess, infer, or fill in missing data with industry averages. If a vendor does not publish it, we mark it as unpublished (—).
Descriptive text (What is X?, Who is it best for?)
These sections paraphrase information from the vendor's own listing and documentation. We rewrite it to avoid copyright issues, but we do not add claims the vendor did not make. If a vendor says their plugin "helps teams collaborate," we might write "designed for teams who need collaboration capabilities," but we will not claim it has specific features the vendor did not list.
What we do not write
We do not write:
- Subjective opinions — "This is the best X plugin" or "Users love this feature"
- Performance comparisons — "Faster than alternative Y" or "More reliable than Z"
- Use-case recommendations — "Perfect for law firms" (unless the vendor explicitly targets that audience)
- Feature evaluations — "The reporting dashboard is intuitive" or "Setup is complicated"
- Vendor endorsements — "Trusted by thousands" (unless the vendor publishes a customer count)
If the vendor publishes customer testimonials or case studies on their listing, we may include those as direct quotes attributed to the vendor in the "What the vendor says" section. We do not rewrite testimonials or present them as independent verification.
Affiliate links and disclosure
No links on this site are affiliate links today. If affiliate links are ever added, clicking one and making a purchase through the vendor's marketplace could earn us a commission at no additional cost to you, and this page and the footer will say so.
If affiliate links are added, they will be marked with a "↗" symbol, open in a new tab, and carry rel="sponsored nofollow noopener". Links to vendor documentation, support pages, and third-party resources are not affiliate links.
Affiliate relationships do not influence what plugins we list, how we describe them, or where they appear in the catalog. The catalog's default order is alphabetical or by last-verified date, and the /best collections are ordered only by explicit marketplace-data criteria (rating, feature count, or update date) that each collection names — never by commission rate or affiliate status. A plugin with no affiliate program receives the same treatment as one with an active affiliate link.
We disclose affiliate relationships in three places: this editorial policy page, the affiliate disclosure page, and the footer of every page on the site. We do not hide affiliate links or present them as neutral recommendations.
Why we publish no ratings of our own
This catalog does not publish its own ratings, scores, or user reviews — we do not evaluate plugins and have no review data of our own. The one place ratings appear is the /best collections, and those numbers are the marketplace's own: the listing's rating and review count as published on the marketplace, shown with their source. There are three reasons we add nothing beyond that.
We cannot verify reviews
User reviews require verification infrastructure we do not have. Without confirming that reviewers are actual users, reviews become noise or manipulation. We would rather publish no reviews than unverified ones.
Ratings imply evaluation
A five-star rating or "Editor's Choice" badge of our own would suggest we have tested the plugin, compared it to alternatives, and judged its quality. We have not done that work. Our role is to report what vendors and marketplaces publish, not to evaluate whether their plugins are good — which is why the /best collections quote the marketplace's numbers instead of scoring anything ourselves.
Ratings create ranking pressure
Once we assign ratings, vendors will ask to improve their scores, dispute ratings, or request featured placement. That turns editorial decisions into negotiations. We avoid that pressure by publishing only verifiable facts — deployment model, pricing, SSO availability — that vendors can correct by updating their marketplace listings.
Error reporting and corrections
If you find an error — wrong pricing, outdated deployment information, incorrect SSO status — report it through the correction form. Include the plugin name, the field that is wrong, and a link to the correct information on the vendor's site or marketplace listing.
We review every error report against the source. If the source confirms the error, we update the listing. If we cannot confirm the error because the vendor has not updated their listing, we reply with what we found and ask you to have the vendor update their official page first.
For legal requests (copyright, takedown, formal notices), use the contact address on the contact page when one is configured.
Editorial independence
We do not accept payment from vendors for inclusion, updates, featured placement, or favorable descriptions. Vendors cannot buy their way into the catalog or pay to appear higher in lists.
Vendors can request corrections through the same process available to everyone else — the correction form or the vendor contact address. Corrections are processed based on whether the marketplace listing supports the change, not based on who requested it.
We do not offer "premium listings," "sponsored placement," or "verified badges" for sale. The "Facts verified" badge on every listing shows the date we last confirmed the data against the source — it is not a paid certification.
Affiliate commissions are tied to user clicks, not to editorial decisions. A plugin with a high affiliate payout does not receive better descriptions, higher placement, or more prominent links than a plugin with no affiliate program.
For questions about this policy, see Contact.