Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Missing lot of components from Fluent UI #73

Closed
zoran123456 opened this issue Aug 27, 2021 · 4 comments
Closed

feat: Missing lot of components from Fluent UI #73

zoran123456 opened this issue Aug 27, 2021 · 4 comments
Labels
area:fluent-ui-web-components A FluentUI specific issue closed:not-actionable There is no action to be taken in response to this issue. community:question A question from the community. community:request Issues specifically reported by a member of the community. feature A new feature

Comments

@zoran123456
Copy link

馃檵 Feature Request

Hi! So this "fast.design" is more of a generic frontend web framework, which also includes some components from Fluent UI?
I'm having problems understanding the difference between fast.design and fluent UI.

https://developer.microsoft.com/en-us/fluentui#/

I noticed in the examples, a lot of components are missing in fast.design, for instance, Avatar component, Rating, Command Bar, Ribbon Menu, etc. So I don't know what are we supposed to do with those components? I am using "BlazorFluentUI" and it does work quite well (although it has bugs), with all controls from Fluent UI supported, but I would really prefer to go with the official MS framework.

Can we expect to have additional (all!) components in the future, or shall we treat fast.design framework as something not entirely focused on the Fluent UI (more like a separate, generic "one size fits them all" framework)?

Thank you.

@EisenbergEffect
Copy link
Contributor

I think this question is best answered by @chrisdholt who leads our components and experiences team. I'll defer to him to provide an explanation about the site and future plans.

In general, I will say that we try to run the open source project as any other open source. So, if the community says "we really need component X", that is something we will listen to. Because we must juggle many competing priorities for our time, sometimes the reason we don't have a specific component is not because we don't want to, but because no one has specifically asked for it, and due to the lack of request, we've prioritized other work (where perhaps we have heard community response).

Definitely, always feel free to request specific components. It's easiest if we have an issue per component, and if you share a few of your use cases for the particular component. We take the component design, extensibility, accessibility, etc. of each component pretty seriously so any scenarios you can provide are very helpful. The best place to request the components is probably on our main FAST monorepo here: https://github.com/microsoft/fast Specifically mention that you want a Fluent version of the component so we know how to prioritize our design system work. Once the component lands in the main library, it's fairly easy for us to add a wrapper here for Blazor developers.

@EisenbergEffect EisenbergEffect added area:fluent-ui-web-components A FluentUI specific issue community:question A question from the community. community:request Issues specifically reported by a member of the community. feature A new feature labels Aug 27, 2021
@awentzel
Copy link
Contributor

awentzel commented Nov 5, 2021

@EisenbergEffect @chrisdholt has this been addressed? If so, may we close this issue?

@EisenbergEffect
Copy link
Contributor

Command Bar has been added as Toolbar. Avatar and Rating are in development. I think we should close this in lieu of having individual component requests opened on the main repo. That will help us to figure out what to build next.

@EisenbergEffect EisenbergEffect added the closed:not-actionable There is no action to be taken in response to this issue. label Nov 5, 2021
@EisenbergEffect
Copy link
Contributor

EisenbergEffect commented Nov 5, 2021

For future reference, please make requests for individual components here: https://github.com/microsoft/fast If you specifically want it as a FluentUI component, please add that detail to the request (since our team maintains more than one design system). Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:fluent-ui-web-components A FluentUI specific issue closed:not-actionable There is no action to be taken in response to this issue. community:question A question from the community. community:request Issues specifically reported by a member of the community. feature A new feature
Projects
None yet
Development

No branches or pull requests

3 participants