Back in the early 2000s, content management systems (CMS) were still in their infancy. Websites were mostly static, and managing content dynamically required custom scripts or early blogging tools. My journey into CMS development started with Greymatter, took me through PHP-Nuke, PostNuke, and XOOPS, and ultimately shaped my understanding of PHP and modular web development.
The Beginning: Greymatter and My First Community
My first encounter with a CMS was Greymatter (Wayback Machine / Already multi-lang !), a Perl / CGI-based news publishing tool. It had an admin interface, allowed full templating, and even supported multiple users. For a first experience, it was pretty powerful! My first community site ran on Greymatter, and I enjoyed tweaking it to fit my needs.
However, Greymatter wasn’t modular enough—every time I wanted to add a new feature, I had to manually integrate it into the code. That quickly became frustrating.
The Rise of PHP (2000-2001): Exploring New Tools
Around this time, PHP was exploding in popularity, and I started looking for something that would make my life as an administrator easier. That’s when I stumbled upon myPHPNuke. It was my first introduction to a PHP-based CMS, but it didn’t hold my attention for long.
I kept testing various blog platforms, but most suffered from:
- Poor documentation
- Weak installation processes
- Limited functionality
- A lack of extensions
Discovering PHP-Nuke: A Game Changer
Then I found PHP-Nuke (Waybackmachine), and everything changed. It had exactly what I was looking for:
- A dedicated admin interface
- A block-based system
- A modular architecture
Excited by the possibilities, I built my first real community site with PHP-Nuke:
i-trends.de – A website dedicated to Windows shell replacements like LiteStep and DesktopX.
I migrated my hand-coded HTML site to PHP-Nuke, started modifying its code, and soon realized I wanted to go even deeper. I bought my first PHP book, dived into learning, and began coding new extensions.
One of PHP-Nuke’s standout features was blocks, but they lacked usability—most were just for display. So I started developing custom sideblocks with usability in mind, extending existing modules, and tailoring the CMS to better serve my community.
Jumping to PostNuke: More Flexibility
As time passed, PHP-Nuke’s development slowed, and I felt restricted by its limitations. That’s when I discovered PostNuke (Waybackmachine)—a fork of PHP-Nuke that promised more flexibility and better modularity.
I quickly migrated i-trends to PostNuke and started working with Patrick Kellum, who was a PostNuke developer at the time. I became a Beta Tester and helped with:
- The first phpBB module integration for PostNuke
- An advanced block system for better customization
During this phase, I developed i-blocks, named after my site, i-trends. These custom blocks added more functional, user-friendly features to PostNuke’s ecosystem.
Exploring XOOPS and Returning to PostNuke
By January 2002, I felt PostNuke development was slowing down, and I started looking for new alternatives. That’s when XOOPS (Waybackmachine) entered the scene. It caught my attention with:
- Fresh ideas
- Simple administration
- A promising development team
However, after testing it, I realized that XOOPS wasn’t evolving quickly enough for my needs. So, I returned to PostNuke and began developing for version 0.7x, which introduced more advanced features.
Becoming a PostNuke Core Developer
By April 2002, I officially joined the PostNuke Management & Development team as a core developer (MagicX). It was an incredible experience working with a talented team to push PostNuke forward.
I stayed with the team until early 2003, but eventually, I had to step away. Differences in management vision and my growing workload made me realize it was time to focus on my own projects. It was a tough decision, but an important one.
5 Years Building My Own CMS – Fenix
I spent five years with a like-minded friend from Mexico City, working on our own CMS. Together, we founded ScriptConnector and began developing Fenix. We had everything functioning and were close to the finish line—but sometimes, the stars just don’t align! (The road to ScriptConnector – Waybackmachine )
Looking Back: The Evolution of CMS and My Growth
Reflecting on my journey from Greymatter to PostNuke, I realize how much these experiences shaped my approach to development. Every system I explored taught me something new—whether it was modularity, usability, or scalability.
This period also ignited my passion for PHP development and laid the foundation for the projects I would work on in the years to come.
Even today, as CMS platforms like WordPress, Joomla, and Drupal dominate the landscape, I look back fondly at those early days—when we were all just hacking, learning, and pushing the boundaries of what was possible.
