docs: clarify what dev-resources accepts

Developer audience is the criterion; having an API no longer disqualifies a
resource. dev-resources and public-apis overlap by design - a developer tool
with a public API belongs in both, and a listing in one is not a duplicate of
the other. Paid products are accepted.

Author: marcelscruz

CONTRIBUTING.md

@@ -20,11 +20,13 @@ Everyone is welcome to collaborate to this project, but please take into conside
 
 Before submitting, make sure your resource meets all of the following criteria:
 
+-   **For developers** — the resource must be something developers would use to build software. Free or paid, both are fine. Products aimed at a non-developer audience are not accepted, however well made they are
 -   **Main product only** — the resource must be the main product itself; internal tools or features of a larger product are not accepted
 -   **Custom domain required** — projects hosted on shared subdomains (`vercel.app`, `netlify.app`, `herokuapp.com`, `github.io`, `pages.dev` and similar) are not accepted
 -   **Available now** — no waitlists, betas behind closed signups, or "coming soon" products
 -   **Quality bar** — low-effort projects are not accepted
--   **APIs belong elsewhere** — API submissions should go to the [public-apis](https://github.com/marcelscruz/public-apis) repository, or be submitted directly on https://publicapis.dev/submit
+
+Having an API does **not** disqualify a resource — most developer tools have one. If your product also exposes a public API that others can connect to, it belongs in [public-apis](https://github.com/marcelscruz/public-apis) **as well**; the two directories overlap on purpose, and a listing in one is not a duplicate of the other.
 
 Submissions are reviewed by an automated reviewer first — a bot account may comment on, approve, or close your pull request — and by the maintainer for the final merge.