Fabric React is a responsive, mobile-first, open-source collection of robust components designed to make it quick and simple for you to create web experiences using the Office Design Language
.
React components from Office UI Fabric React are used by many teams accross O365 and Microsoft for building their experiences. Some examples are SharePoint, OneDrive, Outlook, VisualStudio team services, ...
These components are also used by third party developers building extensiblity components using the SharePoint Framework.
Start with our README document.
To create your first app using Office UI Fabric React read the Sample App document.
https://developer.microsoft.com/fabric
Please open all issues at our GitHub issues location.
Things to remember while opening an issue
- Please fill out as many details as you can.
- We highly encourage you to submit PRs for issues.
----------------------------------------------------------------------------------------------
### Bug Report
- __Package version(s)__: (fill this out)
- __Browser and OS versions__: (fill this out if relevant)
#### Priorities and help requested (not applicable if asking question):
Are you willing to submit a PR to fix? (Yes, No)
Requested priority: (Blocking, High, Normal, Low)
Products/sites affected: (if applicable)
#### Describe the issue:
<!-- fill this out -->
#### Actual behavior:
<!-- fill this out -->
#### Expected behavior:
<!-- fill this out -->
### If applicable, please provide a codepen repro:
<!-- See http://codepen.io/dzearing/pens/public/?grid_type=list for a variety of examples -->
----------------------------------------------------------------------------------------------
Office UI Fabric React is an open-source distributed project. Lots of developers from inside and outside Microsoft contribute to this project. We highly encourage contributions. There is a core team that works hard to stay on top of the issues and pull requests.
Office UI Fabric React is an open-source distributed project. If you are building a new app inside O365 or Microsoft, this project will potentially save you lots of time, resources and headaches. We encourage all developers who use Fabric React to return a small amount to the community. If you notice bugs, we encourage you to not only open an issue on it but also help fix it. If you have a component that you believe others should use, feel motivated and encouraged to contribute that component back to the community. Sharing is caring. Many developers contribute outside their primary job responsibilities. Additionally, there is plenty to learn. We use a lot of cutting edge best practices used in the industry. Learning those can help you in your career.
We have a very active community both outside and inside Microsoft. Please use the Microsoft Teams channel for communication from within Microsoft. And a GitHub issue from outside Microsoft. We triage these issues at least once a week.
Start by reading our Contributing document. Please point out any missing or incorrect details.
Yes, you totally can. You will need to help out with reviewing pull requests and triaging and fixing issues. For now, only Microsoft employees can be a part of the core team. We are looking into changing that policy to allow non-Microsoft folks to be a part of the core team.
We are very proactive and work hard to keep the outstanding pull request count low. But if your pull request is non-trivial and stuck for a long time, please feel free to tag the pull request that it has been hanging for long and you need help.
Please refer to the following documents.
Contributing fixes and new components
The Fabric React core team works hard to stay on top of the open issues. We triage issues at least once a week. Due to an increased volume in the number of issues, we have been triaging more often. Once the issue count is under control, we may go back to the once a week rythm.
We try to fix high priority bugs ASAP.
- Is this issue blocking the consumer?
- Is this a regression? If yes, how and when did it get in?* Is this a very serious bug?
Other bugs will qualify as Normal or lower priority and will get fixed as a part of the normal release cadence.
From time to time we do plan to close issues that are very old and have no activity.