The fact we have a book on front-end CMS design is irony in itself.
The problem with popular CMS systems today stems from the tight coupling of back-end architecture and front-end architecture.
Remove the coupling, and the need for a book on Front End Drupal vanishes, leaving us with a simple API which we can integrate with our own custom or third party front-end.
by Anonymous Coward writes:
on Tuesday May 19, 2009 @03:54AM (#28008499)
I agree with this and it's one of the reasons I like drupal. It makes the back-end, which used to be the largest part of a job (setting up a way to put data into a system), into the smallest.
With the way templates work, you're pretty much free to do whatever you want. And honestly, if you just want to throw out the drupal front-end system altogether you could do that, and either use their API to get the data you need or just write your own way to get the data out of the database in the way you want.
I have to say, though, I tried dozens of other CMSs over the years and always hated them (as most people on slashdot today seem to hate them). Drupal is the first one I've found to be robust, intelligently put together (you almost never have to hack the core files for any reason, despite what many people are claiming), and ridiculously easy learning curve (again, against what most people here are saying... but then, I suspect they tried to jump right in as programmers looking for things to develop rather than realizing 98% of what you need is already out there).
CMS should have no "front end" (Score:2)
The problem with popular CMS systems today stems from the tight coupling of back-end architecture and front-end architecture.
Remove the coupling, and the need for a book on Front End Drupal vanishes, leaving us with a simple API which we can integrate with our own custom or third party front-end.
Re:CMS should have no "front end" (Score:0)
I agree with this and it's one of the reasons I like drupal. It makes the back-end, which used to be the largest part of a job (setting up a way to put data into a system), into the smallest.
With the way templates work, you're pretty much free to do whatever you want. And honestly, if you just want to throw out the drupal front-end system altogether you could do that, and either use their API to get the data you need or just write your own way to get the data out of the database in the way you want.
I have to say, though, I tried dozens of other CMSs over the years and always hated them (as most people on slashdot today seem to hate them). Drupal is the first one I've found to be robust, intelligently put together (you almost never have to hack the core files for any reason, despite what many people are claiming), and ridiculously easy learning curve (again, against what most people here are saying... but then, I suspect they tried to jump right in as programmers looking for things to develop rather than realizing 98% of what you need is already out there).