Open GeoffCoxMSFT opened 1 year ago
@GeoffCoxMSFT good points, we've also been thinking about how to make positioning concepts clearer with respect to individual components, since those docs aren't really known by users.
Added to our board for next sprint planning
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
considering for H2/2024 - docs revamp
In the v9 storybook documentation, customers reading the component documentation don't think to look under developer topics to read about positioning. We should cross-link these topics in storybook to help developers discover how to position floating components.
@ling1726 - LMK what you think about cross-linking the docs vs. documenting positioning more in each component topic.