Help & Reference
BlockNinja glossary
Find the approved meaning of BlockNinja product, content, data, workflow, access, AI, plugin, and recovery terms.
How to use this glossary
Use these terms in guides, support conversations, interface copy, and training. Prefer the current customer-facing name. When two terms seem similar, follow the distinction in the definition and verify the current interface before publishing instructions.
Product and site terms
| Term | Meaning |
|---|---|
| BlockNinja | The product family for building, managing, operating, and extending websites. |
| CMS | The BlockNinja content-management application where administrators build and operate a site. |
| Site | One website and its content, settings, users, domains, data, and installed capabilities. |
| BlockNinja account portal | The managed account dashboard for sites, domains, team access, plans, and account operations. Use this customer-facing name; do not substitute an internal service name. |
Page-building terms
| Term | Meaning |
|---|---|
| Page | A public or draft route assembled from content, settings, and blocks. |
| Block | A configurable unit of page structure or content, such as text, media, navigation, or a data-backed component. |
| Master Page | A reusable page structure that supplies shared regions or layout to other pages. |
| System Page | A page used by a built-in public journey, such as a special listing or error experience. |
| Template | A reusable presentation definition for rendering a page or content context. |
| Block Template | A reusable starting configuration for a block. |
| Menu | An ordered set of navigation items that links people to pages or other approved destinations. |
Publishing terms
| Term | Meaning |
|---|---|
| Draft | Saved work that is not the current public version. |
| Preview | A temporary view used to inspect unpublished work before making it public. |
| Published | The version currently available through its public route. |
| Archived | Content retained for reference but removed from its normal active publishing flow. |
Private work stays Draft until its role, safety, accessibility, desktop, narrow, and public-journey checks pass.
Posts and editing terms
| Term | Meaning |
|---|---|
| Post | A dated or editorial content item that can appear in a blog or category journey. |
| BlockNote editor | The shared rich-content editor used for structured headings, paragraphs, lists, media, links, and other content blocks. |
| Category | A named grouping used to organise and browse related posts or guides. |
| Author | The approved public byline identity assigned to content. |
Data terms
| Term | Meaning |
|---|---|
| Table | Tables hold data in defined fields and rows. |
| View | Views shape data for pages by selecting, filtering, sorting, or presenting records from Tables. |
| Data Bucket | A legacy term for an earlier data mechanism. Use Tables and Views for current guidance unless maintaining an explicitly legacy site. |
Do not call a View the data store. The Table holds the data; the View shapes it for a use.
Workflow terms
| Term | Meaning |
|---|---|
| Workflow | A defined sequence of steps that processes an event or task. |
| Resume | Continue a paused or interrupted workflow run from its recoverable point. |
| Run again | Start another workflow run when retrying the whole task is the intended recovery. |
Use the label shown by the current failed or paused run. Resume and Run again are not interchangeable promises.
Access and identity terms
| Term | Meaning |
|---|---|
| Viewer | A role intended for visibility with the narrowest administrative access. |
| Admin | A role for routine site administration and editorial operations. |
| Superadmin | A privileged CMS role for trusted site administration. |
| Account Owner | The person with ultimate responsibility for a managed BlockNinja account. |
| SSO admin | An administrator who enters a managed site through the approved single sign-on route. |
| Emergency local admin | A separately controlled local CMS identity reserved for recovery when managed sign-in is unavailable. |
| Public user | A person using a site's public account or audience-facing features, distinct from a CMS administrator. |
Role names can exist at different layers. State whether you mean the local CMS, BlockNinja account, or per-site managed access.
Backup and visibility terms
| Term | Meaning |
|---|---|
| Backup | A recoverable copy of site state created for protection or an approved operation. |
| Restore | A controlled operation that replaces current state from a selected backup. Preview and verify scope before execution. |
| Hidden site | A site configured to discourage normal search-engine discovery. Hidden is not the same as private access control. |
AI terms
| Term | Meaning |
|---|---|
| Satoru | The BlockNinja assistant surface for guided product help and supported tasks. |
| Satoru AI | The BlockNinja AI capability used where the product explicitly presents AI-assisted work. |
| Agent design notes | Public guidance about audience, tone, and design intent that may be exposed to AI assistants. It must never contain secrets or private data. |
Describe the task and human review. Do not claim AI output is automatically correct or approved.
Plugin terms
| Term | Meaning |
|---|---|
| Plugin | An installable capability that extends a site. Current standalone plugins run as sandboxed Wasm modules distributed in codeless .bnp packages. |
| Plugin provisioning | The approved process that prepares plugin services, settings, or site resources. |
| Plugin egress | Controlled outbound network access granted to a plugin for approved destinations and purposes. |
Never describe current plugins as native shared-library code. Keep secrets out of plugin settings unless the documented encrypted integration path explicitly supports them.
Integration and protocol terms
| Term | Meaning |
|---|---|
| MCP | A supported protocol for connecting compatible clients to approved BlockNinja tools or context. |
| OAuth 2.1 | The current authorisation model for supported MCP clients. Use the product's authorisation flow instead of sharing credentials or static secrets. |
Terminology checks
- Say BlockNinja account portal, not an internal platform name.
- Say Tables hold data; Views shape it for pages.
- Use Resume and Run again exactly as the recovery action shown.
- Use sandboxed Wasm and codeless .bnp package for current standalone plugins.
- Use OAuth 2.1 for current MCP client authorisation.
- Never put raw identifiers, secrets, personal data, or internal hostnames in user-facing explanations.
Completion check
A reader can distinguish the site, account portal, CMS, role layers, page-building objects, content states, Tables and Views, workflow recovery actions, backup and restore, AI surfaces, plugin controls, and MCP authorisation without internal implementation prose.
Publication gate: keep this glossary private until product, support, security, and editorial reviewers have confirmed every definition against the current interface and governing decisions.
Related guides
Welcome to BlockNinja
Learn which BlockNinja surface owns your task: the public site, BlockNinjaCMS, the managed account portal, or an installed plugin before making changes.
Core BlockNinja concepts
Understand how sites, pages, blocks, themes, posts, Tables, Views, and plugins fit together so you can choose the right object before making changes.
Roles and access at a glance
Compare Viewer, Admin, and Superadmin access, choose the least privileged role for each task, and understand how managed SSO roles map into the CMS.