Digiter Builder Documentation

Digiter Builder 2.0.2

Visual WordPress page builder with dynamic content and controlled publishing

Product overview

Digiter Builder 2.0.2 is a visual page builder for WordPress with responsive layouts, reusable design systems and separate draft/publication controls.

Build responsive pages with reusable components, dynamic loops, display rules and portable design packages. An Annual license unlocks authoring and signed updates; existing published pages continue after expiry. Optional AI uses your own paid provider account.

Demo, purchase, delivery and activation

• The Shop product card provides the reviewed complete license-gated ZIP only after Customer Account login and email confirmation. No license is needed for the product's declared minimal Demo function.
• For a downloadable commercial plan, Digiter Shop waits for verified PayPal confirmation, issues the domain-bound signed license and sends the protected full-package download and license key to the checkout email.
• The Demo and commercial delivery use the same complete license-gated product version. Activating a valid key unlocks the full installed capacity without reinstallation; the paid email link remains available for a clean copy or recovery.
• Eligible Account purchases also expose current protected downloads while update access remains active. Download counts, expiry, domain and plan terms remain those recorded for the order.
• Private signed releases integrate with the standard WordPress Plugins and Dashboard Updates screens. Update eligibility follows the purchased update period and does not change the permanent-use term of a Lifetime license.

Current release highlights

• When a reviewed license-gated Demo is available, a confirmed Customer Account can download it from the Shop product card.

Core capabilities

• 110 module definitions with responsive Grid/Flex authoring
• Separate drafts, publication controls, saved versions and Undo
• Reusable components, global styles and site templates
• Dynamic Loop Builder with public-field queries and display rules
• Reviewed design packages with media and dependency checks
• Optional prompt-only AI drafts using your own OpenAI account
• Domain-bound Annual license and signed WordPress updates

Install and activate

• Use WordPress 6.6 or later and PHP 8.2 or later. OpenSSL is required for license and release verification. Use HTTPS, a current backup and a staging copy when upgrading an existing production site.
• In Plugins → Add New → Upload Plugin, select the complete digiter-builder-studio ZIP and activate it. To upgrade, keep the same plugin folder and accept WordPress’s replacement confirmation. Do not uninstall the old plugin as an upgrade step.
• Open Digiter Builder → License. Copy the exact domain shown there into the Shop order or manual license request, then paste the complete DNT1 key into the activation form. A key for a different product, domain or plan cannot activate Builder.
• The Annual plan covers one domain for 365 days and includes authoring and signed updates during the active term. The launch price is CHF 49.90 per year; the checkout always displays the current seller-configured price. The same signed key format is used for automatic Shop orders and authorized manual Shop issuance.
• Without an active license, administrators can inspect and preview designs, export them and use Help. New authoring changes and AI generation cannot be saved or applied to the site. Existing published layouts, navigation, forms and other public interactions continue to work; expiry never deletes content.

Create your first page

• Open the editor from the dashboard and choose a new page or an existing supported post. Set the page title, then start with a blank layout or a supplied template. Review imported sample text and links before publication.
• Add a section, choose its Grid or Flex layout, then insert headings, text, images and buttons. The structure panel shows parent and child relationships. Select the actual module you want to change before using its content, style or advanced controls.
• Choose media from the WordPress library, supply meaningful alternative text for informative images, and make button labels describe their destination. Prefer a single primary heading and a logical heading hierarchy.
• Save the working draft, inspect the preview at desktop, tablet and mobile widths, then Publish explicitly. Saving a draft and publishing are separate operations. Check the public URL while logged out after publication.

Drafts, history and shared editing

• The editor keeps the working document separate from the published document. A public visitor receives the published version until a permitted editor explicitly publishes a change.
• Undo and Redo operate on the current editing session. Saved versions are durable document checkpoints. Review the selected saved version before restoring it, then publish if the restored result should become public.
• A stale document revision must be reloaded or reconciled before saving. Do not resolve a conflict by repeatedly overwriting from two browser tabs. Export a design package if you need to preserve an alternative branch before reloading.
• Use editorial notes for coordination, and keep WordPress role permissions appropriate for the content type. A valid product license never grants a user WordPress administrator or publishing capabilities.

Layout and responsive design

• Grid sections control columns, ratios, gaps and placement. Flex sections control direction, wrapping, alignment and distribution. Use consistent spacing tokens and shared styles before adding local overrides.
• Desktop, tablet and mobile controls cascade according to the selected setting. Preview long titles, translated labels, narrow menus and image crops at actual device widths. Avoid fixed widths that exceed the containing column.
• Typography controls include font family, weight, size, line height, letter spacing and supported responsive values. Bundled fonts work locally; installing optional font or audio packs may require an administrator and an external download.
• Global styles and reusable components affect more than one page. Inspect component usage before changing shared content. Local overrides are suitable for a single exception; a shared style is suitable for a repeated design decision.

Modules and integrations

• The bundled module reference lists all 110 registered module definitions and their visible controls. Choose modules by purpose: layout, editorial content, media, data, navigation, marketing, forms and commerce. A catalogue entry does not imply that an external service is installed or configured.
• Media modules provide galleries, sliders, audio, video and interactive image presentations. Check captions, keyboard operation, reduced-motion preferences and image loading. External embeds follow the availability and privacy behavior of their provider.
• Forms use their configured delivery and storage settings. Test validation, spam controls, confirmation text and delivery to an address you control. Review retention and export/delete options before collecting real visitor data.
• WooCommerce modules require an active, configured WooCommerce installation. Payment buttons link to the configured destination; Builder does not process or guarantee a payment. External form and builder-template integrations require their corresponding active plugin.
• The demonstration in Demo Showcase is a browser-only simulation. Its sample cards, display rules and Undo do not edit WordPress content, send forms, call AI or make a purchase.

Loop Builder and dynamic content

• Add a Custom post loop and choose the content type, count, sorting and optional include/exclude lists. Exclusions take precedence over explicit inclusions; excluding every included item correctly returns no records.
• Create the card layout inside the first editable loop item. The same structure repeats for matching records, while dynamic bindings resolve in each record’s context. Bind fields such as title, featured image or supported public metadata rather than copying sample text into every card.
• Use public scalar REST fields or public Native Fields for numeric or text filters and ordering. Private, unknown or unsupported fields are rejected or produce no matches. Native Fields use a private query index; reindex after a schema or visibility change and allow scheduled batches to finish.
• Numeric comparisons use numeric semantics, so 10 and 10.0 compare equally. Text comparisons retain text semantics. Verify both matching and non-matching sample records and the empty-state layout.
• Pagination and load-more evaluate the saved published node and its ancestor visibility rules. Repeated form and quiz interactions inside loop cards are intentionally disabled; place an interactive form outside the repeated card instead.

Display rules, schedules and caching

• Build AND or OR groups with supported role, taxonomy and public-field conditions. Each group can contain up to eight rules and a document condition can contain up to eight groups. Use the rule explanation preview to check the current content and visitor context.
• Visibility combines the node’s own rules with ancestor rules, audience settings and schedule. A hidden parent hides its descendants. Unknown roles, private fields, malformed rules and invalid schedule values fail closed.
• Schedules use valid UTC timestamps. Configure them through the editor and verify the intended local time. An invalid or incomplete schedule must be corrected before assuming the content will be visible.
• Conditional pages are marked against normal public caching where possible. Configure host, CDN and other cache plugins to respect the page and session rules; a cache that ignores those signals can still serve stale or inappropriate output. Test logged-out and relevant logged-in roles separately.

Design packages and asset transfer

• Export a .digiter.json package to move a reviewed layout between Builder installations. The export includes eligible local image, audio and font files, compatible linked reusable/component/loop documents and flattened style snapshots.
• Inspect the import first. Review dependencies, external URLs, naming conflicts and media counts, then explicitly accept import. New attachments and linked document copies receive new local identifiers. Original destination documents are not overwritten.
• The limits are 30 media files, 4 MB per file, 16 MB total raw media, 24 MB package JSON, 12 linked documents and four dependency levels. Cycles, missing dependencies, checksum mismatches and unsupported external builder/mega-menu template dependencies are rejected.
• Only administrators with media-upload permission can import packages. If resource creation fails, the importer removes the resources it just created. Undo after a successful editor insertion reverses the layout insertion but intentionally does not delete newly imported library resources.
• External media stays linked to its original URL. Native field definitions, taxonomy identities, navigation menus and third-party font installations are not automatically migrated. Recreate or map those dependencies and test the destination before publishing.

AI assistant

• AI is optional and disabled until an administrator configures an OpenAI API key and enables it. The annual Builder price does not include OpenAI usage. The site owner pays any provider charges through their own provider account.
• The key can be supplied through the DBS_AI_API_KEY server constant or saved in encrypted WordPress options using the site’s authentication salt. Keep the same salts or re-enter the key after a salt rotation. The key is never returned to the editor or included in design exports.
• Enter a short prompt, choose a content language and explicitly agree to send that prompt. The request uses the Responses API with store=false and sends the prompt, not the current page document. Provider processing remains subject to the provider’s account terms.
• The assistant returns a restricted draft made from native hero, text, card, steps, FAQ and call-to-action sections. Review the preview, insert it, edit factual claims and links, and use Undo if the result is unsuitable. AI never publishes a page automatically.
• An administrator sets the per-editor daily request limit from 1 to 100; the default is 10. Invalid output, provider errors and unavailable service are reported rather than silently inserting broken content. Test a real provider request with your own key before relying on the feature in production.

Languages and SEO ownership

• The interface follows the WordPress user locale by default. A user can choose the site language or a supported explicit interface language without changing another user’s preference or the site’s language.
• English, Bosnian, Croatian, Serbian Latin and Serbian Cyrillic have complete indexed interface catalogues for this release. Other included catalogues have partial coverage and fall back to English. Do not assume that every included language is fully translated.
• Changing the interface language does not translate authored page text. Set the document content language to describe the actual page content and review authored text separately.
• Builder can provide a page description when another recognized SEO owner is absent. When Digiter SEO Compass or another recognized SEO plugin is active, manage the description there to avoid duplicate tags. Inspect the public page source after changing ownership.

Updates and recovery

• Open Digiter Builder → Updates and select Check for updates. A valid annual license requests the current signed release from Digiter Shop. Available updates appear in Plugins and Dashboard → Updates and can be installed with the standard WordPress update flow.
• Automatic updates use the same WordPress auto-update preference shown on the Plugins screen. The Builder Updates page changes that same preference. The signed Shop release must also permit automatic installation; feature and major releases require manual installation.
• Every remote release must have a valid RSA signature, an unexpired manifest, the expected product and an HTTPS package on Digiter’s approved endpoint. The downloaded ZIP must match the signed SHA-256 before WordPress extracts it. An invalid or unavailable release never replaces the installed plugin.
• To install a ZIP manually, use the Upload ZIP link on the Updates page, select a trusted complete Builder package and review WordPress’s replacement confirmation. Manual local ZIP replacement uses WordPress’s own authorization flow; it is not represented as a verified Shop download.
• An authorized signed previous release is offered only if its version is at least 2.0.0 and older than the installed version. Keep a full files-and-database backup: plugin rollback does not roll back content or schema changes. Do not downgrade new layouts to pre-1.11 code, which cannot preserve newer rules and loop structures.
• On multisite, authoring licenses are domain-bound to each site. Only users with network plugin-update permission can replace shared plugin files. Test your domain mapping and use an eligible license for the primary site’s update request.

Troubleshooting and support

• If activation fails, compare the shown domain, product slug, annual plan, expiry and server clock. Paste the complete key without adding quotes. Missing OpenSSL prevents verification. Never put the key into a public screenshot or support export.
• If an update is unavailable, distinguish an expired license from an unpublished release, blocked HTTPS request or invalid signature. Run Check for updates once after the cause is corrected. Do not disable signature or checksum checks to force installation.
• If a page looks wrong, compare the published public URL with the current draft, then check responsive overrides, shared styles, theme templates, required integrations and caches. Use a saved version when the problem is an authoring change.
• If a loop is empty, check publication status, include/exclude intersection, field visibility, numeric/text operator choice, query indexing and ancestor display rules. A private field is not a valid public filtering source.
• For support, include Builder version, WordPress/PHP versions, the affected module, the shortest reproduction steps and a sanitized design export where possible. Keep license keys, API keys, personal submissions and customer records out of public reports.

Protection, integrity and recovery model

• Account-gated Demo packages must be verified to keep only the declared minimal runtime available until a valid signed license is activated. Customer data, credentials, signing material and internal release records must never be included.
• A downloaded WordPress ZIP remains technically inspectable. Confirmed-Account access, encryption at rest, user-bound expiring links, integrity checks, request limiting and crawler controls protect storage and delivery but do not claim impossible post-download DRM.

Administration and visibility

• Use WordPress 6.6 or later and PHP 8.2 or later. OpenSSL is required for license and release verification. Use HTTPS, a current backup and a staging copy when upgrading an existing production site.
• In Plugins → Add New → Upload Plugin, select the complete digiter-builder-studio ZIP and activate it. To upgrade, keep the same plugin folder and accept WordPress’s replacement confirmation. Do not uninstall the old plugin as an upgrade step.
• Open Digiter Builder → License. Copy the exact domain shown there into the Shop order or manual license request, then paste the complete DNT1 key into the activation form. A key for a different product, domain or plan cannot activate Builder.
• The Annual plan covers one domain for 365 days and includes authoring and signed updates during the active term. The launch price is CHF 49.90 per year; the checkout always displays the current seller-configured price. The same signed key format is used for automatic Shop orders and authorized manual Shop issuance.
• Without an active license, administrators can inspect and preview designs, export them and use Help. New authoring changes and AI generation cannot be saved or applied to the site. Existing published layouts, navigation, forms and other public interactions continue to work; expiry never deletes content.
• Digiter Shop → Demo Downloads manages the reviewed Account-gated package. The current commercial release is validated and linked without a duplicate upload. Manual fallback accepts only the exact same current ZIP, version and SHA-256. Publish only after testing both unlicensed minimal mode and licensed full activation.
• With an active update entitlement, signed Shop releases appear automatically in WordPress Plugins and Dashboard Updates. Manual Check now, Update now and authorized rollback remain available in the product administration.

Typical operating workflow

• Create a layout or choose a template
• Bind content and review display rules
• Preview desktop, tablet and mobile
• Save the draft, then publish deliberately

Operational considerations

• Open Digiter Builder → Updates and select Check for updates. A valid annual license requests the current signed release from Digiter Shop. Available updates appear in Plugins and Dashboard → Updates and can be installed with the standard WordPress update flow.
• Automatic updates use the same WordPress auto-update preference shown on the Plugins screen. The Builder Updates page changes that same preference. The signed Shop release must also permit automatic installation; feature and major releases require manual installation.
• Every remote release must have a valid RSA signature, an unexpired manifest, the expected product and an HTTPS package on Digiter’s approved endpoint. The downloaded ZIP must match the signed SHA-256 before WordPress extracts it. An invalid or unavailable release never replaces the installed plugin.
• To install a ZIP manually, use the Upload ZIP link on the Updates page, select a trusted complete Builder package and review WordPress’s replacement confirmation. Manual local ZIP replacement uses WordPress’s own authorization flow; it is not represented as a verified Shop download.
• An authorized signed previous release is offered only if its version is at least 2.0.0 and older than the installed version. Keep a full files-and-database backup: plugin rollback does not roll back content or schema changes. Do not downgrade new layouts to pre-1.11 code, which cannot preserve newer rules and loop structures.
• On multisite, authoring licenses are domain-bound to each site. Only users with network plugin-update permission can replace shared plugin files. Test your domain mapping and use an eligible license for the primary site’s update request.
• This is a complex, actively maintained WordPress plugin. Despite pre-release testing, reproducible defects or compatibility issues can occur; confirmed product defects are corrected through maintained updates according to the customer’s active update entitlement.

Privacy, security and implementation boundary

Enter a short prompt, choose a content language and explicitly agree to send that prompt. The request uses the Responses API with store=false and sends the prompt, not the current page document. Provider processing remains subject to the provider’s account terms.

Support and troubleshooting

For product support contact [email protected].

Licensing, updates, support and ownership

A Digiter purchase grants the usage entitlement described by the selected product plan. It does not transfer copyright, source code ownership, trademarks, design rights, private signing material or proprietary implementation knowledge. Lifetime plans, where offered, refer to the stated software-use entitlement; update periods are shown separately in the Shop and purchase record.

Hosted Smart Cloud Monthly is an Account-bound service and is operationally different from a downloadable domain license. Standard plugin purchases may be completed as a guest where the Shop allows it, while Account-based purchases can remain associated with the verified Digiter Account.

Protected downloads and private updates are delivered through the Digiter Shop licensing system. Customers should retain their purchase email and license information and should not publish license keys publicly. For setup, licensing, delivery, update or product questions contact [email protected]. Digiter Team will investigate verified issues and work with the customer toward a practical resolution.