- From: Ole Ersoy <notifications@github.com>
- Date: Thu, 18 May 2017 10:48:57 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 18 May 2017 17:49:31 UTC
Here's an article on how to publish Angular 4 components to NPM:
[Distributing an Angular Library - The Brief Guide](http://blog.mgechev.com/2017/01/21/distributing-an-angular-library-aot-ngc-types/)
I within the next 3 years we will have thousands, if not tens of thousands, of angular components like this one available to us:
``` js
@Component({
selector: 'my-zippy',
template: `
<section class="zippy">
<header #header class="zippy-header">{{ title }}</header>
<section class="zippy-content" id="zippy-content">
<ng-content></ng-content>
</section>
</section>
`
})
```
These are composites. They are javascript and a bunch of HTML elements put together. They talk to each other, drink tea, even Unicorn Frappucinos - God Help Us! All of this state and activity needs to be accessible. Screen readers need to know what's going on with `<my-zippy title="Read Me!">`
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/509#issuecomment-302488692
Received on Thursday, 18 May 2017 17:49:31 UTC