1,432 places to submit your product

Publish a genuinely reusable privacy or accessibility lesson on your tool, give it a stable URL and open license, then add its educational metadata to MERLOT.

Create your original interactive privacy or accessibility guide and add relevant external actions to cited live tools.

Propose a text-based, interactive course on web privacy, security headers, local-first tools, or accessible frontend testing, with practical code exercises and clear outcomes.

Create your real Airflow provider with hooks/operators and documentation metadata, publish it, then add it to Airflow’s Ecosystem page by PR.

After open-sourcing a maintained component, submit the TOML project file and website through GitHub PR.

Offer a substantial free privacy checklist, accessibility workbook, or safety template from a branded storefront and link your tool only as supporting documentation.

Host a genuine public accessibility learning or testing event and submit its dates, description and your tool event URL.

Implement a scoped open-source compliance or security-assurance program, self-certify honestly, then request your tool Community of Conformance listing.

Publish an open-source Sensu check/handler for your tool, create GitHub releases and bonsai.yml, then register it with description and tags.

Create a useful StackStorm integration or automation pack for your workflow, then submit it through the official Exchange Incubator pull-request process.

Build a Bitrise Step that runs your tool secret, privacy, or accessibility checks on explicitly chosen build artifacts.

Create a defensive parser, scenario, or collection for your real -supported log source, document and test it, then submit it to CrowdSec Hub.

Create a TypeScript or Go module that runs your tool web audits in CI and returns machine-readable JSON/SARIF with useful pass/fail thresholds, then publish it to Daggerverse.

Submit your tool through the official reviewed product form.

Create a genuine JavaScript SDK or demo on GitHub Pages and request an appropriate js.org subdomain that links to its official your tool documentation.

Contribute your provider bundle with useful privacy or security components and provider documentation links.

Build and teach a live, project-based cohort on creating local-first privacy tools or accessible web utilities, supported by a substantive public syllabus and real instructor profile.

Share your openly licensed digital-safety lesson pack or Moodle activity and curate it into an educator-focused collection.

Publish a machine-readable privacy, accessibility, or scam-pattern dataset or API and complete its evidence-based public certificate.

Build a functional OPA/Rego privacy-policy integration or developer tool, document it, then add its ecosystem entry and logo through the official docs repository.

Submit a complete, openly licensed privacy/digital-safety textbook already used in higher education.

Publish a free mini-course on privacy, redaction, scam detection, or accessibility with genuine your tool exercises in the curriculum.

Publish a genuinely useful free privacy checklist, redaction template, or safety workbook that complements your tool and has standalone value.

Publish a coherent multimedia field guide on privacy, scam evidence, or accessible documents with cited your tool demonstrations.

Publish a public reproducible privacy-safe research workflow with a Snakefile, README, configuration, catalog metadata, and tests.

Publish a working browser demo or starter that teaches your integration, with accurate title, description and canonical documentation link.

Develop a neutral, sourced learning project about privacy, accessibility, or online-scam literacy and cite your tool only in relevant exercises.

Build a genuine founder or designer profile and publish your detailed UX, accessibility, or privacy-design case study with accurate role and process credits.

Package your free-software self-hosted deployment, implement reliable install, upgrade, backup and restore operations, then submit it to the official app catalog.

Use the free listing path for your tool; evaluate paid multi-directory service separately.

Pitch a practical, outcome-based tutorial on client-side privacy, accessible UI, or web safety using original examples and an honest author identity.

Submit a formal publication, case study, educational resource or on-demand training linking digital resilience to disaster-risk reduction.

Publish your focused open demo or developer utility and link its canonical your tool page from the app and project description.

Apply with an original class outline and teaching sample for privacy-safe design, accessibility, or a practical productivity workflow, then build the class project and lessons if approved.

Create a real founder or researcher portfolio containing original your tool engineering, privacy, and accessibility articles already published under that person's byline.

Submit only your tool tools with a clear civic or public-interest use case, using the official project name, URL, one-sentence description, accurate category, and contact email.

Document a real participatory public-decision deployment as a Case, Method or Organization entry with evaluations and project URL.

Build a ProcessWire admin module for external URL, metadata, accessibility or security audits, register as a module author and submit it to the official directory.

Register a stable, genuinely research-used your tool software, service, or database with accurate maintainer and version metadata.

Publish an original UI/UX visual case study showing your tool interaction design, accessibility states, and design process, with a contextual project URL.