awesome-copilot/plugins/cms-development/skills/content-management-systems/references/cms-platform-workflows.md

CMS Platform Workflows

This reference keeps the high-level platform map close to the skill so the agent can choose the right seam quickly.

Platform Map

Platform	Primary extension surfaces	Media and asset convention	Notes
WordPress	Themes, plugins, template parts, hooks	Theme assets inside the active theme; authored media under uploads-style paths	Good fit for template hierarchy, taxonomy, custom fields, and local/static export workflows
WooCommerce	WordPress themes and plugins plus product/catalog extensions	Same base conventions as WordPress, with product imagery as authored media	Treat it as WordPress first, then apply commerce-specific content and admin rules
Shopify	Themes, Liquid sections, blocks, apps, metafields	Theme assets and hosted store media are distinct concerns	Prefer app or metafield seams over theme-only hacks when data must survive redesigns
Wix	Site builder surfaces, apps, content collections, custom elements	Hosted media library plus editor-managed assets	Favor editor-safe changes and avoid assuming file-system level access
Squarespace	Templates, code injection, content collections, commerce settings	Hosted asset library managed through the platform	Expect narrower extension points and stronger hosted constraints
Drupal	Themes, modules, content types, views, taxonomy	Managed files and theme assets are separate	Strong fit for structured content, enterprise workflows, and migration-heavy changes
Joomla	Templates, modules, components, plugins	Managed media plus template-owned assets	Similar split between templates and extensions; watch routing and content component boundaries
HubSpot CMS Hub	Themes, modules, templates, serverless functions, CRM-linked content	Hosted file manager plus theme assets	Content, marketing, and CRM concerns are tightly coupled
Webflow	Designer, CMS collections, components, embeds, limited code export	Hosted assets and CMS collection media	Export constraints matter; distinguish what survives export from what depends on hosted CMS features
Adobe Experience Manager	Components, templates, content fragments, experience fragments, workflows	DAM-managed assets plus component resources	Enterprise governance, authoring workflows, and content fragment models drive most changes

Media Rule of Thumb

• Theme-owned images belong with the theme or template package.
• User-authored images belong in the platform's upload or media-library flow.
• If a project supports both, keep them distinct in config and in code paths.

Generic CMS Responsibility Map

Most CMS codebases group behavior into the same handful of responsibilities. Use this as a checklist when locating the owning seam in any project:

• Runtime assembly and request routing
• Theme or template system and shared template helpers
• Admin and editor controllers with their view templates
• Content, taxonomy, and settings persistence (repositories, models, schema/migrations)
• Content transformation utilities (markdown, shortcodes, block renderers)
• Static export, deploy, or render pipeline entry points

Map the project to these responsibilities first, then make the smallest change that preserves the platform's structure.