[consulting] Drupal site development but with restrictions

[Cameron Eagans]

You could probably do a lot with just Rules, Views, and Panels, but not
allowing glue code is going to significantly hinder anything really crazy
that they want to do. If they don't like custom code, then they can't have
really special things done on their site.

Plus, I assume that this is going to mean that you can't have a version
controlled copy of the site and you're just going to have to work on a
shared dev site (with all of the other developers on the project). This is
going to be a huge pain in the neck.

If it were me, I would not touch this project with a ten foot pole.
--
Cameron Eagans
http://cweagans.net


On Mon, Aug 20, 2012 at 1:37 PM, Sam Cohen <sam at samcohen.com> wrote:

> Hi all,
>
> A big university in our area, one for which I've built many Drupal sites
> for various departments, centers, etc, has recently contracted with Acquia
> for hosting, and they are putting a plan in place where all University
> related sites will be part  have to be hosted by them (and Acqia) and be
> part of a multisite.  They plan to limit which modules sites are permitted
> to use and also want to restrict any custom modules from being used at
> all.
>
> I've never built a site without a custom module and at least some glue
> code and I've never worked with such restrictions.  It's really giving me
> something to think about.  (No word yet on restrictions with custom themes)
>
> I've never encountered this before.  I'm curious if anyone else has run
> into this anywhere.
>
> Thanks,
> Sam
>
>
>
> Sam Cohen, Principal
> New Media Solutions <http://new-media-solutions.com>
> Drupal Training & Services
> * <http://new-media-solutions.com/drupal-training>*
> <http://twitter.com/samcohen>
>
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20120820/9d8fce3b/attachment.html