A few months ago I realized how lucky we are in Drupal for the solution we have for responsive images. I reviewed the different automated tools for Responsive Images outside Drupal when I was looking for documentation for a Responsive Web Design talk. I saw there are many great solutions, but few of them incorporate the concept of artistic direction, or in other words the ability to decide how the images should be adapted to each device.
Blog: drupal planet
While working with Drupal 7 we had some development workflows that worked very well for us and now we want to adapt those workflows to the new major version of Drupal.
One of this "development features" as you may call them was the possibility of having some predefined content that can be recreated at any time to test the site. For example you don't have to worry about creating new users that represent the different roles every time you set up a fresh site, they will be there.
Some time ago I was chatting about Drupal with a friend who said to me:
“But my clients prefer Wordpress because Drupal is not user friendly for the content administration.”
I was amazed and I promised to him that I’ll write a post to show everybody how usable and user friendly Drupal could be. So, here it is!
Following the series Mercè started and the talks I have been giving I wanted to write a bit more about Behat and some niceties that I learned on the way.
One of the main points people get interested on Behat is not only because you can use natural language to describe and test your application but also because all the tests are able to run in a real browser.
Let’s make an overview of the main pieces available to achieve a broader testing strategy.
Automated testing is one of the resources that greatly facilitates the task of development and one of the tools we can use with good integration with Drupal is Behat. It's an open source framework for behavioral testing, and that means that the testing is done using the web as a user would do.
One of its main strengths is its readability: it is written in natural language describing the behavior to be tested, and allows us to check at any time if our application behaves as expected.
In Ymbra we find it especially useful to know if any new changes we have made to the code produces some regression in functionality, which can easily pass unnoticed and take some time to be detected.
Nowadays frontend developers can't live without some preprocess tool that make tackling the CSS style easier.
In Ymbra we prefer Sass (Syntactically Awesome StyleSheets) in the themes of our projects, and often we opted to develop subthemes of Zen, and take advantage of all the tools and benefits that gives us regarding writing the CSS style of the project.
I would like to explain how Sass can help...
Few days ago in Ymbra we had a challenge about how to load Drupal 7 entities during a cron job. The main issue here is that cron doesn't run with enough credentials and we need higher permissions to perform some operations.
Those entities had user access restrictions in place and when cron runs as anonymous user (even if you trigger it logged in as the user with id=1) those restrictions were respected and we weren't able to load our entity content to be later sent in an email.
So what can we do to run cron as Drupal admin?
While the American Drupalistas (and some brave travellers) are enjoying a fantastic DrupalCon in Austin, the Amsterdam organising comittee is working hard to produce the best European DrupalCon ever. This team is formed by Drupal Association staff and a group of volunteers, of which I am one, and at the moment we're in the process of getting session proposals and selecting the best possible content....
Since its inception, Ymbra has taken very seriously to get involved in community by all possible means and it is for this reason that we have always been present in as many drupal events as possible, being Drupal Camps in Spain and Drupal Developer Days mandatory (so if if you have attended to any drupal event in Europe you are likely to have met any of us!). And since attendance is not enough for us, we have tried to get involved in those events in many different ways: as sponsors, presenting...