microsoft / microsoft/documentdb-mcp

[Positioning] Establish brand & voice consistency guidelines

Open
#77 0 comments 0 reactions 1 assignee View on GitHub

@khelanmodi is already working on this.

Since May 13, 2026.

documentation positioning tier-3
Dominant language
TypeScript
Stars
2
Forks
4
Avg merge
6d 21h
Merged PRs (30d)
3

Description

Goal

Stop saying Cosmos DB for MongoDB vCore in docs. Pick one voice.

What to ship

A short BRAND.md (or section in CONTRIBUTING.md) covering:

  • Product name: always Azure DocumentDB. Never Cosmos DB for MongoDB, never MongoDB vCore, never Cosmos Mongo.
  • Logo usage: link to assets/documentdb-logo.jpg (or the official asset URL). Sizing and clear-space rules.
  • Voice: technical, candid, security-forward. Avoid marketing puffery.
  • Audience-facing terms glossary: profile (not connection), tier (not role), etc. Pick once and stay consistent.

Acceptance criteria

  • Lives in repo, linked from CONTRIBUTING.
  • All existing docs swept once for compliance.
  • PRs touching docs are reviewed against this.

Depends on

  • Naming clarity (already established with user — Azure DocumentDB).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.