content-management-systems

Guides theme, plugin, and content model changes across CMS platforms like WordPress, Shopify, and Drupal.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill content-management-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-management-systems
Source: https://github.com/github/awesome-copilot/tree/main/skills/content-management-systems
Command: npx skills add https://github.com/github/awesome-copilot --skill content-management-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

CMS projects mix themes, plugins, admin interfaces, media pipelines, and content models, and editing the wrong layer breaks platform conventions. This Skill helps locate the correct implementation seam before making changes across platforms like WordPress, Shopify, Drupal, and Webflow.

Core Features & Use Cases

  • Seam Identification: Maps any CMS codebase to its owning layers: theme runtime, extension points, admin controllers, content persistence, and render pipelines.
  • Platform-Specific Guidance: Provides a reference table covering extension surfaces and media conventions for WordPress, WooCommerce, Shopify, Wix, Squarespace, Drupal, Joomla, HubSpot CMS Hub, Webflow, and Adobe Experience Manager.
  • Use Case: When adding a custom field to a WordPress theme, the Skill directs you to trace the stored field, validation rules, preview path, and final render path together instead of patching a template in isolation.

Quick Start

Use the content-management-systems skill to add a new taxonomy field to my WordPress theme and update its editor preview.

Frequently Asked Questions about content-management-systems

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide where to make a change in a CMS codebase?

Map the codebase to standard CMS responsibilities first: runtime routing, theme system, admin controllers, content persistence, transformation utilities, and render pipelines. Then make the smallest change at the owning seam rather than scattering logic across templates.

What platforms does this CMS workflow cover?

It covers WordPress, WooCommerce, Shopify, Wix, Squarespace, Drupal, Joomla, HubSpot CMS Hub, Webflow, and Adobe Experience Manager. A reference file maps each platform's extension surfaces and media conventions.

Should theme images go in the media library or theme folder?

Theme-owned decorative images belong in the active theme folder, while user-authored media belongs in the platform's upload or media-library flow, conventionally under uploads/. Keep the two distinct in config and code paths.

How do I handle content model changes in a CMS?

Prefer migration files or exportable schema definitions over ad hoc runtime mutations. Keep slugs, publish dates, excerpts, canonical metadata, and taxonomy relations as structured fields rather than embedding them in presentation markup.

When should I use an app or metafield instead of editing a Shopify theme?

Use app or metafield seams when data must survive theme redesigns. Theme-only changes are appropriate for presentation, but structured data stored in metafields persists independently of the active theme.