See for yourself by comparing the designs. Things like omitting the sidebar completely, doing the footer menu well, doing the primary/secondary links ideally, squeezing a language selection block into the header - they're mostly *possible* with Drupal, but they don't fit well with the normal design and tend to require some custom PHP code in the template, rather than Just Working. When I say "too hard" I mean that it was too hard for me to do at that point when I was just creating a prototype of it all. Some, like the primary and secondary links, would have come back properly a little later on, but the thing is they require *work* in Drupal, while in Django the system can be designed that way at a lower level, more friendlily. (For example, instead of having a "language block" which is just a fixed block, you can easily have a template which manages the HTML for the block completely). Working with Drupal yourself extensively, you may disagree with me on the "too hard" - but I hope you'll see what I mean, anyway.
On Mon, Nov 29, 2010 at 11:54 AM, Donna Benjamin <donna@...2156...> wrote:
On Thu, 2010-11-25 at 11:39 +1100, Chris Morgan wrote:
Some elements in duckgoesoink's design I had changed for no good reason other than that in Drupal it would be too hard to do it another way.
Which elements?
-- Donna Benjamin - Executive Director Creative Contingencies - http://cc.com.au ph +61 3 9326 9985 - mob +61 418 310 414 open source - facilitation - web services
sorry, wasn't aware that document wasn't made public I thought it was when I published for those of you who missed it please refresh this link.... https://docs1.google.com/document/d/1K2O-gRdbkP0XATykk6LcPo6O5-JdQzK4QmPpuLo... Thanks!
On Sun, Nov 28, 2010 at 5:24 PM, Chris Morgan <chris.morganiser@...400...>wrote:
See for yourself by comparing the designs. Things like omitting the sidebar completely, doing the footer menu well, doing the primary/secondary links ideally, squeezing a language selection block into the header - they're mostly *possible* with Drupal, but they don't fit well with the normal design and tend to require some custom PHP code in the template, rather than Just Working. When I say "too hard" I mean that it was too hard for me to do at that point when I was just creating a prototype of it all. Some, like the primary and secondary links, would have come back properly a little later on, but the thing is they require *work* in Drupal, while in Django the system can be designed that way at a lower level, more friendlily. (For example, instead of having a "language block" which is just a fixed block, you can easily have a template which manages the HTML for the block completely). Working with Drupal yourself extensively, you may disagree with me on the "too hard" - but I hope you'll see what I mean, anyway.
On Mon, Nov 29, 2010 at 11:54 AM, Donna Benjamin <donna@...2156...> wrote:
On Thu, 2010-11-25 at 11:39 +1100, Chris Morgan wrote:
Some elements in duckgoesoink's design I had changed for no good reason other than that in Drupal it would be too hard to do it another way.
Which elements?
-- Donna Benjamin - Executive Director Creative Contingencies - http://cc.com.au ph +61 3 9326 9985 - mob +61 418 310 414 open source - facilitation - web services
participants (2)
-
Chris Morgan -
Ian Caldwell