a summary of our approach to Drupal web development and coding standards

We believe Drupal sites work best for clients when we help provide a roadmap to self- sufficiency, as this is one of the key advantages to be exploited from use of open source technologies. Most of this section, in as far as it relates to project management, is about how we aim to deliver self-sufficiency by how we manage your project.

We also believe it’s key to have a good approach to business continuity planning (BCP), the bed rock of which is supplying solutions which are fully installable from source, backed up by clearly defined documentation and processes.

At miggle we always feel this is achieved by

  • Documentation
  • Clear processes
  • Open source technology
  • Use of accepted standards within open source technology

Within the context of Drupal

  • Commitment to coding standards (http://www.drupal.org/coding-standards)
  • No core or contributed hacks. 
  • If we find bugs in code, patch it and contribute it back to the community
  • Use of contributed modules over custom modules. The less custom code we write the more future proof your solution and the easier to find staff or contractors to manage it. This is key from a BCP perspective.
  • If we can find opportunities to contribute custom modules back to the community via drupal.org we will propose the rationale and benefits behind that you you can make an informed decision. We think there are benefits to this approach for clients, which is one we have taken previously.
  • Where possible, use of base themes for design. Again, this makes it easier to find people who will know how to work on your solution if required
  • Dedicated third-party hosting. All the time you engage us we can manage the technical contact with the hosting provider on your behalf if required. All code (which is versioned) is deployed across multiple environments, which provide opportunities for unit testing, automated testing, regression testing, QA and UAT.
  • miggle approach projects using a continuous integration methodology. What this means is that all code is evaluated and deployed in such a way that it can be rigorously tested before new functionality is released. Automated tasks are defined to reverse the release process should the need arise.
  • A flexible support and maintenance package. Regardless of how self-sufficient you aim to be there are likely to always be areas on which you need support, or new features deployed. We offer flexible support packages which help you manage this.

 

There’s little point in using an open source solution if we then rip it to bits and embellish it with custom code, because the resulting product will quickly lose the benefits that come with iterative improvements to the platform, increasing risks in terms of BCP (Business Continuity Planning) and reducing its level of future proofing. So at miggle, we always look to stay as close to a core and contributed approach as possible, as per Drupal standards – the details of which are described below.

If you want to take back control of your web sites and applications then get in touch with miggle to see how we can deliver operational freedom for you in Drupal.