CMS Builder: content models and site publishing
Assess interactivetools.com’s CMS Builder for a retail content site. Check content models, editor access, template integration and maintenance.
- Published
- Last updated
CMS Builder is interactivetools.com’s self-hosted content management software for creating editing forms and displaying their records through website templates. It suits a retail content site when editors need structured buying guides or policies and a developer maintains the public pages. The buying decision includes that developer work, hosting and recovery alongside the software itself.
Identify the CMS Builder product
CMS Builder is the two-word product from interactivetools.com, distinct from Builder.io and the general category of website builders. Its CMS Builder overview lists release 3.84 and full source code. The documentation identifies itself as version 3.83, so match instructions to the version installed on the inherited site.
Start the handover by recording the installed version and active plugins, together with any changes to the program’s original files. Include the licence agreement supplied with that installation. A developer’s branding can replace the CMS name in the editing interface, so a retailer’s logo alone does not identify the underlying product.
The application manages content sections. The public website gets its layout from the templates containing the viewer code. That separation suits an existing custom website, but it also means a new field does not automatically gain a place on the public page.
Model the content and editor controls
CMS Builder administrators configure sections and their fields through the Database Editor. The quickstart distinguishes multi-record sections from single-page sections, then generates viewers for the chosen section. An editor fills in the forms that an administrator has configured.
Consider a fictional retailer managing buying guides and a delivery policy. Give buying guides a multi-record section, with a title and introduction plus body text, category and image fields. A delivery policy can use a single-record section when the website needs one current policy. Separate fields let the template place the introduction beside an image without extracting it from formatted body text.
Use one existing guide to assess the editing form. Confirm an editor can add another guide without rebuilding the page. Check that an uploaded image has the descriptive text and size the template expects. Treat the example field list as a proposed model, not a set of fields supplied automatically with CMS Builder.
Access control also changes the handover. The provider’s user-account documentation describes section permissions and separates administrator access from ordinary editing. An Author can change their own records, while an Editor can access any record in the section. Single-record sections use an access checkbox instead of those multi-record levels.
For the policy revision, give the responsible editor access to that section and test the account’s actual view. Decide who approves the wording before it reaches the public page. A permission level alone does not establish a separate approval workflow.
Changing an existing paragraph is editorial work. Adding a new field needs section configuration, while displaying it or changing page layout needs template work. Scope that ongoing CMS development before accepting the site’s maintenance quote.
Connect the content records to public pages
CMS Builder’s supported quickstart route generates PHP viewer code that a developer copies into the website’s PHP files. A multi-record guide section can have a listing and a detail page. A single-record policy uses a detail viewer. The developer adjusts the generated HTML to match the website.
Follow one record through that route. Save a guide, open its public URL and confirm the heading and image come from the intended fields. Then change one sentence and inspect the public page again. If the site adds caching or another publishing layer, include that layer in the update test.
Keep commerce prices and available stock in the commerce system that owns them. A guide can refer to a product identifier, with the website obtaining transaction data from its commerce connection. Copying a price into editorial prose creates another value someone must maintain. Orders also remain with the order system rather than becoming ordinary guide records.
A separate customer-answer knowledge source needs its own delivery path. For the fictional policy revision, identify whether it consumes the rendered page, an export or a maintained document. Publish the approved change, complete that transfer and ask a question whose answer depends on the revised sentence. Confirm the previous rule has been replaced. Installing a CMS does not establish this connection.
Operate and maintain the installation
CMS Builder requires a PHP and database host, with the retailer or its service provider responsible for operating it. The installation guide specifies PHP 8.1 or later and MySQL 5.7.32 or later, or a compatible database. It lists mysqli, gd, curl, openssl and mbstring extensions. The server also needs the file permissions required by the application.
The documented installation uploads the software to the web server and runs its browser installer. Allocate responsibility for server updates and access separately from content editing. An inherited installation needs a tested upgrade route as well as a working login.
The plugin documentation describes PHP extensions to the application, including minimum-version requirements. List the plugins the site actually uses and assign someone to maintain custom integrations. The upgrade guide calls for a backup before replacing program files and notes compatibility work for older custom code.
Recovery requires more than a copy of the content database. The backup guide distinguishes a website backup from an SQL backup of CMS tables. Its website backup covers the web root and data folder, with a database dump included by default. Review exclusions and restore a copy in an isolated environment before relying on it.
Compare proposals against the actual installation. Separate the software licence and any plugin terms from hosting charges, template development and paid support. The provider’s download page requires an account and also advertises installation and custom programming services. Access to a download does not include every service needed to run the site.
Require a usable exit package in the maintenance agreement. Name who supplies content records and uploaded media. Include the templates and explain how another developer can read the package. A database backup aids restoration, but a move to a different CMS also needs field mapping. Choose CMS Builder when its configured forms fit the editors’ work and the support agreement covers the templates and recovery the retail site depends on.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.