Publish roll-up announcement for the Cosmos DB Functions quickstart trio (#877, #878, #879)

[kristenwomack]

Goal

Once #877 (JavaScript), #878 (Java), and #879 (PowerShell) merge, publish a single announcement covering the new Cosmos DB Functions quickstarts together, instead of three separate template-add notices.

Why this matters

The three PRs cover one cohesive customer story: a Functions plus Cosmos DB language matrix authored by @paulyuk. A consolidated announcement gives developers a clearer picture of what shipped and why it matters, keeps the gallery-update feed cleaner, and sets a reusable pattern for similar releases ahead (the Service Bus matrix in #832 through #836, the Timer trigger set in #844, and the Flex plus Files mount in #847).

Scope

• Confirm Add functions-quickstart-javascript-azd-cosmosdb to awesome-azd gallery #877, Add functions-quickstart-java-azd-cosmosdb to awesome-azd gallery #878, and Add functions-quickstart-powershell-azd-cosmosdb to awesome-azd gallery #879 have merged
• Draft a short announcement and pick the right surface (blog post, social, or release note) that:
  • Names the three new quickstarts and their target audience
  • Links each template's source repo
  • Frames the language matrix as a single release
  • Credits @paulyuk
• Coordinate publishing channel and timing with the Functions DevRel team

Out of scope

• Per-template announcements
• Other Functions PRs still open (Add template: functions-quickstart-typescript-azd-service-bus (Issue #824) #832, Add Functions Timer trigger templates for Python, JavaScript, TypeScript, PowerShell, and Java #844, Add Azure Functions Flex Consumption with Azure Files OS Mount templates #847), which deserve their own roll-ups once they merge

Context

Committed to in PR comments on #877, #878, and #879.

[simonlpaige]

Given the issue is about coordinating a consolidated announcement for three merged PRs (Cosmos DB Functions quickstarts in JavaScript, Java, and PowerShell), the most valuable contribution is to propose a concrete, reusable announcement template and suggest the optimal publishing surface based on the repository's existing patterns.

---

The roll-up approach makes sense for this language matrix. To streamline the drafting and set a pattern for the upcoming Service Bus (#832-#836) and Timer trigger (#844) releases, I'd suggest structuring the announcement as a short GitHub Discussion post (under the announcements category if enabled) rather than a blog or social post. Discussions are indexed, searchable, and keep the conversation tied to the repo.

Template suggestion for the post body:

Title: New: Cosmos DB + Azure Functions quickstarts (JS, Java, PowerShell)

Body:
Three new azd templates are now available in the gallery, covering the Cosmos DB + Functions language matrix:

• JavaScript
• Java
• PowerShell

Each template provisions a Functions app with Cosmos DB bindings using Bicep infrastructure, following the same architecture so you can compare implementations side by side. Authored by @paulyuk.

To try one: azd init -t <template-name>

This also sets the pattern for the upcoming Service Bus (PRs #832-#836) and Timer trigger (#844) matrix releases, which will get similar roll-up posts once merged.

---

If you want to keep it even lighter, a single comment on the gallery's existing "What's New" pinned issue (if one exists) would work too. I can help adapt the wording for that surface if needed.