The horror that is proprietary CMS
Turns out CollegePublisher is a nightmare for XHTML/CSS guys like me. On the one hand I can understand that they’re trying to divvy every individual component into its “object”, but having to edit countless, separate boxes full of code isn’t exactly easy when you’re trying to redesign a whole site. The main problem is keeping track of which code is going where. Add into this that there’s object-oriented code everywhere and you’re staring straight into a big mess.
To be fair, I’ve only glanced through the system. I’m still clinging to the hope that I’ll be able to keep track of everything, not to mention be able to do the things I want to do once I have a design to work with.
UPDATE: [Sept. 10, 2007, 8:00 PM] To CP’s credit they responded very quickly to a request I made over the weekend and had a test domain set up and ready to go for me by early Monday. I requested this so I can play around with the system without breaking the live site. Thanks CP! :-)
September 18th, 2007 at 8:32 pm
No wonder I couldn’t make heads or tails of it half the time.