For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dev Portal
DocsAPI ReferenceLearnCommunityChangelog
DocsAPI ReferenceLearnCommunityChangelog
  • Overview
    • Quick Start
    • Sandboxes
    • Tools & SDKs
    • Support
  • Docs
    • Archive
            • ReCAPTCHA v2
            • Anatomy of a Theme
            • Blueprint and Developer Mode
            • Theme Update Process
            • Style Editor
            • Product Filtering Toolkit
            • Template Syntax
            • Store-Wide Global Panels
            • Store-Wide Global Variables
            • Global Variables
            • LNG Variables
            • Email Templates
            • Checkout Styling
    • Closed Beta Programs
Dev Portal
LogoLogo
On this page
  • Prerequisites
  • Update Process
  • Other Requirements
ArchiveStorefrontBlueprintThemes

Theme Update Process

Deprecated
Was this page helpful?
Previous

Blueprint and Developer Mode

Next

Style Editor

Built with

This is archived documentation for the legacy Blueprint theme framework. For current storefront documentation, see Stencil or Catalyst.

Here is how BigCommerce and our partners collaborate to integrate a partner’s theme changes/updates into the BigCommerce Theme Marketplace (which merchants also know as our “theme store”):

Prerequisites

Integrating a partner’s theme changes requires these preconditions:

  • Partner has an existing theme in the BigCommerce Theme Marketplace.

  • BigCommerce sets up a Theme Development store (or converts an existing regular store) and applies the theme. All theme files will automatically be copied into the WebDAV /template/ directory.

Template Path Abstracted The Theme Development store resolves the %%GLOBAL_TPL_PATH%% variable into /template/. Therefore, assets will be pulled from the /template/ directory, which is accessible via WebDAV or via the BigCommerce control panel.

Update Process

1

Switch on Theme Development mode

The partner switches on Theme Development mode, by using: http://<STORE>/admin/index.php?ToDo=viewTemplates&dev=enable.

2

Request theme switch

The partner asks BigCommerce to switch a theme. (Partners currently cannot switch it directly, because it’s a paid theme.)

This step will wipe out all files in the /template/ directory and copy in the latest version of the integrated theme.

3

Pull changes from GitHub fork

The partner pulls changes from BigCommerce’s GitHub fork, to get the most recent version onto their local machine as well.

4

Make changes

The partner makes appropriate changes to CSS/HTML files.

5

Commit and open pull request

The partner commits their changes into the feature branch, and opens a pull request against the BigCommerce fork.

If BigCommerce made conflicting changes (which should happen only when resolving urgent issues), the partner might need to rebase changes (using git rebase master) in order to resolve the conflicts.

6

Email Git URL

Partner emails their Git URL to the BigCommerce Theme Marketplace.

7

Integration

BigCommerce integrates changes into BigCommerce Themes.

Other Requirements

  • Partners must not change the repository’s directory structure or directory names.
  • Files should have permission 644 (rw-r--r--).
  • Directories should have permission 755 (drwxr-x-r-x).