The logo graphics available for download on this page are provided under
<aclass="cc-by-anchor"target="_blank"href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.
This means that you can pretty much do what you like with it including printing it on shirts, creating your own variations, or getting it tattooed over your navel.
</p>
<p>We do ask that you not use the rest of the site graphics in other contexts to avoid confusion.</p>
<p><b>New <code>*ngIf</code> capabilities</b> - New in version 4.0 is the ability to use additional syntax to create local variables. This can be very helpful in cases such as working with observables …</p>
<p><b>New <code>*ngIf</code> capabilities in Angular v4</b> - Angular v4 introduces the ability to use additional syntax to create local variables. This can be very helpful in cases such as working with observables …</p>
<p>By not using “Angular 4” in the title, the content still feels applicable and useful after version 5, 6, 7 have been released, as the syntax is unlikely to change in the short and medium term.</p>
<p>3rd parties should use the terminology “X for Angular” or “ng-X” for software projects. Projects should avoid the use of Angular X (e.g. Angular UI Toolkit), as it could create authorship confusion. This rule does not apply to events or meetup groups.</p>
<p>Developers should avoid using Angular version numbers in project names, as this will artificially limit their projects by tying them to a point in time of Angular, or will require renaming over time.</p>
<p>Where a codename or shortname is used, such as on npm or github, some are acceptable, some are not acceptable.</p>
<p>As always, component and directive selectors should not begin with “ng-” selectors as this will conflict with components and directives provided by the Angular team.</p>
