upgrade
upgrade

📡Media Technologies

Popular Content Management Systems

Study smarter with Fiveable

Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.

Get Started

Why This Matters

Content Management Systems sit at the intersection of several key concepts you'll be tested on in Media Technologies: platform architecture, user experience design, scalability, and the democratization of web publishing. Understanding CMS options isn't just about knowing which tool does what—it's about recognizing how different architectural approaches (monolithic vs. headless, hosted vs. self-hosted) shape what's possible for content creators and businesses. These platforms represent the infrastructure layer that determines how digital content reaches audiences.

When you encounter CMS questions on an exam, you're being tested on your ability to match technical requirements to appropriate solutions. Can you identify why a government agency needs different features than a fashion blogger? Do you understand the trade-off between ease of use and customization flexibility? Don't just memorize platform names—know what architectural philosophy and target use case each system represents.


Traditional Open-Source CMS Platforms

These platforms give users full control over their code and hosting, following a monolithic architecture where the front-end and back-end are tightly coupled. They prioritize flexibility and community-driven development over simplicity.

WordPress

  • Powers over 40% of all websites globally—this market dominance makes it the default standard for understanding CMS functionality
  • Plugin and theme ecosystem creates virtually unlimited customization through modular add-ons rather than core code changes
  • Low barrier to entry with intuitive dashboard, though this accessibility can lead to security vulnerabilities when users neglect updates

Drupal

  • Enterprise-grade security architecture—preferred by government agencies and large institutions requiring strict data protection
  • Modular system with extensive API support allows developers to build complex, interconnected content structures
  • Steeper learning curve reflects its power; requires developer expertise but offers unmatched control for large-scale deployments

Joomla

  • Built-in multilingual support—unlike WordPress, which requires plugins, Joomla handles multiple languages natively in its core
  • Advanced user management makes it suitable for membership sites, intranets, and platforms requiring complex permission structures
  • Middle-ground positioning between WordPress's simplicity and Drupal's complexity, though this has limited its market differentiation

Compare: WordPress vs. Drupal—both are open-source and self-hosted, but WordPress prioritizes accessibility while Drupal prioritizes security and scalability. If an FRQ asks about platform selection for a government website, Drupal is your answer; for a small business blog, WordPress.


Hosted Website Builders

These platforms bundle hosting, design tools, and CMS functionality into all-in-one solutions. They sacrifice customization depth for ease of use, targeting users who prioritize speed over technical control.

Wix

  • Drag-and-drop interface eliminates coding requirements entirely, representing the extreme end of user-friendly web design
  • Cloud-based architecture means no software installation or server management, but also limited portability if you want to migrate
  • Built-in SEO and marketing tools reflect the platform's focus on small business owners who need integrated solutions

Squarespace

  • Design-forward template library—templates are created by professional designers, prioritizing visual aesthetics over raw functionality
  • All-in-one pricing model bundles hosting, domains, and e-commerce, simplifying the purchase decision but limiting flexibility
  • Target audience of creatives and artists shapes every feature decision, from portfolio layouts to image optimization

Compare: Wix vs. Squarespace—both are hosted builders targeting non-technical users, but Wix emphasizes customization freedom while Squarespace emphasizes design polish. Think of Wix as "build anything" and Squarespace as "build something beautiful."


E-Commerce Specialized Platforms

These systems are built specifically for online retail functionality, with features like inventory management, payment processing, and order fulfillment integrated into the core architecture rather than added through plugins.

Shopify

  • Purpose-built for online stores—payment processing, shipping calculations, and inventory tracking are native features, not add-ons
  • App ecosystem extends functionality while maintaining the platform's managed, user-friendly approach
  • Subscription pricing model includes hosting and security, making total cost predictable for small to medium retailers

Magento

  • Enterprise-scale architecture handles thousands of products and high traffic volumes that would overwhelm simpler platforms
  • Extensive customization requires developer expertise—this is not a DIY solution but a professional development platform
  • Open-source community edition available alongside paid enterprise version, offering flexibility in deployment models

Compare: Shopify vs. Magento—both dominate e-commerce, but Shopify targets small-to-medium businesses wanting simplicity while Magento serves large enterprises needing unlimited customization. The trade-off is ease of use vs. scalability.


Content-First Publishing Platforms

These platforms prioritize the writing and publishing experience over design flexibility, built specifically for bloggers, journalists, and content-focused organizations.

Ghost

  • Minimalist publishing interface—strips away complexity to focus entirely on writing and content delivery
  • Built-in membership and subscription features support direct monetization without third-party plugins
  • Open-source with hosted option gives users choice between self-hosting control and managed convenience

Headless and API-First Architecture

Headless CMS platforms decouple content management from content presentation, allowing developers to deliver the same content across websites, apps, and other channels through APIs. This represents a fundamental architectural shift from traditional CMS design.

Contentful

  • API-first architecture means content is stored once and delivered anywhere—web, mobile apps, IoT devices, digital signage
  • Separation of concerns allows content teams and developers to work independently with different tools and timelines
  • Enterprise scalability supports complex content models and high-volume delivery across global infrastructure

Webflow

  • Visual development environment bridges the gap between design tools and CMS functionality without requiring traditional coding
  • Hybrid approach combines visual design freedom with structured CMS capabilities for dynamic content
  • Designer and agency focus positions it as a professional tool rather than a DIY builder, despite its visual interface

Compare: Contentful vs. traditional CMS platforms—Contentful's headless architecture offers omnichannel delivery but requires developer resources to build front-ends, while WordPress or Drupal provide complete websites out of the box. Choose headless when content must appear across multiple platforms simultaneously.


Quick Reference Table

ConceptBest Examples
Open-source flexibilityWordPress, Drupal, Joomla
Enterprise securityDrupal, Magento
Beginner-friendlyWix, Squarespace, WordPress
E-commerce specializedShopify, Magento
Design-focusedSquarespace, Webflow
Headless/API-firstContentful, (Ghost API)
Content creator monetizationGhost, Shopify
Large-scale/high-trafficDrupal, Magento, Contentful

Self-Check Questions

  1. Which two platforms would you recommend for a government agency requiring maximum security, and what architectural features make them appropriate?

  2. Compare and contrast Shopify and Magento: what type of business would choose each, and why does the trade-off between ease of use and scalability matter?

  3. A media company wants to publish articles on their website, mobile app, and smart TV app simultaneously. Which CMS architecture would best serve this need, and which platform exemplifies it?

  4. What distinguishes hosted website builders (Wix, Squarespace) from traditional open-source CMS platforms (WordPress, Drupal) in terms of user control and technical requirements?

  5. If an FRQ asks you to recommend a CMS for a professional photographer with no coding experience who prioritizes visual presentation, which platform would you choose and what features justify your selection?