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.
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.
I disagree. With decoupling you might have a simple API, but that API is specific to the CMS you're using. You might still want to have a book from which to learn how to use it to create front ends.
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: (Score:1)
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.
I disagree. With decoupling you might have a simple API, but that API is specific to the CMS you're using. You might still want to have a book from which to learn how to use it to create front ends.