One of the most puzzling nightmares for non-technical web deciders has to be the choice of the underlying technical solution; i’ve seen many of them sit there in meetings during the early stages of projects, waiting for the geeky talk to be over!
But even if you feel that web tech matters tend to fly a little over your head, you still might have heard the quite common question that often gets asked first (for most internet websites, at least): “Should we use a CMS or a framework on this one?” However, you might not fully understand what a CMS or a framework is technically speaking (which probably makes you fine leaving it to the tech people).
There even might have been that one time, when you heard about CMFs (Content Management Frameworks), and have felt very, very sad about it…
Well, do not panic, for here are my 2 cents to try to put some order into it for you!
Architecture?
Picture by Frits Ahlefeldt-Laurvig, CC BY-ND
A common metaphor used for web technical architectures is actual building architectures, and i’ve had the high point of it during Fabien Basmaison’s conference at Paris Web last year, which was entirely dedicated to that metaphor. I have to say, it does work in a lot of cases, mostly thanks to that clear cut between technical and non-technical skills and responsibilities, but in some cases it just doesn’t (try to explain data replication, or web services, other than with a very unimaginative neighbour who copies everything you own, or a limited double of the keys for your neighbour to come steal stuff!)
So, here’s the starting point: you want to build some building, and you know what you want, but you don’t know how that thing gets done. Continue Reading »