April 15th, 2012
I didn't attend any responsive web design sessions at DrupalCon Denver 2012 because there was just too much going on under the hood, both for Drupal 7 and Drupal 8. But before this milestone event fades into the past, it is necessary to grab what this historic "reaffirmation" DrupalCon tells us about the state of Drupal is in this key area and how the rest of us should incorporate it into our development process. What frameworks, base themes, standard configurations, and other approaches should we adopt?
This corrects the grave omission of the whole key subject of responsive web design from my recent report back article on DrupalCon Denver 2012.
Here I attempt to address the question by treating myself to an Easter Sunday responsive web design marathon, and grabbing my first conclusions, synthesized with my thinking up to the present (“Mobile first” is the tip of the iceberg and when blithely repeated reduces to a buzzword without addressing the huge multi-server and services, real time and single page app challenges that are increasingly facing the web app builder. While mobiile first (there, I've said it) responsive web design is key, promiscuous Drupal with multi-node servlets and services integration is fundamental). But this material is absolutely essential, there's a lot to learn, don't go to work without it: I present here my take on each of the following presentations: Rethinking responsive building techniques with drupal - johnalbin, Responsive web design: the past, present, and future – lewisnyman, A responsive project process – daveruse, Creating responsive and mobile-first drupal themes - himerus, Html 4 s - while we're waiting for the revolution - mortendk, and finally Keynote - Luke Wroblewski. BTW, Panopoly is responsive out of the box (what does that even mean?).
For many reasons DrupalCon Denver 2012 was a source of “fresh air” and excitement in the community, with emerging developments promising the “democratizing of technology” and a new head start in Drupal 7 site building (see What's new in panels and several references to the panopoly distribution below). All this of course in the context of the push towards Drupal 8 (currently estimated to be usable in approximately 18 – 24 months from now) and the debate as to what it will be like.
This (longish but I hope useful) article is an objective as possible review of the presentations I recognized as being absolutely key, out of the handful I was able to attend directly. I have organized them into a couple of main threads, as a prelude to a “What's up with Drupal” series of articles to be published in the near future covering my own recommendations and perspectives for site building and web application development with Drupal over the next couple of years.
You can think of Drupal 7 Business Solutions as a magnificent and never ending blog post showing how a business owner can truly get an extremely functional website going using the CMS framework Drupal. The book, written by Trevor James and Mark Noble and published by Packt Publishing, is of course so much more: it includes all the details, all the steps actually required, to design, build, launch and maintain such a website (in this case, the Artisan Bakers Collective Website is the case study used throughout).
November 21st, 2011
Main site: http://aws.amazon.com/
Console overview, tour, all categories of info: http://aws.amazon.com/console/
For example, Amazon EC2 Features at http://aws.amazon.com/console/#ec2
I watched the EC2 tutorial at http://d36cz9buwru1tt.cloudfront.net/console/AwsConsole.html
AWS Documentation: http://aws.amazon.com/documentation/
EC2 Documentation (Getting started (recommended), user's guide, etc.): http://aws.amazon.com/documentation/ec2/
Go to http://aws.amazon.com/ and click on the button which says Sign up for a free Amazon Web Services Account – Sign Up Now.
You can use your existing Amazon customer account email and password if you already have one.
There are lots of bubbly install howto's on the web concerning the Node programming environment. But what are the best practices for updating, really?
First of all I tried the obvious: