Skip to main content

Themes

Themes

Purpose and when to use this record

BriskControl storesa themesstorefront’s asvisual parttheme, ofbrand assets, colors, typography, and active presentation.

At a glance

  • Identify it by: Name.

  • Check its business context: Store.

  • Why care: Store, publication, consent, payment, and fulfillment states affect what customers see and what staff must act on; check the ecommercecorrect module.store Thisbefore generatedsaving.

    reference
  • Why care: Availability and publication flags affect future use without erasing history. Prefer disabling an obsolete setup record when existing transactions still refer to it.

Before you begin

You need the Brisk permission for the action you are taking on themes. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Have valid Store records ready first. Those selections determine where this Theme belongs and which later screens can find it.

Create a recordTheme

TheCreate evidencea packetTheme identifiesonly when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and sourcemake locationlater selection harder.

  1. Select the business context first: Store.

  2. Enter the required identifying and operational values: Store, and Name.

  3. Review Is Active, Preset, Theme Pack, Hero Layout, Product Card Style, and Script Type deliberately; these choices control availability or workflow rather than merely describing the record.

  4. Save the Theme, then confirm Name on its detail page before continuing.

After saving: Open the screen that uses this choice and confirm the Theme appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Delete a Theme

Delete this page.Theme only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

If the record is merely obsolete, use Is Active to remove it from future use while preserving existing references.

On the confirmation page, verify Name. After confirmation, return to the Themes list and make sure only the intended Theme was removed.

ViewReview recordTheme details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Theme currently means. Verify Is Active, Preset, Theme Pack, Hero Layout, Product Card Style, and sourceScript locationType before relying on it for thisa action.decision.

Confirm

Follow user-facingStore stepsto beforedetermine approvingwhether the issue is on this Theme or on one of those linked records.

Next check: Open the screen that uses this choice and confirm the Theme appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Edit an existing Theme

Edit this Theme when the underlying policy or classification changed. First determine whether historical transactions should retain the old value; if so, deactivate the old choice and create a new one.

  1. Open the detail page. Compare Store with the supporting document or approved request.

  2. Recheck Is Active, Preset, Theme Pack, Hero Layout, Product Card Style, and Script Type. These values are most likely to change storefront visibility, customer communication, payment, or fulfillment.

  3. Save the change, return to the list, and confirm that the Theme now appears under the expected Is Active, Preset, Theme Pack, Hero Layout, Product Card Style, and Script Type.

After the change: Open the screen that uses this choice and confirm the Theme appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Find and review recordsthemes

Brisk Themes list screen displayed with fictional documentation-demo data.
The Themes list screen in the Brisk documentation demo.

The evidence packet identifiesUse the viewThemes list to find the correct record before opening or changing it. Compare Name. Records with similar names or numbers can still belong to different Store.

  • Keyword search checks Name.

  • Narrow the list with Store filters.

  • The initial order emphasizes Name. Select a column heading when you need a different comparison.

Open the Theme whose Name match the task. If it is missing, clear the list filters and sourcerecheck locationStore, Is Active, Preset, Theme Pack, Hero Layout, and Product Card Style, plus the remaining screen fields rather than creating a replacement immediately.

Fields and business rules

Brisk stores 39 user-relevant fields for this action.Theme, Confirmincluding user-facing1 stepslinked-record beforeselection approvingand 5 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

andsourcelocation Confirmuser-facingstepsapproving record

Field RequiredWhat it controls
StoreYesThe evidencestore packetassociated identifieswith thethis viewtheme.
NameYesHuman-readable name for this action.theme.
Is beforeActive NoWhether this page.

theme

Deleteis aactive.

PresetNoThe evidencepreset packet identifies the view and source locationrecorded for this action.theme. ConfirmAvailable user-facingvalues: stepsAtelier, beforeMonochrome, approvingCoastal, Forest, Paper.
Theme PackNoSelect a full-layout Brisk storefront theme pack. Available values: Storefront Classic, Modern, Minimal.
Section ConfigNoSection-level content configuration used by Brisk theme packs.
Primary ColorNoThe primary color recorded for this page.theme.
Accent ColorNoThe accent color recorded for this theme.
Background ColorNoThe background color recorded for this theme.
Heading FontNoThe heading font recorded for this theme.
Body FontNoThe body font recorded for this theme.
Hero TitleNoThe hero title recorded for this theme.
Hero SubtitleNoThe hero subtitle recorded for this theme.
Custom CssNoThe custom CSS recorded for this theme.
Announcement TextNoThe announcement text recorded for this theme.
Hero LayoutNoThe hero layout recorded for this theme. Available values: Split, Centered, Minimal.
Product Card StyleNoThe product card style recorded for this theme. Available values: Soft, Outline, Minimal.
Favicon ImageNoOptional site favicon image for this storefront theme.
Site Background ImageNoOptional full-width storefront background graphic shown across pages while users scroll.
Shared Head HtmlNoThe shared head HTML recorded for this theme.
Shared Header HtmlNoThe shared header HTML recorded for this theme.
Shared Footer HtmlNoThe shared footer HTML recorded for this theme.
Script TypeNoChoose ES module scripts for modern import/export support or classic scripts for legacy snippets. Available values: ES Module, Classic Script.
Javascript AssetsNoOptional script URLs, one per line. Prefix with "module:" to force ES module loading.
Shared JavascriptNoThe shared javascript recorded for this theme.
Home Template HtmlNoThe home template HTML recorded for this theme.
Home Template JavascriptNoThe home template javascript recorded for this theme.
Product Template HtmlNoThe product template HTML recorded for this theme.
Product Template JavascriptNoThe product template javascript recorded for this theme.
Page Template HtmlNoThe page template HTML recorded for this theme.
Page Template JavascriptNoThe page template javascript recorded for this theme.
Collection Template HtmlNoThe collection template HTML recorded for this theme.
Collection Template JavascriptNoThe collection template javascript recorded for this theme.
Blog Index Template HtmlNoThe blog index template HTML recorded for this theme.
Blog Index Template JavascriptNoThe blog index template javascript recorded for this theme.
Blog Post Template HtmlNoThe blog post template HTML recorded for this theme.
Blog Post Template JavascriptNoThe blog post template javascript recorded for this theme.
Contact Template HtmlNoThe contact template HTML recorded for this theme.
Contact Template JavascriptNoThe contact template javascript recorded for this theme.

What happens next

Open the screen that uses this choice and confirm the Theme appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Common mistakes and troubleshooting

  • The record will not save: Recheck Store, and Name and any message beside the field. A required related record may also be inactive or unavailable to your role.

  • The record saved but is not available where expected: Recheck Is Active, Preset, Theme Pack, Hero Layout, Product Card Style, and Script Type, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

  • The values look right but the result is wrong: Open Store from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.