cncf / cncf/endusers

[strategist] Events page links only to 2025 archive — no upcoming-event tracking

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

Description

## Strategic Finding

**Type**: roadmap-gap (Phase 1 pillar: events)
**Horizon**: near-term

`docs/events/index.md` links only to the KubeCon + CloudNativeCon North America 2025 *archive*. With KubeCon NA 2026 approaching, the events pillar shows past events only. ROADMAP.md Phase 1 calls for "upcoming end-user events at KubeCon + CloudNativeCon" — currently hand-maintained and already outdated.

## Rationale

Events are the highest-intent page for the end-user audience (people deciding whether to attend/engage). An events page showing only last year's archive signals an unmaintained site to exactly the visitors the community most wants to convert. Unlike metrics, there is no authoritative machine-readable source, so the fix is a curation process, not just a pipeline.

## Proposed Next Step

Restructure the events page into "Upcoming" and "Past" sections, add the next scheduled KubeCon + CloudNativeCon end-user events (End User Summit, End User Reception) with authoritative events.linuxfoundation.org links, and add a quarterly freshness check to the content-review cycle. Acceptance: at least one upcoming event is listed whenever one is scheduled, and no past event appears under "Upcoming".

Tracks ROADMAP.md Phase 1 / issue #59.

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

Contributor guide

Open the contributing guide

Research direction

Start with docs/events/index.md and ROADMAP.md Phase 1, then review issue #59 for the existing events context. Restructure the page into Upcoming and Past sections, add authoritative links for scheduled KubeCon + CloudNativeCon end-user events, and document the quarterly freshness check; done means scheduled events appear under Upcoming and past events do not.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.