ONB-01 — Read & annotate the Fluent Motion System core docs
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- react
- Domain
- documentation
Research direction
Read the listed Motion pages first: Introduction, Migration, MotionSlotAPI, PresenceMotionSlotAPI, the react-motion README, and the preview Components Introduction and Atoms pages. Record findings in a shared document under unclear, missing, surprising, or wrong, then debrief with Robert at the end of W1; completion is a categorized annotation set that can inform DOC-01 and DOC-10.
Written by the indexing model from the issue text.
Description
Description: Read through the existing Fluent Motion System documentation — including the new pages Robert recently published (Motion/Introduction, Motion/Migration, Motion/MotionSlotAPI, Motion/PresenceMotionSlotAPI, the updated react-motion README, plus Motion/Components (preview)/Introduction and Motion/Components (preview)/Atoms). Annotate as you go: anything unclear, missing, or surprising for a senior UXE coming in fresh.
Why it matters: Establishes baseline mental model and produces the first batch of docs improvement signal. Annotations become DOC-01 and DOC-10 inputs.
- Difficulty: Easy
- Dependencies: None — this is the entry point
- Sequencing: M1 W1
- Pairing: Async; debrief with Robert at end of W1
- Output: A shared doc with annotations grouped by unclear / missing / surprising / wrong
- Dominant language
- TypeScript
- Stars
- 20.3k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 43
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/fluentui
-
Component: CalendarDayGrid Component: WeeklyDayPicker Fluent UI react (v8) Type: Bug :bug:
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Fluent UI WC (v3) Type: Bug :bug: web-components
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
All issues in microsoft/fluentui
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·