cncf / cncf/endusers

[strategist] No launch or promotion strategy: 0 stars, no announcement plan, domain undecided

Closed
#90 0 comments 0 reactions 0 assignees View on GitHub
roadmap
Dominant language
JavaScript
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

## Strategic Finding

**Type**: ecosystem-opportunity / adoption-gap
**Horizon**: mid-term

The site has 0 stars, 0 watchers, and 1 fork. Content pillars (architectures, metrics, awards, community, events, blog) are being built out under ROADMAP Phase 1, but there is no plan for the moment the site goes live: no DNS cutover decision (ADR 0001 still Proposed), no announcement channel (cncf.io blog, TAB meeting, KubeCon), no SEO/discoverability work, and no success metric for launch.

## Rationale

- Content completeness without a launch plan risks a "silent launch" — Phase 1 finishes and nobody notices.
- The blog pillar (#77) and events pillar (#75) are natural launch vehicles (announcement post, KubeCon EU/NA timing) but are currently framed as content chores, not launch assets.
- Adoption signals (stars, inbound links, TAB references) are the feedback loop that justifies continued investment; they are all at zero and unmeasured.

## Proposed Next Step

Add a "Phase 2 — Launch" section to ROADMAP.md (or a LAUNCH.md) defining: launch criteria (Phase 1 pillars green), announcement channels, DNS cutover dependency on #46, and a baseline metrics snapshot to measure against.

Related: #45 (ROADMAP), #46 (ownership), #75, #76, #77

---
*Filed by strategist agent (ACMM L6 — full mode)*

Contributor guide

Open the contributing guide

Research direction

Start by reviewing ROADMAP.md and the related issues #45, #46, #75, #76, and #77 to understand Phase 1, ownership, content pillars, and DNS dependencies. Define whether the work belongs in ROADMAP.md or a new LAUNCH.md, then document launch criteria, announcement channels, the DNS cutover dependency, and baseline adoption metrics.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, release
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.