9 Things You Must consider For Drupal Development

Version Control

Theres really no excuse not to learn, love and religiously use version control.

Local Development Support

Nothing is faster than local development where a developer sets up the full stack on their device.

Online Workspace

This sounds contrary to local development, and it is, but its no less important.

Continuous Integration Tools

One thing that makes projects chaotic is when unexpected bugs crop up. The whole it worked on my machine conversation is everyones least favorite.

http://www.brainvire.com/drupal-cms-development/

A Dev Environment that Matches Production

Going along with the Continuous Integration point, theres nothing more frustrating than a bug that manifests in production.

http://www.brainvire.com/drupal-cms-development/

Access to Debug

If you are trying to figure out a bug, and it works locally but not in the deployment pipeline, youve got to get direct access to start hunting it down.

http://www.brainvire.com/drupal-cms-development/

Drush Remotes

Drupal developers love Drush, the Drupal shell (or alternatively, Drupal in a rush, which is how its pronounced).

http://www.brainvire.com/drupal-cms-development/

Power Tools

The modern website performance stack goes well beyond LAMP. You need to make sure your developers have access to Redis, Solr and can test their work with a reverse-proxy cache like Varnish.

http://www.brainvire.com/drupal-cms-development/

Integration Points

If youre ever stuck trying to think up a conversation-starter with a group of developers, ask them what text editor they use.

http://www.brainvire.com/drupal-cms-development/

Contact us : +1 631-897-7276

Email on : info@brainvire.com

www.brainvire.com