CiviCRM Community Forums (archive)

I haven't done much with Drupal before, but need to get an idea as to how much extra work is it for a designer experienced with Drupal to include support for CiviCRM when building a
custom theme.

We don't care about the admin interface, just the publicly accessible donation, membership and account pages.

If the original project was for a website without any authentication for the public (ie neither registration nor login form), could this explain any reluctance to include this in part of the design project?

This is a different question and it's not possible to answer without more details. Perhaps the design depends on all pages being skinny or having a certain particular style. CiviCRM pages tend to require a wide space and certain aspects of the UI are harder to style accurately. For example, many pages are hard coded with tables, so they are difficult to adjust.

Good to hear, that's pretty much what I had thought. So, back end wise there should be no extra work, but it may stretch and break the way the theme is rendered if doesn't have large enough containers for the tables?