Beyond WordPress: IS 429 Students Put Content Management Systems to the Test

A modern illustration of students comparing several website management dashboards on computer screens, emphasizing different approaches to website design, publishing, and content organization.

What makes a content management system the right choice for a website? Is it ease of use, design flexibility, customization, affordability, or something else entirely?

During the Fall 2025 semester, students in IS 429: Web Content Management and Strategy at the University of Illinois Urbana-Champaign explored these questions through a hands-on assignment that challenged them to venture beyond WordPress and evaluate alternative content management systems (CMS).

Their mission was straightforward: choose an unfamiliar CMS, explore its capabilities, evaluate its strengths and weaknesses, and determine what types of websites and organizations would benefit most from using it.

The results revealed an important lesson about web content management: there is no single CMS that is perfect for everyone.

Exploring the CMS Landscape

Students investigated a variety of platforms, including:

  • Drupal: An open-source CMS offering extensive customization and powerful content management capabilities.
  • Squarespace: A website-building platform emphasizing attractive templates and ease of use.
  • Wix: A visual website builder featuring drag-and-drop editing and integrated tools.
  • Webflow: A design-oriented platform offering substantial control over website layouts and interactions.
  • Blogger: Google’s straightforward blogging platform, designed to make publishing accessible.
  • Weebly: A beginner-friendly website builder with simple editing and e-commerce capabilities.
  • October CMS: A Laravel-based CMS offering flexibility for users comfortable with more technical customization.

Some students created demonstration websites, while others researched their selected platforms through documentation, tutorials, and feature comparisons.

Rather than simply describing each platform, students were encouraged to approach the assignment from the perspective of someone responsible for selecting a CMS for a real organization.

Ease of Use: How Simple Is Simple?

One of the most frequently discussed considerations was usability.

Students evaluating Squarespace generally appreciated its guided setup process, professionally designed templates, and visual editing tools.

One student created a sample cookbook review website, complete with blog, About, and Contact pages. The student observed that Squarespace’s initial setup process asked questions about the website’s purpose, goals, tone, and visual identity. Interestingly, this experience closely resembled the content strategy planning work students had completed earlier in the course.

However, not everyone found the experience equally smooth.

Another student reported frustrating delays when navigating between pages and editing website elements. Although the interface looked approachable, performance problems made certain tasks more difficult than expected.

Wix received similarly mixed feedback. Students appreciated its visual editing environment and customizable templates, but one evaluator struggled to modify a specific element within a predesigned section.

These experiences demonstrated that an interface can appear user-friendly without necessarily being intuitive in every situation.

Drupal: More Control, More Responsibility

Students exploring Drupal encountered a different approach to website management.

Unlike platforms primarily designed around visual page building, Drupal emphasizes structured content, extensibility, and customization.

One particularly interesting evaluation examined Drupal’s accessibility and search engine optimization tools.

The student experimented with the Editori11y accessibility checker, deliberately introducing accessibility problems into sample content to see whether the system would identify them.

When the student created a list without using proper list formatting, the tool displayed a warning. Removing the header row from a table produced a more serious accessibility error.

This was an excellent example of moving beyond a feature checklist and actually testing whether a CMS tool performs its intended function.

The same evaluation explored Drupal modules such as Metatag and SEO-related checklists.

Students recognized that Drupal offers considerable flexibility, but that flexibility comes with additional learning and configuration responsibilities.

For a large organization managing complex content, this trade-off may be worthwhile. For someone publishing a simple personal blog, it might be unnecessary.

Blogger and Weebly: Sometimes Simpler Is Better

Not every website requires a complicated content management system.

Students evaluating Blogger emphasized its straightforward interface, free hosting options, and familiar editing environment.

With basic tools for writing posts, adding images, organizing

Author: TommyMac

Leave a Reply

Your email address will not be published. Required fields are marked *