Most development shops make use of a "development/staging/production" server model.
With Big Data and Open Data Initiatives gaining momentum at quick pace, commercial, non-profit and government organizations are looking for innovative make-overs of how they present data to their stakeholders.
Drupal's great. But why is it so hard to have velocity but not viscosity around clients, dev teams and projects? This thrashing leaves many clients leaving Drupal and many Drupalers hating clients.
Content creators are the people who will continue using the CMS you built, years after you've left the project. As a Drupal Sitebuilder/Developer, you are designing the workflows that will help them to work effectively... or perhaps, condemn them to daily frustration and rage. Their fate (and their lasting impression of Drupal) is in your hands.
- Generate PDFs, JPGs or PNGs of any page on your site as rendered at any screen resolution.
- Generate thumbnail images of any page.
- Test page generation and rendering times as separate from transport times.
- Script and test site interactivity: script clicks and mouseovers on arbitrary pixels or DOM elements and test the results.
- Drush integration.
In this panel discussion, we examine the challenges of using Drupal to bring EPA’s sprawling legacy sites into the modern age. Adapting Drupal to meet the unique needs and workflow of a large government agency isn’t always a pretty process.
We have all heard the buzzword "Responsive Design". There are countless examples of Responsive websites and you may have even dabbled in creating Responsive elements of a website.
There's a lot of talk these days about best practices in development and a lot of handwringing between designers and developers on how best to manage multiple server environments, codebases, and staging/production sites.