Content Management System Development at Full Sail University

After two years of building backends from the ground up, designing APIs, writing TypeScript, and deploying to cloud infrastructure, Content Management System Development asked me to install WordPress. I want to be direct about that contrast because it shapes the entire retrospective. CMS tools are real, widely deployed, and professionally relevant. Coming to them after the stack this program otherwise taught made them feel like a detour. That is not a complaint about CMSs. It is an observation about sequencing.

---

Week 1: Surveying the CMS Landscape

My thoughts at the time

Week one was a research exercise: survey the major content management systems, compare their features, and produce a document evaluating which CMS was best suited for different use cases. WordPress, Drupal, Joomla, headless CMS options, proprietary platforms. The landscape is wide and the differences are real. As a conceptual exercise in understanding why CMSs exist and what problem they were designed to solve, this week had genuine value.

The honest framing of that value is that it reinforced something I already understood from a different angle. CMSs exist because not every website needs a custom-built application, and not every person maintaining a website is a developer. That is a legitimate architectural reality. The course positioned it as a revelation. For someone who had been building custom backends for two years, it landed more as a reminder that most of the web runs on infrastructure that was never intended for developers to operate.

Retrospective insight

The CMS research document was the most intellectually engaging deliverable of the course, which is not a strong endorsement of what followed. Understanding where CMSs sit in the broader ecosystem of web development options is genuinely useful context. Knowing when a project does not need a custom backend, when WordPress or a similar platform is the correct tool for the job, and being able to make that recommendation confidently is a professional skill. Week one provided that framing. I just wish the remaining three weeks had built on it in a more technically ambitious direction.

---

Week 2: Deploying a LAMP Stack and Installing WordPress

My thoughts at the time

Week two was server provisioning: spin up a Linux virtual machine, configure Apache, MySQL, and PHP, and install WordPress so it was accessible on the internet. The LAMP stack is foundational infrastructure that has powered a significant portion of the web for decades, and there is real value in understanding how it fits together. Getting Apache to serve a domain, understanding how PHP sits between the web server and the application, and watching WordPress come to life on a server I had configured myself was a satisfying experience the first time.

The issue is that this was not the first time. Server provisioning and deployment had been covered in Deployment of Web Applications, and cloud infrastructure had been covered in depth in Cloud Application Development. Installing WordPress on a LAMP stack is a more constrained and less demanding version of work that had already been covered more rigorously in earlier courses. The skills required to complete week two were a subset of skills the program had already required me to demonstrate.

Retrospective insight

Understanding LAMP architecture is legitimately useful. A large percentage of professional web work involves WordPress deployments, and being able to stand one up from scratch on a Linux server is a differentiating skill in contexts where most people only know how to use managed hosting panels. The gap between what this week could have been and what it was is that the deployment work stopped at installation. The deeper questions about how a LAMP stack performs under load, how you secure it, and how you scale it were not addressed, even though the program had already equipped me to engage with exactly those questions.

---

Week 3: WooCommerce and the Plugin Ecosystem

My thoughts at the time

Week three was e-commerce: install WooCommerce, configure it with products, and build a functioning online store using WordPress plugins and themes. WooCommerce is a genuinely impressive piece of software. The depth of what it handles through configuration alone, product management, payment gateways, inventory tracking, shipping rules, is a concrete demonstration of what a mature plugin ecosystem can deliver without writing a line of custom code.

The deliverable was a configured store rather than a built one. That distinction is not a minor one. The skills being assessed were configuration and evaluation, not development. After building a custom authentication system with JWT, designing a REST API, and deploying containerized applications to AWS, being graded on the ability to install a plugin and add products to a store was a difficult adjustment to make with enthusiasm. The practical use of those skills is real for a specific category of client work. The depth of the assessment did not match the depth of the program up to that point.

Retrospective insight

WooCommerce is something I understand now as a professional tool rather than a development exercise. Knowing how it works, what it handles natively, and where its configuration ceiling sits means I can give an informed recommendation when a client needs an e-commerce solution. That is the most honest version of the value this week provided. It was not a development challenge. It was an orientation to a category of software that handles a real and common business need.

---

Week 4: PHP Customization and the WordPress Codebase

My thoughts at the time

Week four was the closest the course came to development work: open the WordPress codebase, understand how themes and templates are structured, and make meaningful customizations by modifying PHP directly. PHP is a language I had not worked with in the program before, and the WordPress codebase is a genuinely complex artifact that has accumulated two decades of decisions. Getting into the template hierarchy, understanding how WordPress resolves which file handles which request, and making a customization that required actual code changes rather than just clicking through an admin panel was the most technically substantive work of the four weeks.

It was also the week where the course's constraint became most visible. The customizations required were defined and narrow. The PHP work was enough to demonstrate that I could navigate the codebase and produce a targeted change, but not enough to build any real fluency with PHP as a language or WordPress as a development platform. The course policies noted this was a two-strike class. I passed comfortably, but the weight of that designation felt disproportionate to the material.

Retrospective insight

WordPress theme development and PHP customization are marketable skills that a large portion of the freelance and agency web market still depends on. That is a real fact about the industry that is easy to dismiss from inside a program that teaches modern full-stack development. The honest retrospective is that this week gave me enough exposure to navigate a WordPress codebase professionally, which is more than I had before. It is also less than the two years of material preceding it had prepared me to value.

---

Closing Thoughts

Content Management System Development was the first course in the program that felt genuinely misaligned with where I was in my development as an engineer. That is not a criticism of CMS technology or of WordPress specifically. Both are real, in-demand skills in the professional web development market. It is an observation about sequencing and depth. This course would have been more valuable earlier in the program, before building custom backends made the abstractions CMSs provide feel like stepping backward rather than sideways. The skills it covered are worth having. The moment in the program where they were introduced made them harder to appreciate than they deserved.

---

Where I Use This Now

When a client asks about whether they need a custom-built site or a CMS, the answer I give them is informed by this course. For Cairo Photography, the content management needs were simple enough that a headless CMS approach made more sense than a fully custom backend. Knowing what WordPress can and cannot do at the configuration level means I can recommend it honestly when it is the right tool, rather than defaulting to custom builds for projects that do not require them.

---

Code: PHP Template and WordPress Query Patterns

The WordPress template hierarchy pattern that controls which file handles which request:

<?php
// functions.php - register a custom post type
function register_project_post_type() {
    register_post_type('project', [
        'labels' => [
            'name' => 'Projects',
            'singular_name' => 'Project',
        ],
        'public' => true,
        'has_archive' => true,
        'supports' => ['title', 'editor', 'thumbnail'],
    ]);
}
add_action('init', 'register_project_post_type');

And querying custom post data programmatically:

<?php
// Display the three most recent projects
$projects = new WP_Query([
    'post_type' => 'project',
    'posts_per_page' => 3,
    'orderby' => 'date',
    'order' => 'DESC',
]);

if ($projects->have_posts()) :
    while ($projects->have_posts()) : $projects->the_post();
        echo '<h2>' . get_the_title() . '</h2>';
        echo '<p>' . get_the_excerpt() . '</p>';
    endwhile;
    wp_reset_postdata();
endif;

---

FAQ

When should a client use WordPress instead of a custom-built site? WordPress makes sense when the client will be managing content themselves, when the budget does not support ongoing development for content updates, or when a well-maintained plugin already handles the required functionality (e-commerce, forms, membership). Custom builds make sense when the product requires unique functionality, performance constraints, or a development team that will own the codebase long-term.

What is a headless CMS and how is it different from WordPress? A headless CMS manages and stores content without handling the presentation layer. Instead of rendering HTML, it exposes content via an API that any frontend can consume. WordPress in headless mode works this way via its REST API. Dedicated headless CMSs like Contentful or Sanity are built for this pattern from the start. The advantage is that the frontend and content management are completely decoupled.

Is PHP still worth learning as a web developer? PHP powers a significant percentage of the web, including WordPress, which runs roughly 40% of all websites. It is not a primary language for new greenfield development in most modern stacks, but understanding it is useful for any developer who will encounter or maintain WordPress sites, which is most of the freelance and agency market.

What is WooCommerce and when does it make sense for e-commerce? WooCommerce is a WordPress plugin that adds e-commerce capabilities: product management, shopping cart, checkout, and payment processing. It makes sense for small to medium online stores that need to be managed by non-developers and do not require custom checkout logic. Platforms with complex product catalogues, high traffic, or integration requirements beyond WooCommerce's plugin ecosystem typically outgrow it.

Credits and Collaboration

A huge thank you to Esther Allin for designing the blog banner art! If you're looking for a professional digital media specialist, Connect with her on LinkedIn!