Public product roadmap on the Community Hub

Open
#99 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@boazpoolman is already working on this.

Since Nov 4, 2026.

  • #105 by @boazpoolman — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, typescript

Research direction

Start with the implementation on the feature/public-roadmap branch and read apps/cms/src/plugins/roadmap-sync/README.md for setup and publishing rules. Review the CMS and /roadmap work described in the issue, then check the listed launch requirements and open questions. Done means the roadmap is ready to launch with those setup tasks and decisions addressed.

Written by the indexing model from the issue text.

Description

Summary

Add a public product roadmap at /roadmap on the Community Hub. It shows the items the product team marks as public in the Notion Product Roadmap, with Canny votes and GitHub progress next to each one, lined up against Strapi releases.

A first implementation is on feature/public-roadmap.

Why

Partners and community members regularly ask what's coming next, and today the answer lives on an internal board. A public page gives them one place to see what's planned, what's being built and what has shipped, with links to vote and follow the work.

What's on the branch

CMS

  • roadmap-item content type. Public and read-only; the API only ever serves published items.
  • release content type, filled from GitHub releases and open milestones.
  • roadmap-sync plugin. Runs nightly, or on demand through a secret-protected endpoint. It pulls the rows ticked for the public roadmap, adds Canny votes and status plus GitHub issue state, and publishes an item only when it has a public title, a public description, a public status and no dead links. Everything else stays a draft. Nothing is ever deleted.
  • A weekly "needs attention" digest to Slack through n8n: missing copy, broken links, items not reviewed in 60 days.

Web

  • /roadmap with a stats banner, a Planned / In progress board, a release timeline, release and area filters, search and sort.
  • Cards link out to the feedback thread and the GitHub issue. Clicking a card opens its details in a modal at /roadmap?item=<slug>, so items can be shared.

Setup, publishing rules and the Notion fields are documented in apps/cms/src/plugins/roadmap-sync/README.md.

Needed before launch

  • Add the four new properties to the Notion Product Roadmap (Public title, GitHub links, Docs link, Public review date)
  • Write public titles and descriptions for a first batch of items and tick them for the public roadmap
  • Add the Notion, Canny and GitHub credentials to the CMS environment (see .env.example)
  • Confirm the Slack channel for the digest (the workflow posts to #product-roadmap for now)
  • Add "Roadmap" to the community navigation in the CMS
  • Agree who owns the weekly digest review

Open questions

  • Area names. Cards show squad names (CMS core, DX…). Do we want public-facing area names instead?
  • Linear. Pulling GitHub links from Linear is out of scope for this first version.
  • Canny. The "post not found" handling hasn't been checked against the real Canny API yet.
Dominant language
TypeScript
Stars
1
Forks
3
Avg merge
38m
Merged PRs (30d)
18

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from strapi/community

All issues in strapi/community

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.