chromeos: Google Operating System for web applications
headless chromium: chromium without a graphic interface (hence headless), controlled through the command line. It can be used in server environments, for automated tasks or testing.
monochrome: (mono)chrome provides the android chrome browser and the android webview together. Hence, the android webview is not a component delivered separatly
trichrome: separate Chrome and WebView APK that depend on a common shared library APK (Android platform feature introduced with Android Oreo).
component
android webview: Android webview component, based on chromium code. It is used to display web pages as a part of an android client application.
aura: Chrome's next generation hardware accelerated UI framework. Aura provides basic window style hierarchy, etc.. See Aura shell (ash) for desktop and shell features.
blink: Blink is the rendering engine used by chrome & chromium. It renders marked up content (such as HTML, image files, etc.) and formatting information (such as CSS, etc.). It is originally a fork of Webkit.
breakpad: Breakpad is a set of components for crash-reporting
browser process: main process that runs the UI, manages tabs and plugin processes
chrome early loading framework: The chrome early loading framework starts early in the chrome process, typically setting up browser dll blacklist
content API: Public API exposed to embedders of the content module.
content module: Core code needed to render a page using a multi-process sandboxed browser. It includes all the web platform features (i.e. HTML5) and GPU acceleration. It does not include Chrome features, e.g. extensions/autofill/spelling etc.
courgette: differential compression algorithm for making Google Chrome updates significantly smaller
media: multimedia code for chromium (audio/video codecs, audio/video capture and rendering, ffmpeg, libvpx...)
mojo: Mojo is a framework for interprocess (IPC) communication, cross-language or platforms communications. It supports a common IDL format that can be bound to multiple languages. Beyond IPC, it is useful for code modularization.
ozone: Ozone is a platform abstraction layer beneath the Aura window system that is used for low level input and graphics.
renderer process: process per browser tab to render html pages (uses blink rendering engine)
sandbox: prevents hacking. Sandbox leverages the OS-provided security to allow code execution that cannot make persistent changes to the computer or access information that is confidential
V8 JavaScript engine: Google's open source high-performance JavaScript and WebAssembly engine, written in C++
views: framework for doing UI development, providing rendering, layout and event handling.
weblayer: high level embedding API to support building a browser. It's the reusable version of Chrome.
technology
Google Cloud Print (GCP): GCP enables any app (web, mobile, desktop) on any device to print to any cloud-connected printer.
servicification: Some Chromium features and subsystems are being refactored as services, with public API boundaries and runtime isolation via Mojo interfaces. The goals are to improve maintainability and extensibility of the system, with a more flexible runtime configuration.
project
onion soup: Code re-architecture project to 1) migrate web-platform features from //content/renderer/ to Blink and 2) massively simplify the abstraction layers.
deprecated
native client (NaCl): sandbox for running compiled C and C++ code in the browser efficiently and securely, independently of the user’s operating system (End of support on Chromium: use WebAssembly)
Pepper Plugin API (PPAPI): cross-platform API for Native Client-secured web browser plugins (deprecated, replaced by WebAssembly)