microsoft / microsoft/fluentui

ONB-01 — Read & annotate the Fluent Motion System core docs

Open Beginner friendly
#36,142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area: Animation Fluent UI react-components (v9) Motion UXE backlog Type: Feature
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

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

Contributor guide

No contributing guide indexed for this repository

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.

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.

Assessment

Tech stack
react
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.