Merge pull request #2584 from Polymer/3-0-glossary

update glossary for 3.0

Author: Kate

app/3.0/docs/glossary.md

@@ -4,14 +4,11 @@ title: "Polymer Glossary"
 
 <!-- toc -->
 
-<div>
-{% include 'outdated.html' %}
-</div>
-
 ## A
 
-### Analyzer
-See [Polymer Analyzer](#polymer-analyzer).
+### AMD modules
+
+AMD modules are loaded by a web browser using a small library. This means AMD modules can be used with browsers that don't support native ES modules. You can configure your [Polymer CLI](#polymer-cli) build settings to convert ES modules to AMD modules.
 
 ### app shell
 In a progressive web app, the app shell contains the CSS, HTML and JavaScript that implements the 
@@ -24,49 +21,35 @@ See [Instant Loading Web Apps with an Application Shell
 Architecture](https://developers.google.com/web/updates/2015/11/app-shell) for more information.
 
 ## B
+
 ### Bower
-Bower is a package manager for web projects. Bower automates the installation of packages like 
-custom elements and JavaScript libraries. Polymer distributes its core library and elements via 
-Bower. See [bower.io](https://bower.io) for more information.
 
-### bower.json
-`bower.json` is a manifest used by Bower for configuring packages for use as dependencies. See [the 
-`bower.json` specification](https://github.com/bower/spec/blob/master/json.md) for more information.
+Bower is a package manager for web projects. Bower automates the installation of packages like custom elements and JavaScript libraries. Polymer 1.x and 2.x distribute their core library and elements via Bower. See [bower.io](https://bower.io) for more information.
+
+In Polymer 3.0, [npm](#npm) replaces Bower as a package manager.
 
-## C
-### crisper
-crisper extracts inline scripts from an HTML file. crisper is useful for separating JavaScript from 
-HTML in order to deploy in an environment that uses CSP (Content Security Policy).
+### bundling
+
+Bundling concatenates an app's scripts and resources to reduce the number of network requests it takes to load dependencies. 
+
+By contrast, if both server and browser support HTTP/2 (a newer protocol that permits concurrent resource requests), it can be acceptable to leave resources unbundled. Unbundled builds permit lazy loading of dynamic dependencies. By default, Polymer apps are unbundled.
 
 ## D
 ### dependency
 
 *dependency* may refer to:
 
-* A package dependency, such as a Bower or npm package that your project uses.
+* A package dependency, such as an npm package that your project uses.
 * A specific resource that is required by another, such as HTML files or JavaScript libraries. See 
 also: [dynamic dependency](#dynamic-dependency), [static dependency](#static-dependency), 
 [transitive dependency](#transitive-dependency).
 * A data dependency in the context of the Polymer data system: a piece of data that an observer, 
 computed property or computed binding depends on.
 
-### dependency variants
-
-Dependency variants are named sets of Bower [package dependencies](#dependency) at specific 
-versions which are different (usually more specific) than the default dependencies. Variants are 
-specified in [`bower.json`](#bower-json).
+### dynamic import()
+A [dynamic JavaScript `import()` statement](#https://developers.google.com/web/updates/2017/11/dynamic-import) loads a module. In contrast to static [import](#import) statements, dynamic imports load based on code execution, and can take a computed string.
 
-Dependency variants are useful for testing elements against different versions of Polymer and other 
-elements, where [`bower.json`](#bower-json) would normally only let you install and test against 
-one version.
-
-If you run `polymer install --variants`, the `polymer install` tool creates separate builds for 
-your element using the versions of Polymer you specify. You can use the [Polymer development 
-server](#polyserve) to test these variants. 
-
-### dynamic dependency
-A dynamic dependency is a dependency that is imported at runtime, using a mechanism such as 
-`importHref`. Compare [static dependency](#static-dependency).
+The Polymer 3.0 build tools will find your dynamic imports and include them in your build if you use string literals to identify them.
 
 ## E
 ### eager loading
@@ -78,24 +61,34 @@ The HTML actually loaded by the browser to start the application. Usually `index
 application built with an [app shell](#app-shell) architecture, the entrypoint is loaded for many 
 different URLs.
 
+### ES (ES5, ES6/ES2015)
+
+ECMAScript. A specification created to standardize JavaScript. 
+
+ES5 and ES6 (ES2015) are editions of ECMAScript; ES6 adds features to ES5, such as [imports](#import).
+
+The Web Components standards and the Polymer library are based on ES modules, a JavaScript feature added in ES6. Unlike AMD modules, which must be loaded with a library, ES modules are available natively in modern browsers. You can configure the [Polymer CLI](#polymer-cli) build tools to compile your code so that older browsers can still run your app.
+
+### ES modules
+
+ES modules use JavaScript `import` to load bindings that have been `export`ed by another ES module. Polymer uses ES modules to package the features of the Polymer library and load their dependencies.
+
 ## F
 ### fragment
-Fragments are used to define bundles and are often associated with routes or non-critical 
-resources. A fragment is a lazily-loaded HTML file. 
+Fragments are resources, such as custom element definitions, that are only loaded if the user follows a route that requires them. Fragments can be used by a bundler to identify resources that should be packaged together.
 
 ## G
 ### git
-A distributed version control system. Bower depends on git to install components from their GitHub 
-repositories.
+A distributed version control system. 
 
 ### gulp
 A streamed JavaScript task runner that can be used to set up a custom build process using the 
 [`polymer-build` library](#polymer-build).
 
-## H
-### hydrolysis
-This tool has been replaced by [Polymer Analyzer](#polymer-analyzer). It is a static analysis 
-framework for Web Components. 
+## I
+### import
+
+The [JavaScript `import` statement](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import) loads an ES module. Polymer 3.0 uses `import` statements to load the Polymer library, utilities and elements. `import` is an [ES6](#es6) feature.
 
 ## L
 ### lazy loading
@@ -107,10 +100,7 @@ app](https://github.com/Polymer/shop). In the Shop app, views are elements which
 only when they are routed to. 
 
 ### linter
-A linter is a piece of software that analyzes code for suspicious-looking constructions that can 
-potentially cause errors; for example, for example, registering an element without specifying its 
-tag name, or using invalid data-binding syntax. The Polymer tools include [`Polymer 
-Linter`](#polymer-linter), which does this for Polymer apps and elements.
+A linter analyzes source code and warns you about possible errors. Polymer CLI includes [`Polymer Linter`](#polymer-linter).
 
 ## M
 ### monolithic
@@ -119,75 +109,65 @@ architecture or dynamic code loading.
 
 ## N
 ### Node.js
-An event-driven JavaScript runtime environment. The [Polymer CLI](#polymer-cli) and [bower](#bower) 
-are both built on Node. For more information, visit [nodejs.org](https://nodejs.org).
+An environment for writing JavaScript applications and server-side code. Works with a package manager, npm. [Polymer CLI](#polymer-cli) and the Polymer Elements
+are built on Node. For more information, visit [nodejs.org](https://nodejs.org).
 
 ### npm
-Package management system for [Node.js](#node-js).
+npm is a package manager for [Node.js](#node-js). The Polymer library and core elements are distributed via npm.
 
 ## P
 ### package.json
 A metadata file used by [npm](#npm) to manage project dependencies.
 
 ### Polymer CLI
-A command line tool for Polymer projects. The Polymer CLI has a number of tools for working with 
+A command line tool for Polymer projects. Polymer CLI has a number of tools for working with 
 Polymer and Web Components. For more information, see the [Polymer CLI documentation](/{{{polymer_version_dir}}}/docs/tools/polymer-cli).
 
-#### `polymer build`
-This command builds your project with a preconfigured build pipeline. It calls `polymer-build` with 
-options configured for a build suitable for an [app shell](#app-shell) app.
+#### `polymer build` {#build-command}
 
-To customize your build pipeline, you can use `polymer-build` itself in conjunction with other 
-build tools.
+Polymer CLI command. Takes a build configuration from command line options, or from a [polymer.json file](#polymer-json), and packages your app for deployment on a web server. 
+
+`polymer build` is a convenient wrapper for the [`polymer-build`](#polymer-build) library. Use the `polymer-build` library itself if you need greater customization of your build process.
 
 #### `polymer init`
 Initializes a Polymer project. Contains a set of starter templates for elements and apps. 
 
 #### `polymer install`
-Install command for Polymer apps. Installs [Bower](#bower) dependencies, equivalent to running 
-`bower install`. With the option `--variants`, also installs any [dependency 
-variants](#dependency-variants) specified in the `variants` property of [`bower.json`](#bower-json).
+Calls `npm install`.
 
 #### `polymer lint`
-Invokes [`polymer-linter`](#polymer-linter) to [lint](#linter) a polymer project.
+Calls [`polymer-linter`](#polymer-linter) to analyze your code for potential problems. 
 
 #### `polymer serve`
 This command starts [`polyserve`](#polyserve), a simple development server for Web Components.
 
 #### `polymer test`
 Runs tests for your Polymer app with [`web-component-tester`](#web-component-tester).
 
-### polymer-build
-`polymer-build` is a library for building Polymer projects. `polymer-build` allows you to 
-completely customize your build and combine additional streams and build tasks in any order. 
+### Polymer Analyzer
+A static analysis tool for Web Components. Used by the tools in Polymer CLI to parse your code. For more information, see the [README](https://github.com/Polymer/tools/tree/master/packages/analyzer).
 
-Compare the `polymer build` command, which calls `polymer-build` with preconfigured options. 
+### polymer-build
+`polymer-build` is a library for building Polymer projects. `polymer-build` allows you to completely customize your build process and integrate it with other tools. For more information, see the the [README](https://github.com/Polymer/tools/tree/master/packages/build).
 
 ### Polymer Bundler
 Polymer build tool that follows HTML Imports and `<script>` tags to concatenate resources into a 
 single page for production. Can improve performance by reducing network trips.
 
 ### Polymer Linter
-[Linter](#linter) invoked by `polymer lint` command. Lints a Polymer project.
-
-### Polymer Analyzer
-A static analysis framework for web applications. 
+[Linter](#linter) invoked by `polymer lint` command. Warns you about potential problems in your Polymer code-for example, data binding with a property that doesn't exist, or using deprecated CSS selectors. For more information, see the [README](https://github.com/Polymer/tools/tree/master/packages/linter).
 
-### `polymer.json`
-`polymer.json` is the Polymer build configuration file. It lets you configure your app’s entrypoint 
-and app shell files, instead of passing these as parameters to polymer build.
+### `polymer.json` {#polymer-json}
+Configuration file. Sets options for how Polymer CLI tools should interact with your project, and defines the output of the `polymer build` command. Use polymer.json to create one or more build configurations, and to specify the locations of source files, data files, and extra dependencies. 
 
-`polymer.json` also lets you specify the locations of source files, HTML fragments and additional 
-dependencies, and configure the [Polymer linter](#polymer-linter).
-
-### `polyserve`
-`polyserve` is a locally-installable web server for developing [Bower](#bower) components. 
+### progressive web app 
+A progressive web app (PWA) is a reliable, fast web site that works seamlessly on mobile, tablet and desktop. A PWA has the look-and-feel of a native application and delivers content when offline, but is served over HTTPS via any modern web browser. 
 
 ## R
 ### routing
 Routing is the process an app uses to determine how to respond to a client request for a particular 
 endpoint. A default route is the endpoint the app directs the user to when no route is specified. 
-In a PWA, the [app shell](#app-shell) performs routing.
+In a progressive web app, the [app shell](#app-shell) performs routing.
 
 ## S
 ### service worker
@@ -218,13 +198,6 @@ dependency of file A.
 The *transitive dependencies* of a resource are all the dependencies, direct and indirect, that a 
 resource depends on.
 
-## V
-### variant
-See [dependency variant](#dependency-variant).
-
-### vulcanize
-This tool has been replaced by [Polymer Bundler](#polymer-bundler).
-
 ## W
 ### web-component-tester
 A browser-based testing environment for web components. Runs your tests in local browsers or