Becoming a Certified Developer

4 Aufrufe Markdown

The certified mark shows developers who passed our review and keep their standard: the five criteria, what the mark gives you and how it is lost.

Overview

Certification is not bought and not requested on a form. It is earned: developers who meet the criteria are reviewed, and the mark is granted by the team.

You cannot switch it on yourself. The profile dialog edits your name, tagline and links; the mark and whether the profile is published are the team's decision.

The mark is not permanent. It is reviewed periodically and can be removed when the standards are no longer met.

Prerequisites

At least three published products Add-ons or themes live on the Marketplace. Drafts and pending submissions do not count.
A 4.0 or higher average rating Computed from the reviews your published products received.
Code and security review A separate review run by the WISECP team. It is broader than the one each submission goes through.
Compatibility with the current release Your products keep working with the current WISECP version.
Answers within 24 hours How quickly customer questions are answered. This is why the support address on your profile matters.

Structure

The mark appears on three screens and means the same thing on all of them.

WhereWhat changes
Developer directoryYour card carries the mark and certified developers sort to the top of the list
Your public profileThe mark sits next to your name; visitors can open it to read the criteria
Product pagesIt appears in the byline, beside the developer name

The directory sorts by certification first, then by the rating the products earned, then by how many are published. The mark lifts you above developers with a similar rating.

Walkthrough

Meet the criteria

  1. Get three products live. The first usually takes longest; the next ones move faster through the same path.
  2. Watch the reviews. The average is computed from all your published products, not from the best one.
  3. Test your products on each new WISECP release and ship a new version when one is needed.

Be ready for the review

  1. Fill in the support and contact addresses on your profile. The response criterion runs through them.
  2. Keep your product documentation current. Products with missing setup steps generate questions.
  3. The code and security review is run by the team. There is no separate form to fill in.

Keep the mark

  1. Reviews repeat periodically, and the mark can be removed when the criteria are no longer met.
  2. Retiring a product lowers your published count and may put you under the three-product threshold.
  3. If the mark is removed, your profile and products stay live; only the mark and the sorting priority go.

Reference

Who grants it The WISECP team only. Neither the mark nor the published state can be changed from the developer's profile dialog.
Directory visibility The directory lists only profiles with something published. An approved developer without products does not appear.
Where the figures come from Product count, rating and review totals on your profile are derived from your products, not stored on the profile.
Periodic review Repeated at intervals. The mark can be removed when the criteria are no longer met.

Example

The five criteria are read one by one; meeting four of them is not enough.

Reading the criteria
Published products : 4        -> met (three or more)
Average rating     : 4.3      -> met (4.0 or higher)
Compatibility      : v5 ready -> met
Response time      : ~2 days  -> not met (24 hours)
Code review        : pending  -> run by the team

This profile clears the numbers but misses the response criterion. The mark is not granted until the missing one is addressed.

Pitfalls

One product cannot carry the average

The rating comes from every published product. Leaving an older, poorly rated one unmaintained pulls your newer products down with it.

The mark is not permanent

Each review asks whether the criteria still hold. Retired products and unanswered questions can take it back.

Certification does not replace product review

Every new product and every new release from a certified developer still goes through review.

War das hilfreich?

Vielen Dank für Ihre Rückmeldung!

Brauchen Sie weitere Hilfe?

Unser Support-Team ist rund um die Uhr für Sie da, wenn Sie oben nicht fündig werden.