angular-cn/aio/content/marketing/presskit.html

<h1 class="no-toc">Press Kit</h1>
<div class="presskit-container l-space-neg-top-8">
  <div class="presskit-row">
    <div class="presskit-inner">
      <div>
        <h2>ANGULAR LOGO</h2>
        <p>
          The logo graphics available for download on this page are provided under
          <a class="cc-by-anchor" 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>
      </div>
    </div>
  </div>

  <div class="presskit-row">
    <div class="presskit-inner">
      <div class="presskit-image-container">
        <img src="assets/images/logos/angular/angular.svg" alt="Angular">
      </div>
      <div>
        <h3 class="l-space-left-3">FULL COLOR LOGO</h3>
        <ul class="l-space-left-3">
          <li>
            <span>Angular Logo (png) - <a href="assets/images/logos/angular/angular.png" download>Download</a></span>
          </li>
          <li>
            <span>Angular Logo (svg) - <a href="assets/images/logos/angular/angular.svg" download>Download</a></span>
          </li>
        </ul>
      </div>
    </div>
  </div>

  <div class="presskit-row">
    <div class="presskit-inner">
      <div class="presskit-image-container">
        <div>
          <img src="assets/images/logos/angular/angular_solidBlack.svg">
        </div>
      </div>
      <div>
        <h3 class="l-space-left-3">ONE COLOR LOGO</h3>
        <ul class="l-space-left-3">
          <li>
            <span>Angular Logo Black (png) - <a href="assets/images/logos/angular/angular_solidBlack.png" download>Download</a></span>
          </li>
          <li>
            <span>Angular Logo Black (svg) - <a href="assets/images/logos/angular/angular_solidBlack.svg" download>Download</a></span>
          </li>
        </ul>
      </div>
    </div>
  </div>

  <div class="presskit-row">
    <div class="presskit-inner">
      <div class="presskit-image-container">
        <div>
          <img src="assets/images/logos/angular/angular_whiteTransparent.svg" class="transparent-img-bg">
        </div>
      </div>
      <div>
        <h3 class="l-space-left-3">ONE COLOR INVERSE LOGO</h3>
        <ul class="l-space-left-3">
          <li>
            <span>Angular Logo White Semi-Transparent (png) - <a href="assets/images/logos/angular/angular_whiteTransparent.png" download>Download</a></span>
          </li>
          <li>
            <span>Angular Logo Semi-Transparent (svg) - <a href="assets/images/logos/angular/angular_whiteTransparent.svg" download>Download</a></span>
          </li>
        </ul>
      </div>
    </div>
  </div>

  <div class="presskit-row">
    <div class="presskit-inner">
      <div>
        <h2>PRESS AND MEDIA</h2>
        <p>For inquiries regarding press and media please contact us at
        <a href="mailto:press@angular.io">press@angular.io</a>.</p>
      </div>
    </div>
  </div>

  <style>
    div.bullets ul {
      list-style-type: disc !important; margin-left: 1em !important;
    }
  </style>

  <div class="presskit-row">
    <div class="presskit-inner">
      <div class="bullets">
        <h2>BRAND NAMES</h2>
          <h3>Angular</h3>
          <p>The name <b>Angular</b> represents the work and promises provided to you by the Angular team.</p>

          <p>When not specified, Angular is assumed to be referring to the latest and greatest stable version from the Angular Team.</p>

          <h4>Example</h4>
          <p><b>Version v4.1 now available</b> - We are pleased to announce that the latest release of Angular is now available. Staying up to date is easy!</p>

          <h4>Example</h4>

          <p><b>Correct: </b> "New <code>*ngIf</code> capabilities</b>&mdash;new in version 4.0 is the ability to ..."</p>
          <p><b style="color: red">Incorrect: </b> "New <code>*ngIf</code> capabilities in Angular 4</b>&mdash;Angular 4 introduces the ability to ..."</p>

          <p><b>Reasoning</b></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>

          <h3>AngularJS</h3>

          <p><b>AngularJS</b> is the v1.x series of work and promises provided by the Angular team.</p>

          <h4>Examples</h4>
          <ol>
            <li>AngularJS is one of the most used framework on the web today (by number of projects).</li>
            <li>Millions of developers are currently building with AngularJS.</li>
            <li>Developers are beginning to upgrade from AngularJS to Angular.</li>
            <li>I’m upgrading my application from AngularJS to Angular.</li>
            <li>I'm using AngularJS Material on this project.</li>
          </ol>

          <p>AngularJS projects should use the
          <a href="assets/images/logos/angularjs/AngularJS-Shield.svg" title="AngularJS logo">
          original AngularJS logo</a> / icon, and not the Angular icon.</p>

          <img src="assets/images/logos/angularjs/AngularJS-Shield.svg" alt="AngularJS Logo" style="margin-left:20px;" >

          <h3>Angular Material</h3>

          <p>This is the work being performed by the Angular team to provide Material Design components for Angular applications.</p>

          <h3>AngularJS Material</h3>

          <p>This is the work being performed by the Angular team on Material Design components that are compatible with AngularJS.</p>

          <h3>3rd Party Projects</h3>

          <p><b>X for Angular</b></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>

          <b>Do not use</b>
          <ul>
            <li><code>ng2-</code></li>
            <li><code>angular2-</code></li>
          </ul>

          <b>OK to use</b>
          <ul>
            <li><code>ng-</code></li>
            <li><code>angular-</code></li>
          </ul>

          <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>

          <h4>Examples</h4>
          <ul>
            <li>The ng-BE team just launched <code>ng-health</code> to help developers track their own health.</li>
            <li>I’m going to use NativeScript for Angular to take advantage of native UI widgets.</li>
            <li><code>ReallyCoolTool</code> for Angular.</li>
            <li><code>ReallyCoolTool</code> for AngularJS.</li>
          </ul>
      </div>
    </div>
  </div>

  <div class="presskit-row">
    <div class="presskit-inner">
      <div class="bullets">
        <h2>TERMS WE USE</h2>
        <p>
        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.
        </p>
        <ul>
          <li>Ahead of Time compilation (AOT)</li>
          <li>Just in Time compilation (JIT)</li>
        </ul>
      </div>
    </div>
  </div>
</div>