FAQ / Did You Know — Domain-Control Data-Gap Analysis
Scoping of the "Did You Know?" screen (DYK / FAQ list). Documentation only.
Did You Know? (5172:15051)
⛔ ABANDONED (2026-06-29) — Change 4 (DYK / FAQ) dropped. The "Did You Know?" / FAQ feature was
abandoned per the Backend API Mapping Report (Change 4).
No new endpoint will be built and this screen is not proceeding. The analysis below is retained for historical
context only and does not reflect committed work — disregard the "needs a new endpoint" framing.
Headline (historical) — NEW feature; needs a new API endpoint. The control is already speced — a list of
listy card generic (Did You Know List): date · headline (· subtitle) · favorite · → detail.
"Did You Know?" is a new screen, not part of the existing app — no feature, UI, or endpoint exists for
it today. It needs a new backend API endpoint as its data source. The Q/A + date/headline shape is
already modeled (unwired) by KCMFAQItem { Question, Answer } and KCMAlertItem { headline,
story, publishDate } in KCM.cs — a reasonable contract starting point. Favorites is the one cross-control
gap (per MEC).
1 · Screen & control
- Title "Did You Know?" + a list of 6×
listy card generic(date + headline; first row "All DYKs & FAQs" = view-all/filter). - Each row carries a favorite heart (recurring affordance — see MEC favorites gap).
2 · Data-source mapping
| Element | Data | Source | Status |
|---|---|---|---|
| Did You Know list | date · headline · subtitle · nav target | New API endpoint required (new feature, no existing source). Shape modeled by the unwired KCMFAQItem { Question, Answer } / KCMAlertItem { headline, story, publishDate } in KCM.cs. | new endpoint |
| Favorite | is-favorite + toggle | — (cross-control favorites gap, per MEC) | gap |
3 · Confirm / gaps
| # | Item | Note |
|---|---|---|
| 1 | DYK/FAQ data source — new endpoint | "Did You Know?" is a new feature, not in the existing app; it needs a new API endpoint. No existing source — not notifications, not hard-coded. The KCMFAQItem (Q/A) / KCMAlertItem (date/headline/story) models in KCM.cs exist but are unwired — useful as a contract shape. (Corrects an earlier "source confirmed: GetNotificationListAsync" note.) |
| 2 | Favorite | Same cross-control favorites gap flagged in MEC — no favorites API today. |
| 3 | "All DYKs & FAQs" row | Confirm it's a view-all/category entry vs a content item. |
4 · Summary
- Control: Did You Know List (
listy) — already speced. - Source — new endpoint required: "Did You Know?" is a new feature with no existing data source; the backend needs a new endpoint. Shape modeled (unwired) by
KCMFAQItem/KCMAlertIteminKCM.cs. - Gap: favorites (cross-control, no API).