Glossary

Documentation Index

Fetch the complete documentation index at: https://zite.com/llms.txt

Use this file to discover all available pages before exploring further.

​

Zite essentials

• Zite: An AI-powered app builder for businesses creating custom software, internal tools, dashboards, portals, and websites without starting from code.
• App: The web application you create in Zite. An app can be internal only or live on the web, and can include pages, data, workflows, integrations, authentication, and published access.
• Workspace: A shared collection of apps, databases, and forms for a team or organization. Workspace access can be managed for teammates or user groups with permissions such as Use or Edit.
• Prompt: The instruction you give Zite. Good prompts describe the goal, the user experience, the data involved, and any constraints.
• Preview: The live working view of your app inside the editor before or after publishing.
• Publish: The action that makes your latest app version available at its shareable link or custom domain.
• Share to web: The setting that controls whether your Zite is publicly accessible by link. See Share to web.
• Custom domain: A domain you connect to a published Zite instead of using the default Zite link.
• Version history: A timeline of changes to your app that lets you return to an earlier working state. See History.
• Duplicate: A separate copy of an existing Zite that you can modify without changing the original.

​

Agent and editing terms

• Agent: The AI builder inside Zite that reads your instructions, inspects your app, and helps plan, edit, or answer questions.
• Build mode: The mode where Zite makes changes to your app. Use it when you want the agent to create, update, or fix something. See Build mode.
• Plan mode: The mode where Zite scopes the work before making changes. Use it for larger or unclear requests. See Plan mode.
• Chat mode: The mode where Zite answers questions or gives suggestions without editing the app. See Chat mode.
• Selective edits: Fast visual edits to text, images, colors, spacing, and other interface elements. Some selective edits do not use credits. See Selective Edits.
• Manual editor: The controls used to adjust selected UI elements directly, such as text color, font size, spacing, borders, and shadows.
• Credits: Usage units consumed when Zite performs AI work or certain high-value actions. See Understanding credits.
• Model: The AI system used to reason about and generate changes. Different models may be better for different levels of complexity. See Model Selection.
• Fix it for me: A repair action that asks Zite to diagnose and resolve an app error. It is free to run and does not consume credits.

​

App structure

• Page: A screen or route in your app, such as a dashboard, form, detail page, or settings page.
• Route: The URL path for a page, such as /dashboard or /customers/123.
• Navigation: Links, menus, tabs, sidebars, or buttons that help users move between pages and sections.
• Component: A reusable part of the interface, such as a button, table, form, card, modal, or chart.
• State: Information that can change while someone uses the app, such as a selected record, a filter value, or whether a modal is open.
• Responsive design: Layout behavior that adapts to different screen sizes, including desktop, tablet, and mobile.
• Mobile settings: Options that control how your Zite behaves on mobile devices, including home screen installation. See Mobile settings.
• Embed: Placing a Zite inside another website or product using an embedded frame. See Embedding.
• QR code: A scannable code that opens your Zite link. See QR codes.

​

Data and databases

• Data source: The place your app reads from or writes to, such as Zite Database, Airtable, Google Sheets, or another connected service.
• Zite Database: Zite’s built-in no-code database for storing app data in tables and records. See Zite Database.
• Database: A structured place to store information that an app can query, display, update, or delete.
• Table: A collection of related records, such as Customers, Orders, Tasks, or Products.
• Record: One item inside a table, similar to a row in a spreadsheet.
• Field: A typed column on a table, such as text, number, date, file, select, or linked record. See Field types.
• AI Field: A database field with a prompt that lets AI fill in values automatically, such as categorizing, scoring, summarizing, or extracting information from other fields. See AI Fields.
• View: A saved way to filter, sort, group, or display records in a database table.
• Linked record: A relationship between records in different tables, such as linking an Order to a Customer.
• Lookup field: A field that shows information from a linked record.
• Formula: A computed value based on other fields or expressions. See Formulas.
• Import: Bringing existing data into Zite Database from a file or connected source. See Import data.
• Export: Downloading database records for use outside Zite.

​

Workflows and integrations

• Workflow: Backend logic that powers app actions, such as reading data, saving data, sending notifications, calling APIs, or running AI. Workflows are sometimes called endpoints or API routes. See Workflows.
• Workflow run: One execution of a workflow.
• Run history: Logs that show past workflow runs, inputs, outputs, and errors. See Workflow run history.
• Trigger: The event that starts a workflow, such as a button click, form submission, page load, or webhook.
• Action: A step a workflow performs, such as creating a record, sending a Slack message, or calling an external API.
• Input: Data passed into a workflow, such as a user ID, form values, selected filters, or a search term.
• Output: Data returned by a workflow to the app or another system.
• Integration: A connection between Zite and another service, such as Slack, Google Sheets, Airtable, OpenAI, Linear, or HubSpot. See Integrations.
• API: A structured way for software systems to communicate with each other. For example, a Zite workflow can call an API to look up shipping rates or update a CRM.
• Endpoint: A URL or workflow route that accepts requests and returns responses.
• Webhook: An event-based notification sent from one system to another when something happens. For example, Stripe can send a webhook when a payment succeeds.
• Streaming: Sending results back gradually as they are generated, commonly used for AI chat experiences.

​

Access and security

• Authentication: Requiring users to sign in before they can access part or all of an app. See Authentication.
• User: A person who can access your published app.
• Collaborator: A teammate who can help build or manage a Zite project.
• User group: A set of users that can share access rules or permissions. See User groups.
• SSO: Single sign-on, a way for users to sign in through an identity provider. See SSO.
• User sync: Keeping users and groups in Zite aligned with an external identity provider. See User sync.
• Permission: A rule that controls who can view, edit, submit, or manage something.
• Public app: A Zite app that anyone with the link can open.
• Private app: A Zite app that requires approved access, usually through login or workspace controls.
• Audit log: A record of security and account events for review. Audit logs are only available on Enterprise plans. See Audit logs.

​

UI and product terms

• Dashboard: An app or collection of views that helps users monitor and work with data, often including tables, charts, filters, metrics, tasks, and record details.
• Portal: A secure app where clients, vendors, partners, or team members can view information and complete tasks.
• Internal tool: An app used by a team to manage operations, approvals, support, inventory, sales, or other business processes.
• CRM: Customer relationship management software used to track leads, customers, conversations, and next steps.
• Form: A set of fields for collecting input from users.
• Modal: A focused overlay that appears above the current page for a specific task or confirmation.
• Drawer: A side panel that slides in to show details, navigation, filters, or settings.
• Toast: A short status message that appears temporarily after an action.
• CTA: Call to action. A button or link that asks the user to do something, such as submit, approve, publish, or continue.
• Empty state: The screen or message shown when there is no data yet, often with a suggested next action.
• Loading state: The UI shown while data or an action is still in progress.
• Error state: The UI shown when something fails and the user needs context or a recovery path.

​

Useful prompt terms

• MVP: Minimum viable product. The smallest useful version of an app that proves the workflow or idea.
• Acceptance criteria: Specific conditions that define when a requested change is complete.
• User story: A short description of a feature from the user’s point of view.
• Edge case: A less common situation the app should still handle correctly.
• Iteration: A round of changes that improves the app based on feedback or testing.
• Refactor: Improving the structure of code or logic without changing how the app behaves.
• Regression: A new bug where something that used to work stops working after a change.
• Validation: Checking that user input is complete, correctly formatted, and safe before using it.
• Accessibility: Designing an app so people can use it with keyboards, screen readers, sufficient contrast, and clear structure.
• Performance: How quickly and smoothly the app loads, responds, and completes actions.

Related topics