Glossary
Plain-language definitions for terms used throughout this guide, alphabetical. If you're looking for how these are actually built, see the Contributor Guide's glossary instead — that one covers implementation vocabulary, this one covers what you see in the app.
Category — a folder-like grouping for templates, used to organize and filter the template list. See Managing templates.
Deploy — publishing your finished template so it's actually used, as opposed to Save (which just keeps your progress). See Testing, saving, and deploying.
Domain — the business area you're working in, chosen at the start of setup. Skipped automatically if your organization only has one.
Entry — one field in your template's output. Entries have a type (plain value, boolean, spreadsheet cell, node graph, code, or a group containing other entries) and appear as rows in the entries list.
Graph — the visual, node-by-node way of building an entry's value. See Building a mapping.
Input source — how a template's document arrives in production: as a file, an email attachment, or fetched over HTTP. See Configuring input sources.
Iterator — the mechanism for handling repeating data, like rows in a table. See Declaring variables with context.
Node — one step in a graph — a single block that does one thing (read a value, combine values, apply a condition, and so on), connected to other nodes to build up an entry's value.
Operator — your organization, as MorphMapper understands it. Determined automatically by the link you use to get into the app; see Getting started.
Plugin — a piece of automated help — suggesting values, detecting repeating structures, and similar — that you can turn on or off per template. See Working with plugins.
Raw editor — a separate, advanced screen for editing a template's entire underlying JSON directly, where Save deploys immediately rather than just saving progress. See Using the raw editor.
Schema — the underlying structure a template is built on top of, chosen when the template is created. Some schemas have their own settings to fill in; see Configuring a schema.
Template — the thing you're actually building: a complete mapping from a source file to structured output, made up of entries. See Choosing a domain and template.
Variable (context) — a value you declare once and reuse across multiple entries, instead of rebuilding the same logic each time. See Declaring variables with context.