Managing Themes

In the WPCloset ecosystem, a Theme represents the visual and structural foundation of a WordPress site. By hosting your proprietary themes—or managed public themes—in WPCloset, you ensure that your design integrity remains secure while providing a controlled update experience for your users.

The Concept of a Managed Theme

Unlike public themes, a WPCloset theme is restricted to authorized installations. The theme record in your dashboard acts as the central authority, managing the identity, metadata, and version history for your visual assets.

Managing themes via WPCloset provides:

• Design Protection: Your custom designs are shielded from the public; only authorized sites can access the source code.
• Maintenance Control: Whether it’s a custom layout or a popular public framework, you control the rollout of CSS fixes and design changes.
• Native Integration: Private themes appear in the WordPress “Appearance” screen with professional metadata and screenshots, just like a theme from the public repository.

Adding Themes to Your Library

WPCloset supports two methods for adding visual assets to your repository:

1. Custom Design Uploads

Upload your proprietary theme .zip files directly. WPCloset automatically parses the style.css headers to extract the theme name, version, and author details for you.

2. Importing from the Public Repository

You can import any theme from the official WordPress.org directory.

• Why Import? Public themes often receive frequent updates that can change layouts or break custom CSS “child themes.” By importing a public theme into WPCloset, you “freeze” the version.
• Managed Updates: Once imported, your sites will no longer check the public repository for that theme. You choose when to bring in a new update from the public source, ensuring you can test visual changes before they reach your production sites.

Establishing Theme Identity

The Theme Slug (The Matching Key)

The Slug is the unique identifier for your theme (e.g., agency-pro-theme).

• Update Locking: If a theme slug matches one found in the public WordPress repository, WPCloset logic takes priority. This “locks” the theme to your private vault, ensuring that public updates never overwrite your custom code or “reset” your design configurations.

Versioning and Iteration

In WPCloset, the theme record is the “Blueprint,” and the Versions are the actual code iterations.

• Releasing Design Updates: Every time you refine a design or import a new public version, you create a new Version record and upload the corresponding .zip file.
• Changelogs: Documenting changes helps site administrators understand what visual or functional changes will occur once they click “Update.”

Controlled Distribution via Environments

Themes are not pushed to all sites by default. You control the rollout through Deployments to specific Environments.

• Design Workflows: Environments allow you to manage a “Design Pipeline.” You can test a major redesign on a Development environment without affecting the stable look of your Production fleet.
• Instant Activation: Toggling a version as active for an environment immediately makes it the “Current Version” for every authorized site in that tier.

Use Cases for Theme Management

• Individuals: Maintain a “Master Parent Theme” with your preferred configurations and keep it updated across all your personal projects.
• Agencies: Manage a “Brand Framework” theme used across all client projects. When you update the framework’s mobile responsiveness, you can deploy the update to every client site at once.
• Enterprise: Maintain a strict “Corporate Identity” theme across all internal departmental sites, ensuring that branding, colors, and legal headers remain consistent across the entire organization, even if the underlying framework is a public one.