About Discussion Dictionary

Discussion Dictionary is an independent English learner's dictionary and language reference platform. It is a project of Discussion Publishers, an editorial house building open, well-cited reference works for global learners, teachers, researchers and developers.

Who we are

Discussion Publishers is the parent organisation behind this dictionary. Our editorial team includes lexicographers, ESL teachers, linguists and software engineers who work together to publish clear, learner-friendly English definitions with source citations, IPA pronunciation, part-of-speech guidance, revision history and CEFR level tagging.

Every entry on Discussion Dictionary — from everyday words like flour to names like Mary, technical vocabulary, idioms and slang — is designed to answer the questions learners actually ask: what does it mean, how is it pronounced, where does it come from, and how is it used in real sentences.

What we publish

  • Definitions — clear, learner-first meanings, sense-numbered where a word has multiple uses.
  • Pronunciation — IPA phonetic transcription plus audio playback in British and American voices.
  • Grammar & part of speech — noun, verb, adjective, adverb, preposition and more, with usage notes.
  • Examples & citations — real sentences with source references and revision history.
  • Names & cultural terms — gender, origin and meaning for personal names, place names and slang.
  • Word lists & CEFR levels — vocabulary grouped from A1 foundation to C2 mastery.
  • Developer API — a public, key-protected JSON API for building learning apps.

Editorial standards

Contributions and AI-generated drafts move through a review queue where editors verify definitions, senses, citations, examples and pronunciation before entries are published. See our editorial policy for the full workflow and our source licensing notes.

Contact & contribute

Suggest a word, report an issue or partner with us through the contact page or submit an entry from the contribute page. Developers can request an API key from the developer console after signing in.