The logo graphics available for download on this page are provided under CC BY 4.0. 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.
We do ask that you not use the rest of the site graphics in other contexts to avoid confusion.
For inquiries regarding press and media please contact us at press@angular.io.
The name Angular represents the work and promises provided to you by the Angular team.
When not specified, Angular is assumed to be referring to the latest and greatest stable version from the Angular Team.
Version v4.1 now available - We are pleased to announce that the latest release of Angular is now available. Staying up to date is easy!
Correct
New *ngIf capabilities - 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 …
Incorrect
New *ngIf capabilities in Angular v4 - 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 …
Reasoning
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.
AngularJS is the v1.x series of work and promises provided by the Angular team.
AngularJS projects should use the original AngularJS logo / icon, and not the Angular icon.
This is the work being performed by the Angular team to provide Material Design components for Angular applications.
This is the work being performed by the Angular team on Material Design components that are compatible with AngularJS.
X for Angular
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.
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.
Where a codename or shortname is used, such as on npm or github, some are acceptable, some are not acceptable.
Do not use
ng2-angular2-ng-angular-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.
ng-health to help developers track their own health.ReallyCoolTool for Angular.ReallyCoolTool for AngularJS.We often use terms that are not part of our brand, but we want to remain consistent on the styling and use of them to prevent confusion and to appear unified.