As I said in my last post, when the Office UI Fabric came out I immediately put in a feature request on the site for Angular directives the same way we have other design languages like Bootstrap & Google’s Material Design . There are projects that have created Angular directives for these design languages: UI Bootstrap & Angular Material . As you can see from the resolution of that issue, as well as from a dialog in a public Yammer network with the project owner at Microsoft, I took it upon myself to spin up a community project…
In my last post post, [Introducing OfficeUIFabric.com - Demos and Reference Samples for the Office UI Fabric](https://www.andrewconnell.com/blog/introducing-officeuifabric-com-demos-and-reference-samples-for-office-ui-fabric/ I talked about the new OfficeUIFabric.com site I started to have a good publicly accessible and easy to reference the features and components within the Office UI Fabric.
I created it because before we create an Angular directive body of work, we first need something to base them on. How would we know what to measure success against? Sure, the Office UI Fabric has some docs, but we don’t have complete samples or a site where we can easily see how things work like you do with something like Bootstrap . Agreed?
While that project is ongoing, I wanted to let you know about something else:
I’ve created a new org on GitHub, ngOfficeUIFabric that will contain the body of work for the Angular Office UI Fabric directives. The source for this project can be found in the repo ng-officeuifabric . I’ve added a bit of content to it but there’s a long way to go.
The goal is for this to become a high-quality library complete with documentation, samples, unit tests… all that stuff. Think Angular Material … I’ve got a site set aside for this, ngOfficeUIFabric.com .
Angular is well past the time of yet-another-web-framework. Angular is a core web technology these days that will be around for quite a while. Many companies are standardizing their internal web application development on this technology. In my eyes, the ng-OfficeUIFabric should be a reliable and high quality library… not something where we throw a few samples in that meet just your needs. We need reusable stuff.
Before I get start on it or we start adding community contributions, let’s get a few components demo’d out on the OfficeUIFabric.com site first. Then we’ll create one or two Angular directives for them and the theming support, complete with unit tests and samples so contributors can see.
I’m really looking forward to getting the community involved and hopefully some support from Microsoft as well!