Design and Getting it Right The First Time
Monday, July 20th, 2009
I have a project that I started back in May that is right about feature complete. I used a common CMS because the customer thought that is what they needed. It has several features that I wanted: user management, photo albums, easily extensible.
I thought I needed a fully-built CMS. Jesus was I wrong.
It started off ok enough, built some custom functions into the theme, did some shady things with nodes and pages and detecting which page the user was on. It worked well enough, tricking the theme into displaying things I wanted it to, where I wanted it to. Then the customer wanted something fairly easy: Photo Albums.
Oh. My. Lord. I have never had so much trouble trying to get photos to display. There are a myriad of photo plugins/addons/managers. Somehow, none of them are intuitive or function properly. There is a separate plugin (“module”) just for images. Go ahead, try to tell me what you ACTUALLY need to use it.
Some of the modules straight didn’t work, some needed 14 different other modules just to tell me they didn’t want to work. It was a pain in the butt, but I finally found one that worked fair enough, but still didn’t have what I wanted.
Then the customer wanted something a little more tricky: email lists. I have no clue how to do this. None. I don’t even want to try.
Now, I am using a PHP framework and starting from scratch. Back in May when I started, I had never used a framework before. I used this same one on another project about a month ago, and have had favorable results. So now, I’m firing up my text editor and trying again.
This is going to be less of a headache than you think. CakePHP is very easy to set up with user privileges, and once there, it’s just a matter of moving my functions to the proper Models and tweaking some of the pages.
More to come when this is done. Hopefully.
I have a project that I started back in May that is right about feature complete. I used a common CMS because the customer thought that is what they needed. It has several features that I wanted: user management, photo albums, easily extensible.
I thought I needed a fully-built CMS. Jesus was I wrong.
It started off ok enough, built some custom functions into the theme, did some shady things with nodes and pages and detecting which page the user was on. It worked well enough, tricking the theme into displaying things I wanted it to, where I wanted it to. Then the customer wanted something fairly easy: Photo Albums.
Oh. My. Lord. I have never had so much trouble trying to get photos to display. There are a myriad of photo plugins/addons/managers. Somehow, none of them are intuitive or function properly. There is a separate plugin (“module”) just for images. Go ahead, try to tell me what you ACTUALLY need to use it.
Some of the modules straight didn’t work, some needed 14 different other modules just to tell me they didn’t want to work. It was a pain in the butt, but I finally found one that worked fair enough, but still didn’t have what I wanted.
Then the customer wanted something a little more tricky: email lists. I have no clue how to do this. None. I don’t even want to try.
Now, I am using a PHP framework and starting from scratch. Back in May when I started, I had never used a framework before. I used this same one on another project about a month ago, and have had favorable results. So now, I’m firing up my text editor and trying again.
This is going to be less of a headache than you think. CakePHP is very easy to set up with user privileges, and once there, it’s just a matter of moving my functions to the proper Models and tweaking some of the pages.
More to come when this is done. Hopefully.