Glossary

Glossary

Core Tempify terms - alphabetical.

.pbc

Prebyte compiled file. Not rendered again through Prebyte; copied as a raw file.

.pbt

Prebyte template file. Contains placeholders like {{ project_name }} and is resolved at render time via Prebyte.

.tempify-lock.json

Generation lock. Stores template ID, version, managed files, hashes, and values used. Basis for diff and reapply.

Answers

JSON file with question answers (--answers). See Questions & Answers.

BuildPlan

Internal plan: which directories and files are written where, and in which order hooks run.

Config

Global or workspace configuration with defaults and render options. See Configuration.

Diff

Report-only comparison between the current target and a new template state. Writes nothing. See Reapply & Diff.

Hook

Lua script in one of four phases: pre, before_render, after_render, post. See Hooks (Users) / Hooks (Authors).

Include

A template can include other templates via includes and merge files/questions. See Includes & Layering.

layout.lua

Optional rules: rename files, exclude from output, override render behavior. See layout.lua.

Manifest

Loaded template meta-model from template.lua plus scanned files/, questions, hooks.

Prebyte

Separate template engine for .pbt. Tempify embeds Prebyte; direct access via -p / process. See Prebyte Passthrough.

questions.lua

Defines interactive or CLI-answerable questions in groups. See questions.lua Reference.

Reapply

Safe update of an existing target based on the lock file. See Reapply & Diff.

Shared Template Store

User-wide template storage under $XDG_DATA_HOME/tempify. See Shared Template Store.

template.lua

Required manifest of every template: ID, version, source_dir, output, optional includes. See template.lua Reference.

Template ID

Unique identifier (basic_cpp). Set as id in template.lua.

Trust Store

Stores user-approved template roots for hook execution with --accept-hooks ask.

Workspace

Current project directory with optional ./templates/ and .tempify/config.json.

See also

Home · FAQ