Craft CMS: content and commerce decisions

Explore Craft CMS for a bespoke retail site. Examine editorial structure, templates, plugins and commerce options, plus the work your team must maintain.

Craft CMS is a content management system for bespoke websites, where developers shape the editing fields and build the presentation around them. It suits retailers whose buying guides and product advice need more structure than a page editor provides. The project also needs a clear owner for hosting, updates and commerce.

What Craft CMS provides

Craft CMS gives editors structured content tools and gives developers control over how that content appears. Craft 5 is a PHP application backed by a relational database. Its platform documentation describes server-rendered templates and a GraphQL application programming interface (API) for separate frontends.

The CMS manages editorial records. Developers supply the page design, navigation and presentation logic. Commerce functionality comes through a separate implementation, such as Craft Commerce or a connection to the retailer’s existing commerce engine. Installing the CMS alone does not deliver a finished retail storefront.

Craft fits a team that wants editors to work with fields named for its own publishing tasks. A retailer can give a technical reviewer a reusable advice record and give a merchandiser a buying guide that references it. A simpler hosted store workflow can suit a team that mainly changes product listings and wants less responsibility for custom development.

Design content around the store’s questions

Design Craft’s fields around the advice a customer needs, then connect that advice to products through stable references. Craft’s custom fields determine both the editing input and how developers query and display its value.

Consider a fictional retailer selling home coffee equipment. Its guide helps customers choose a grinder for espresso. This illustrative model uses documented fields and templates.

Content recordProposed fieldsEditorial purposeSeparate owner
Espresso grinder guideCustomer question, introduction and advice referencesExplains the buying decisionFrontend template controls layout
Approved adviceGrinding requirement, explanation and review statusSupplies reusable technical wordingA named technical reviewer approves it
Product referenceExternal product identifier and display labelConnects advice to the relevant catalogue itemCommerce engine supplies current product facts
Supporting evidenceSource reference and internal review noteLets the reviewer trace the advicePublic presentation exposes only intended fields

For example, an advice record explains why a customer needs fine grind adjustment for espresso. The guide references that record beside relevant grinders. An editor revises the explanation in its field, previews the guide and submits it through the agreed approval process. The template continues to place the advice in the same part of the page.

If an answer system also uses the advice, export the approved passage with its record identifier and revision. A later correction must replace the old passage in that destination. The connection needs its own refresh process, because changing a CMS field does not prove that an external answer source has updated.

Keep prices and stock out of the advice record. A grinder can become unavailable while the grinding advice remains correct. Resolving the product identifier against the catalogue allows the presentation to hide the unavailable item without deleting the explanation.

Templates, plugins and commerce boundaries

Templates control presentation, plugins add functionality and commerce records retain their own owner. Craft’s template documentation explains how developers use Twig to produce the site’s HTML. The editor changes content within that implementation. A new layout or an extra interactive selector can require developer work.

Craft Commerce is a first-party ecommerce platform integrated with Craft CMS. Its catalogue uses products and variants, while its order model covers carts and completed orders. A project using Craft Commerce can keep those commerce records there. A project connected to another commerce engine must specify which system remains authoritative for each object.

For the fictional grinder guide, the existing commerce engine owns product identifiers and sellable variants, together with live prices and stock. It also owns baskets and orders. Craft owns the guide and approved advice. The custom connection reads product information into the page without allowing an advice edit to rewrite the product or an order.

Craft’s plugin system supports additional fields and integrations. Plugins are installed packages, with separate licensing and support responsibilities. A store must evaluate the actual plugin and supported version for the required job. A catalogue connector supplied by an extension is an extension dependency throughout the site’s life.

Keep an inventory of installed plugins, their maintainers and their compatibility with the chosen Craft version. Assign someone to test updates in a separate environment. The maintenance agreement must cover a replacement or custom repair if a required plugin stops receiving suitable updates.

Scope the development engagement

A useful Craft development brief specifies the editorial workflow and operating handover as well as the visible website. Ask the developer to price defined deliverables so the implementation can be accepted against them.

  • Map existing pages and advice into the new fields, including media and product references. List which URLs stay and which need redirects.
  • Supply representative templates, including long advice, missing images and unavailable products. Define what each page shows when the commerce connection fails.
  • Train editors to create drafts and preview changes. Include the approval responsibilities and a short guide using the retailer’s own content.
  • Document deployment, backups and recovery. Name who applies CMS and plugin updates, monitors failures and answers support requests.

Craft 5’s installation requirements include supported PHP and database versions, PHP extensions and Composer. Installing Craft therefore needs a suitable application environment. The installation guide covers local setup separately from hosting and deployment. A working local editor is only the start of the engagement.

Craft’s deployment guidance separates code and configuration changes from live content. Require the developer to demonstrate that a template release preserves current editorial and commerce records. The handover must include recovery instructions that account for any database migrations.

Craft CMS pricing separates the licence edition from hosting and implementation. The pricing page lists editions by user-account needs and describes included updates plus later update renewals. The licence is per project. Commercial plugins have their own licence and update terms, and a commerce implementation can add further costs.

Budget hosting around application resources, media storage and backups. Quote migration effort, custom templates and commerce integration separately from those recurring costs. Identify whose account holds the licences and hosting so the retailer can retain access when a development engagement ends.

Accept a content change safely

Accept the handover by changing one advice record and following its effect through every intended destination. Use a separate test environment with test catalogue and order records. These are expected acceptance results for the fictional guide.

  1. Record the grinder guide’s existing advice and the related test product’s price and stock. Keep an unrelated test order for comparison.
  2. Ask an editor to change the approved grinding explanation in a draft. Preview must show the revision in the intended guide position while the published test page keeps its existing wording.
  3. Complete the agreed approval and publishing process. The published guide must display the revised explanation without a template edit. If the advice feeds an answer system, its next refresh must replace the earlier passage with the approved revision.
  4. Confirm that the product’s price and stock still match the commerce engine, and that the unrelated order is unchanged. Remove the test product’s availability and confirm that the guide handles the missing purchase option while keeping the advice readable.

The editor must complete the content change through the supplied fields. The developer must explain the rendered result and show that the integration preserves each system’s ownership. Commission the broader site when that small handover works and the support agreement names who maintains it.

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.

See it in actionFree trial · Simple setup