Skip to Content

Newsfeeds

Twitter Lead Generation Cards

New Drupal Modules - 9 January 2015 - 3:46pm

Twitter Lead Generation Cards are a way to let Twitter users sign up for more information about a product. Twitter users click a button to indicate their interest in something which causes a server-to-server request to an endpoint to store that information.

This module provides an endpoint that can handle those server-to-server requests.

Categories: Drupal

3C Web Services: How to override field templates in Drupal 7

Planet Drupal - 9 January 2015 - 1:42pm

Drupal provides a quick and simple way to customize field output globally using template files. Overriding a field's template file can be useful if you need to customize the HTML, data, or provide custom logic to a Drupal field. Template files allow you to target all fields, fields of specific names, fields of specific types and fields of specific content types.

Categories: Drupal

Chapter Three: Principles of Configuration Management - Part Two

Planet Drupal - 9 January 2015 - 1:01pm

This is the second in a series of posts about Drupal 8's configuration management system. The Configuration Management Initiative (CMI) was the first Drupal 8 initiative to be announced in 2011, and we've learned a lot during thousands of hours of work on the initiative since then. These posts will share what we've learned and provide background on the why and how. In case you missed it, you can read the first part here.

Categories: Drupal

Video: Painful PR lessons learned on the way to Guacamelee!

Social/Online Games - Gamasutra - 9 January 2015 - 12:32pm

Developers, how do you best maximize your game's exposure with a limited marketing budget? Drinkbox Studios' (Guacamelee!) Chris McQuinn shares his advice and lessons learned in this GDC 2014 talk. ...

Categories: Game Theory & Design

Drupal Easy: DrupalEasy Podcast 142: New Jersey (News Lightning Round)

Planet Drupal - 9 January 2015 - 12:29pm
Download Podcast 142

...and we're back! After a holiday hiatus, Andrew, Ryan, Ted, and Mike are back for a guest-less news round-up. We set the timer and spent 3 minutes on over a dozen different Drupal-related news items from the past 8 weeks. Drupal 8, Drupal.org user personas, and major merger, someone gets a job, and several 2014 lists are covered, along with our picks of the week.

read more

Categories: Drupal

Acquia retrospective 2014

Dries Buytaert - 9 January 2015 - 12:01pm

As is now a tradition for me, here is my annual Acquia retrospective, where I look back at 2014 and share what is on my mind as we start the new year. I take the time to write these retrospectives not only for you dear reader, but also for myself, because I want to keep a record of the changes we've gone through as a company and how my personal thinking is evolving from year to year. But I also write them for you, because you might be able to learn from my experiences or from analyzing the information provided. If you would like to, you can read my previous retrospectives: 2009, 2010, 2011, 2012 and 2013.

For Acquia, 2014 was another incredible year, one where we beat our wildest expectations. We crossed the major milestone of $100 USD million in annual revenue, the majority of which is recurring subscription revenue. It is hard to believe that 2014 was only our sixth full year as a revenue-generating business.

We've seen the most growth from our enterprise customers, but our number of small and medium size customers has grown too. We helped launch and host some incredible sites last year: from weather.com (a top 20 site) to the Emmys. Our efforts in Europe and Asia-Pacific are paying off; our EMEA business grew substantially, and the Australian government decided to switch the entire government to Drupal and the Acquia Platform.

We hired 233 people in 2014 and ended the year with 575 employees. About 25% of our employees work from home. The other 75% work from offices around the world; Burlington MA (US), Portland OR (US), Washington DC (US), Paris (France), Reading (United Kingdom), Ghent (Belgium), Singapore, Delhi (India), Brisbane (Australia) and Sydney (Australia). About 75% of our employees are based in the United States. Despite our fast growth rate in staff, recruiting remains a key challenge; it's hard to hire as fast as we do and maintain the high bar we've set for ourselves in terms of talent and commitment.

We raised venture funding twice in 2014: a $50MM series F round led by New Enterprise Associates (NEA) followed by Amazon investing an undisclosed amount of money in our business. It's not like Tom Erickson and I enjoy raising money, but building and expanding a sales and marketing team is notoriously difficult and requires big investments. At the same time, we're building and supporting the development of multiple products in parallel. Most companies only build one product. We're going after a big dream to become the preferred platform for what has been called the "pivot point of many enterprise tech stacks" -- the technologies that permit organizations to deliver on the promises of exceptional digital customer experiences from an agile, open, resilient platform. We are also competing against behemoths. We can't show up to a gunfight with a knife, so to speak.

Building a digital platform for the enterprise

Digital has changed everything, and more and more organizations need or want to transform into digital-first businesses to stay in step with the preferences of their customers. Furthermore, technology innovations keep occurring at an ever faster and more disruptive pace. No organization is immune to the forces of digital disruption. At Acquia, we help our customers by providing a complete technology platform and the support necessary to support their digital initiatives. The Acquia Platform consists of tools and support for building and managing dynamic digital experiences. It includes Acquia Cloud, which helps developers deliver complex applications at scale, and Acquia Lift, our digital engagement services for bringing greater context to highly personalized experiences. Let me give you an update on each of the major components.

Drupal tools and support

Drupal gives organizations the ability to deliver a unified digital experience that includes mobile delivery, social and commerce. Great inefficiencies exist in most organizations that use a variety of different, disconnected systems to achieve those three essentials. They are tired of having to tie things together; content is important, social is important, commerce is important but connecting all these systems seamlessly and integrating them with preferred applications and legacy systems leads to massive inefficiencies. Companies want to do things well, and more often than not, Drupal allows them to do it better, more nimbly and in a far more integrated framework.

In 2010, we laid out our product vision and predicted more and more organizations would start to standardize on Drupal. Running 20 different content management systems on 20 different technology stacks is both an expensive and unnecessary burden. We've seen more and more large organizations re-platform most of their sites to Drupal and the Acquia Platform. They realize they don't need multiple content management systems for different sites. Great examples are Warner Music and Interscope Records, who have hundreds of sites on Drupal across the organization, resulting in significant cost savings and efficiency improvements. The success of our Acquia Cloud Site Factory solution has been gratifying to witness. According to a research study by Forrester Consulting, which we released late last year, ACSF is delivering a 944% return on investment to its adopters.

After many years of discussion and debate in the Drupal community, we launched the Acquia Certification Program in March 2014. So far, 546 Drupal developers from more than 45 countries have earned certification. The exams focus on real world experience, and the predominant comments we've heard this past year are that the exams are tough but fair. Acquia delivered six times the amount of training in 2014 compared to the previous year, and demand shows no sign of slowing.

Last, but definitely not least, is Drupal 8. We contributed significantly to Drupal 8 and helped it to achieve beta status; of the 513 critical Drupal 8 bugs fixed in 2014, Acquia's Office of the CTO helped fix 282 of them. We also funded work on the Drupal Module Upgrader to automate much of the work required to port modules from Drupal 7 to Drupal 8.

Acquia Cloud

Drupal alone isn't enough for organizations to succeed in this digital-first world. In addition to adopting Drupal, the cloud continues to enable organizations to save time and money on infrastructure management so they can focus on managing websites more efficiently and bringing them to market faster. Acquia customers such as GRAMMY.com have come to depend on the Acquia Cloud to provide them with the kind of rugged, secure scale that ensures when the world's attention is focused on their sites, they will thrive. On a monthly basis, we're now serving more than 33 billion hits, almost 5 billion pageviews, 9 petabytes of data transferred, and logging 13 billion Drupal watchdog log lines. We added many new features to Acquia Cloud in 2014, including log streaming, self-service diagnosis tools, support for teams and permissions, two-factor authentication, new dashboards, improved security with support for Virtual Private Networks (VPNs), an API for Acquia Cloud, and more.

Acquia Lift

As powerful as the Drupal/Acquia Cloud combination may be, our customers demand far more from their digital properties, focusing more and more on optimizing them to fully deliver the best possible experience to each individual user. Great digital experiences have always been personal; today they have to become contextual, intuitively knowing each user and dynamically responding to each user's personal preference from device to location to history with the organization. After two years of development and the acquisition of TruCentric, we launched Acquia Lift in 2014.

It's surprising how many organizations aren't implementing any form of personalization today. Even the most basic level of user segmentation and targeting allows organizations to better serve their visitors and can translate into significant growth and competitive differentiation. Advanced organizations have a single, well-integrated view of the customer to optimize both the experience and the lifetime value of that customer, in a consistent fashion across all of their digital touchpoints. Personalization not only leads to better business results, customers have come to expect it and if they don't find it, they'll go elsewhere to get it. Acquia Lift enables organizations to leverage data from multiple sources in order to serve people with relevant content and commerce based on intent, locations and interests. I believe that Acquia Lift has tremendous opportunity and that it will grow to be a significant business in and of itself.

While our key areas of investment in 2014 were Acquia Cloud and Acquia Lift, we did a lot more. Our Mollom service blocked more than 7.8 billion spam messages with an error rate of only 0.01%. We continue to invest in commerce; we helped launch the new Puma website leveraging our Demandware connector and continue to invest and focus on the integration of content and commerce. Overall, the design and user experience of our products has improved a lot, but it is still an area for us to work on. Expect us to focus more heavily on user experience in 2015.

The results of all our efforts around the launch of the Acquia Platform have not gone unnoticed. In October, Acquia was identified as a Leader in the 2014 Gartner Magic Quadrant for Web Content Management.

The wind is blowing in the right direction

I'm very optimistic about Acquia's future in 2015. I believe we've steered the company to be positioned at the right place at the right time. As more organizations are shifting to becoming digital-first businesses they want to build digital experiences that are more pervasive, more contextual, more targeted, more integrated, and last but not least, more secure.

The consolidation from many individual point solutions to one platform is gaining momentum, although re-platforming is usually a long process. Organizations want the unified or integrated experience that Drupal has to offer, as well as the flexibility of Open Source. It is still time consuming and challenging to create quality content, and I believe there is plenty of opportunity for us and our partners to help with that going forward.

Without a doubt, organizations want to better understand their customers and use data-driven decisions to drive growth. Data is becoming the new product. The opportunity this creates in commerce is massive.

Cloud computing and Software-as-a-Service (SaaS) continues to be on the rise. Cloud is top of mind and the transition away from on-premise solutions is accelerating even as the arguments around security and privacy issues in the cloud continue to be raised. While there is a certain amount of emotion, and sometimes politics, people are beginning to realize that the cloud is usually more secure and more robust against cyber-attacks than traditional on-premise systems.

The promise of Drupal 8, arguably the most significant advance in the evolution of the Drupal software, has me very excited. It is shaping up to be a great release, and I'm confident it will further secure Drupal's reputation among developers, designers, agencies and site managers as the most flexible, powerful content management solution available.

All of this is not to say 2015 will be easy. This is an incredibly exciting and fast-changing space in the world of technology. Acquia is growing in an incredibly fast-paced, dynamic sector and we realize our mission is to help our customers understand how to think ahead to ever more innovation and change. Simplifying our overall messaging and defining ourselves around the Acquia Platform is a significant first step.

Of course, none of this success would be possible without the support of our customers, partners, the Drupal community, the Acquia team, and our many friends. Thank you for your support in 2014, and I look forward to working with you to find out what 2015 will bring!

Categories: Drupal

Dries Buytaert: Acquia retrospective 2014

Planet Drupal - 9 January 2015 - 12:01pm

As is now a tradition for me, here is my annual Acquia retrospective, where I look back at 2014 and share what's on my mind as we start the new year. I take the time to write these retrospectives not only for you dear reader, but also for myself, because I want to keep a record of the changes we've gone through as a company and how my personal thinking is evolving from year to year. But I also write them for you, because you might be able to learn from my experiences or from analyzing the information provided. If you would like to, you can read my previous retrospectives: 2009, 2010, 2011, 2012 and 2013.

For Acquia, 2014 was another incredible year, one where we beat our wildest expectations. We crossed the major milestone of $100 USD million in annual revenue, the majority of which is recurring subscription revenue. It is hard to believe that 2014 was only our sixth full year as a revenue-generating business.

We've seen the most growth from our enterprise customers, but our number of small and medium size customers has grown too. We helped launch and host some incredible sites last year: from weather.com (a top 20 site) to the Emmys. Our efforts in Europe and Asia-Pacific are paying off; our EMEA business grew substantially, and the Australian government decided to switch the entire government to Drupal and the Acquia Platform.

We hired 233 people in 2014 and ended the year with 575 employees. About 25% of our employees work from home. The other 75% work from offices around the world; Burlington MA (US), Portland OR (US), Washington DC (US), Paris (France), Reading (United Kingdom), Ghent (Belgium), Singapore, Brisbane (Australia) and Sydney (Australia). About 75% of our employees are based in the United States. Despite our fast growth rate in staff, recruiting remains a key challenge; it's hard to hire as fast as we do and maintain the high bar we've set for ourselves in terms of talent and commitment.

We raised venture funding twice in 2014: a $50MM series F round led by New Enterprise Associates (NEA) followed by Amazon investing an undisclosed amount of money in our business. It's not like Tom Erickson and I enjoy raising money, but we have been able to secure the financing that is necessary for a fast-growth, enterprise subscription business like Acquia. Building and expanding a sales and marketing team is notoriously difficult and requires big investments. At the same time, we're building and supporting the development of multiple products in parallel. Most companies only build one product. We're going after a big dream to become the preferred platform for what has been called the "pivot point of many enterprise tech stacks" -- the technologies that permit organizations to deliver on the promises of exceptional digital customer experiences from an agile, open, resilient platform. We're going after a big dream and are competing against behemoths. We can't show up to a gunfight with a knife, so to speak.

Building a digital platform for the enterprise

Digital has changed everything, and more and more organizations need or want to transform into digital-first businesses to stay in step with the preferences of their customers. Furthermore, technology innovations keep occurring at an ever faster and more disruptive pace. No organization is immune to the forces of digital disruption. At Acquia, we help our customers with this wave of digital transformation by providing a complete technology platform and the support and security necessary to maintain it. The Acquia Platform consists of tools and support for building, delivery and managing dynamic digital experiences. It includes Acquia Cloud, which helps developers deliver complex applications at scale, and Acquia Lift, our digital engagement services for bringing greater context to highly personalized experiences. Let me give you an update on each of the major components.

Drupal tools and support

Drupal gives organizations the ability to deliver a unified digital experience that includes mobile delivery, social and commerce. Great inefficiencies exist in most organizations that use a variety of different, disconnected systems to achieve those three essentials. They are tired of having to tie things together; content is important, social is important, commerce is important but connecting all these systems seamlessly and integrating them with preferred applications and legacy systems leads to massive inefficiencies. Companies want to do things well, and more often than not, Drupal allows them to do it better, more nimbly and in a far more integrated framework.

In 2010, we laid out our product vision and predicted more and more organizations would start to standardize on Drupal. Running 20 different content management systems on 20 different technology stacks is both an expensive and unnecessary burden. We've seen more and more large organizations re-platform most of their sites to Drupal and the Acquia Platform. They realize they don't need multiple content management systems for different sites. Great examples are Warner Music and Interscope Records, who have hundreds of sites on Drupal across the organization, resulting in significant cost savings and efficiency improvements. The success of our Acquia Cloud Site Factory solution has been gratifying to witness. According to a research study by Forrester Consulting, which we released late last year, ACSF is delivering a 944% return on investment to its adopters.

After many years of discussion and debate in the Drupal community, we launched the Acquia Certification Program in March 2014. So far, 546 Drupal developers from more than 45 countries have earned certification. The exams focus on real world experience, and the predominant comments we've heard this past year are that the exams are tough but fair. Acquia delivered six times the amount of training in 2014 compared to the previous year, and demand shows no sign of slowing.

Last, but definitely not least, is Drupal 8. We contributed significantly to Drupal 8 and helped it to achieve beta status; of the 513 critical Drupal 8 bugs fixed in 2014, Acquia's Office of the CTO helped fix 282 of them. We also funded work on the Drupal Module Upgrader to automate much of the work required to port modules from Drupal 7 to Drupal 8.

Acquia Cloud

But Drupal alone isn't enough for organizations to succeed in this digital-first world. In addition to adopting Drupal, the cloud continues to enable organizations to save time and money on infrastructure management so they can focus on managing websites more efficiently and bringing them to market faster. Acquia customers such as GRAMMY.com have come to depend on the Acquia Cloud to provide them with the kind of rugged, secure scale that ensures when the world's attention is focused on their sites, they will thrive. On a monthly basis, we're now serving more than 33 billion hits, almost 5 billion pageviews, 9 petabytes of data transferred, and logging 13 billion Drupal watchdog log lines. We added many new features to Acquia Cloud in 2014, including log streaming, self-service diagnosis tools, support for teams and permissions, two-factor authentication, new dashboards, improved security with support for Virtual Private Networks (VPNs), an API for Acquia Cloud, and more.

Acquia Lift

As powerful as the Drupal/Acquia Cloud combination may be, our customers demand far more from their digital properties, focusing more and more on optimizing them to fully deliver the best possible experience to each individual user. Great digital experiences have always been personal; today they have to become contextual, intuitively knowing each user and dynamically responding to each user's personal preference from device to location to history with the organization. After two years of development and the acquisition of TruCentric, we launched Acquia Lift in 2014.

It's surprising how many organizations aren't implementing any form of personalization today. Even the most basic level of user segmentation and targeting allows organizations to better serve their visitors and can translate into significant growth and competitive differentiation. Advanced organizations have a single, well-integrated view of the customer to optimize both the experience and the lifetime value of that customer, in a consistent fashion across all of their digital touchpoints. Personalization not only leads to better business results, customers have come to expect it and if they don't find it, they'll go elsewhere to get it. Acquia Lift enables organizations to leverage data from multiple sources in order to serve people with relevant content and commerce based on intent, locations and interests. I believe that Acquia Lift has tremendous opportunity and that it will grow to be a significant business in and of itself.

While our key areas of investment in 2014 were Acquia Cloud and Acquia Lift, we did a lot more. Our Mollom service blocked more than 7.8 billion spam messages with an error rate of only 0.01%. We continue to invest in commerce; we helped launch the new Puma website leveraging our Demandware connector and continue to invest and focus on the integration of content and commerce. Overall, the design and user experience of our products has improved a lot, but it is still an area for us to work on. Expect us to focus more heavily on user experience in 2015.

The results of all our efforts around the launch of the Acquia Platform have not gone unnoticed. In October, Acquia was identified as a Leader in the 2014 Gartner Magic Quadrant for Web Content Management.

The wind is blowing in the right direction

I'm very optimistic about Acquia's future in 2015. I believe we've steered the company to be positioned at the right place at the right time. As more organizations are shifting to becoming digital-first businesses they want to build digital experiences that are more pervasive, more contextual, more targeted, more integrated, and last but not least, more secure.

The consolidation from many individual point solutions to one platform is gaining momentum, although re-platforming is usually a long process. Organizations want the unified or integrated experience that Drupal has to offer, as well as the flexibility of Open Source. It is still time consuming and challenging to create quality content, and I believe there is plenty of opportunity for us and our partners to help with that going forward.

Without a doubt, organizations want to better understand their customers and use data-driven decision to drive growth. Data is becoming the new product. The opportunity this creates in commerce is massive.

Cloud computing and Software as a Service (SaaS) continues to be on the rise. Cloud is top of mind and the transition away from on-premise solutions is accelerating even as the arguments around security and privacy issues in the cloud continue to be raised. While there is a certain amount of emotion, and sometimes politics, people are beginning to realize that the cloud is usually more secure and more robust against cyber-attacks than traditional on-premise systems.

The promise of Drupal 8, arguably the most significant advance in the evolution of the Drupal software, has me very excited. It is shaping up to be a great release, and I'm confident it will further secure Drupal's reputation among developers, designers, agencies and site managers as the most flexible, powerful content management solution available.

All of this is not to say 2015 will be easy. This is an incredibly exciting and fast-changing space in the world of technology. Acquia is growing in an incredibly fast-paced, dynamic sector and we realize our mission is to help our customers understand how to think ahead to ever more innovation and change. Simplifying our overall messaging and defining ourselves around the Acquia Platform is a significant first step.

Of course, none of this success would be possible without the support of our customers, partners, the Drupal community, the Acquia team, and our many friends. Thank you for your support in 2014, and I look forward to working with you to find out what 2015 will bring!

Categories: Drupal

Lullabot: Manage Your Drupal.Org Projects and Sprints with a Kanban Board

Planet Drupal - 9 January 2015 - 11:30am

I'm not very good with managing my tasks through a simple list—despite my best efforts, the list always seems to keep growing. I prefer to use a Kanban Board, a popular method of arranging lists that highlights the current status of each task. It's nice to see that I actually do get things done, after all!

Categories: Drupal

Blink Reaction: Part Five: Cleanup and Troubleshooting

Planet Drupal - 9 January 2015 - 8:37am

Cleaning up is one of the advantages of working with VMs over a bare metal install. Since everything is in the disk image files, we only need to delete the VM. Vagrant provides two commands for this purpose:

Stopping and Deleting the VM

Change to the directory containing the Vagrantfile, and then stop the VM:

vagrant halt

To delete the VM permanently:

vagrant destroy

That’s it!

Categories: Drupal

Code Karate: Drupal Commerce Course

Planet Drupal - 9 January 2015 - 7:01am
Categories: Drupal

Drupal Commerce: Managing D8 module dependencies with the new Composer Manager

Planet Drupal - 9 January 2015 - 6:06am

It's not uncommon for a Drupal module to need an external library in order to function.
Historically, modules such as oauth2_server have done this by asking the end-user to download the library manually and extract it into sites/all/libraries. A hook_requirements() implementation would nag the end-user until the library is found.
Nowadays, all libraries are registered on Packagist and expect to be installed via Composer, which also resolves and downloads their dependencies. Thanks to Composer and modern PHP, the number and usage of libraries has skyrocketed, with Packagist recently counting its 500 millionth package install. Because of this thriving ecosystem, it is now more desirable than ever for modules to depend on libraries instead of reinventing the wheel. Furthermore, it is desirable for modules to release their core logic as libraries, bringing in additional users and contributors from the wider ecosystem.

So, how does Composer work, and why do we need Composer Manager?

Read on for more details...

Categories: Drupal

LimoenGroen company blog: Automatically generated subdomains in Drupal

Planet Drupal - 9 January 2015 - 5:21am

A few weeks ago the new version of MijnStadMijnDorp.nl was launched to the public. Built by LimoenGroen, it offers a rich media platform where historical societies based in the Dutch province of Overijssel showcase their collections.

One of the project challenges was to emphasize the personalized look and feel of each society within the global site structure; every society has its own homepage with an introduction and a collage of curated content. Subdomains (e.g. subdomain.example.com) helped us achieve this. In this article we discuss what we encountered.

The Subdomain module

The core functionality was established using the contrib module Subdomain. In a nutshell, the Subdomain module can be setup to use a unique subdomain for page callbacks related to a specific user, taxonomy term, organic group or content type.

In the case of MijnStadMijnDorp.nl, we used the organic group mode, as each society is an organic group and needed a subdomain. All content of a society lives within its group and has the subdomain applied to it. By default, the name of the subdomain is either based on the name of the organic group or on end user input. We modified this behavior so the subdomain is set to the name of the organic group (society) by default, but can be manually overridden by users with administrative privileges. This comes in handy for societies with long names where an abbreviated subdomain is more suitable.

Automatically set subdomain after node creation:/** * Implements hook_node_insert(). * * Automatically set subdomain after node creation. */ function my_module_node_insert($node) { switch ($node->type) { case 'society': $node->subdomain = subdomain()->clean($node->title, TRUE); subdomain_url_outbound_cache_clear(); // Create unique subdomain. subdomain()->save_record($node->nid, $node->title, TRUE); break; } } Dnsmasq

During local development, testing dynamically generated subdomains can be cumbersome when using a local hosts file, because wildcards cannot be used. Dnsmasq to the rescue! It is a DNS resolver running as a daemon on a local development machine. Dnsmasq was configured to resolve the DNS zone used for local development (e.g. mijnstadmijndorp.dev) to 127.0.0.1. This also resolves any child zones (subdomains) to localhost. Since we use Apache locally, we had ServerAlias *.mijnstadmijndorp.dev added in the virtual host configuration.

Preparations for deployment

Using dynamically generated subdomains in a production environment typically involves configuring the webserver and the DNS zone for the root domain of the website.

For Apache, adding ServerAlias *.mijnstadmijndorp.nl to the virtual host configuration was sufficient. Similar directives were setup for the other servers in our DTAP-environment, with applicable hostnames.

When using HTTPS (which is always a good idea), serving content from dynamically generated subdomains means you need a wildcard certificate. In our case, a public key certificate with *.mijnstadmijndorp.nl as subject name was used.

For DNS, a wildcard (*.mijnstadmijndorp.nl) A-record was created.

Caveats and considerations

The Subdomain module schema has a textfield for the subdomain value, with a maximum length of 255. RFC 1035 states that the maximum length of a DNS label is 63 characters, and the accumulated length of all labels within a FQDN should not exceed 255 characters. The Subdomain module currently does not check the length of the subdomain DNS label or the accumulated length of the FQDN. This can result in URI’s that do not resolve. We submitted a patch for review that fixes this issue.

In terms of SEO, using subdomains should not negatively affect the ranking of a website as a whole. Google has stated they do not treat subdirectories different from subdomains (source), and as such there should be no penalties or split page rank amongst the subdomains. However, discussions on SEO forums indicate ranking was improved for some users when switching from separated subdomains to one shared hostname with subdirectories (source).

Categories: Drupal

groups.drupal.org frontpage posts: Curso online de Experto en Drupal 7. Pruébalo gratis!!

Planet Drupal - 9 January 2015 - 4:42am

A qué esperas para unirte al curso más completo de Drupal 7? Si tienes dudas, ahora puedes probarlo gratis durante una semana!

Y si quieres continuar con el curso completo, tendrás un 10% de descuento aplicando el cupón CURSOS10.

El curso de Experto en Drupal 7 incluye Site Building y Development y se compone de 60 unidades en 3 niveles: Inicial, Intermedio y Avanzado. Después de completar los tres módulos tendrás que desarrollar un Proyecto Final. La duración total del curso es de 7 meses con 420 horas certificadas, pero puedes acortar este tiempo con mayor esfuerzo y dedicación.

Aunque esta acción formativa requiere un esfuerzo importante, ahorrarás mucho tiempo en comparación con estudiar Drupal por tu cuenta, sin dejarte nada en el camino y ganando muy pronto en solvencia para afrontar cualquier proyecto en Drupal.

Ten cuidado, si lo pruebas querrás continuar!

http://www.forcontu.com/experto-drupal-7

Categories: Drupal

Amazee Labs: Zurich joins the Drupal Global Sprint Weekend 2015

Planet Drupal - 9 January 2015 - 4:35am
Zurich joins the Drupal Global Sprint Weekend 2015

On the weekend of 17. & 18.01.2015, dozens of Drupal contribution sprints will be taking place across the globe. Amazee Labs invites all of you interested in learning, hacking and improving Drupal to join us for two days of pure sprinting at our offices in Zurich.

  • Date: 17. & 18.01.2015
  • Time: 9:00 a.m. - open end
  • Location: Amazee Labs, Förrlibuckstrasse 30, 8005 Zürich
  • Food & Drink: provided
  • Registration: RSVP here

What can I expect from sprinting with you?

  • Get up to speed with the Drupal 8 and dive into coding new patterns
  • See how far you can get with the much improved site building tools in Drupal 8
  • Submit your first Drupal patch as a contributor
  • Help out in a Drupal core initiative
  • Discuss hard problems face-to-face with other experienced Drupalistas
  • A sprint place with enough food and drinks to get things done
  • Be your own client and have fun :)

Who can contribute?

Coders, designers, front-end developers, designers, project managers, user experience experts, clients, basically anyone who wants to improve Drupal, are welcome to the sprints.

Regardless of your knowledge level, if you have built a site in Drupal, you can contribute and are warmly welcomed.

What can I work on?

We will split into groups and work on Drupal core issues. Bring your laptop. For new folks: you can get a head start also by making an account on Drupal.org, setting up your dev environment (https://www.drupal.org/dev-env) and developers can install git before coming and git clone Drupal 8 core.

A great way to get started with contributing to Drupal core is to get involved with an initiative. We'll have local folks present with knowledge about Multilingual, Rules, CMI etc. Also check out the Drupal core initiatives and topics!

The following sprint topics have been proposed already:

Registration: RSVP here

Categories: Drupal

Drupal core announcements: Changes to Drupal 8 that affect admin theme maintainers

Planet Drupal - 9 January 2015 - 4:01am

Happy Friday! I maintain the admin theme in Drupal 8 core: Seven. There have been many changes to Seven in Drupal 8 that affect the relationship between admin themes and modules, and how the admin UI is generated.

I've always thought that the strategy we've put in place are going to have a positive impact on maintainers of contrib admin themes, but I've never sought out feedback directly. I am now!

Object oriented CSS

We now have CSS standards in Drupal 8. All CSS in core is being rewritten and restructured inline with those standards. They are heavily influencds by the principles of OOCSS, SMACSS, BEM, and the writings of Nicolas Gallagher.

The Seven theme, with the introduction and evolution of the Seven Style Guide, embraced these principles from design down to implementation. As all modules with administrative UIs are tested against Seven, the architecture and design of Seven influences all contrib admin themes.

Reusable admin CSS components

Taking influence from frontend frameworks such as Bootstrap, Seven's design is now split into components, instead of per page overrides and designs.

This creates a 'visual api' of sorts that modules hook into and reuse to create the admin UI they need without having to write any CSS. It also ensures a greater consistency throughout Drupal's UX.

One common example are buttons, the classes .button, .button--primary, .button--danger, .buttoner--small can be applied to any element.

Another is the heading classes. Classes like .heading-a, .heading-b, heading-c</code mimic the hierarchy of the <code>h1, h2, h3 elements. You can pick the font sizes that look right for your page without affecting accessibility or overriding it in CSS.

We also have reusable classes to control layout. Using classes like .layout-column.half, .layout-column.quarter, .layout-column.three-quarter will layout your page for you. Classes such as .leader, .leader-double, .leader-triple will add spacing above an element that matches the base leading of Seven, while .trailer, .trailer-double, .trailer-triple will add spacing below.

Another low level component are the color classes, .color-success, .color-warning, .color-error allow you to reuse colors defined in the Seven styleguide, without a tool like Sass or CSS variables.

Less admin CSS in modules

With a full library of reusable CSS components, contrib modules will need to write less CSS. From my point of view, this is a big win for contrib admin theme maintainers, who have to write a lot of custom CSS to override custom CSS in some complex modules, and it's harder to tell if modules are broken because of the changes in the admin theme.

I'm hoping that admin theme maintainers will be able to override just the reusable components and have better coverage of core and contrib modules.

Ongoing work

We are still working on converting a lot of custom CSS into reusable components, and will continue to build the library of components after Drupal 8s release.

Feedback please!

Admin theme maintainers, are there any problems or pitfalls you see with this approach? I would like to know.

Categories: Drupal

Inspired by Ant-Man – Honey I Shrunk The PCs

Gnome Stew - 8 January 2015 - 11:49pm

You’ve probably seen the recent Ant-Man teaser that released at a miniature size.

 

 

It was followed by a full sized trailer that showed off more of the overlooked superhero. Seeing the trailers recently reminded me of one experience on the micro-scale that was really fun and has always stuck with me – playing Unreal Tournament’s giant maps where your character was at an incredibly small size in a real world setting.

 

These maps were incredibly fun because they flipped the paradigm on its head and tapped into that place in our brains where we were 8 year olds playing with toys. The vast epic landscapes of the game were vast epic landscapes that you lived in everyday, they just weren’t so epic at real size.

Run A Session At Micro Size

This idea can be used to great effect in tabletop RPGs. When you need to do something interesting or are looking for a filler session, run a game where the characters are shrunk down and have to interact with the world at Micro Size. There are a lot of great things that can come from running a game where the PCs are shrunk down.

  • It’s unique and is new ground your game has not likely explored yet.
  • It gives you a whole new set of challenges to throw at your players.
  • Your minis are now actual size and the whole room is the map
  • It is a great escape for your BBEG. Chases are nearly impossible when 10 minutes of your running covers about 10 seconds of the villains movement.

So, what do you need to do a session at a micro scale? Not a lot, but there are a few things to consider before jumping into the micro world.

Determine a Reason for Micro Sizing

First off, figure out a reason and set of parameters for the micro-sizing. In reality, a person who was shrunk down to a miniature size would probably be unable to process oxygen as efficiently because their lungs don’t work the same. This is a game though, and that isn’t what is really important. What is important is how and why the characters get shrunk down and what that means. In fantasy games Magic could easily shrink the PCs, in superhero games you’ve got the hand wave of superpowers or mad science, similar to what you would have in a fantastic sci-fi game. With a base reason down for why the shrinking occurs, figure out what other parameters go along with it. Is climbing the chair to get up to the table going to be like summiting everest, or is their leeway because it is a game and at their micro size there are more handholds at that scale? If it is magic, is their some property that allows for them to retain some or all of their strength or agility? (This is a density/mass question that has been debated fiercely on some forums – because we are nerds.) Do you want it so that the PCs have a bit more freedom in moving, or do you want a shrinking scenario where everything becomes harder? These sorts of questions are going to be asked by your players, so it is best to have some rough answers thought out beforehand. This lets you create a solid and unique play experience while also preparing some interesting challenges.

Figure Out The Challenges before hand

You will want to follow up determining the base reasoning and mock-physics behind the shrinking with figuring out the challenges you want to throw at your players. Operating on a micro scale means a whole new set of things to deal with. Things like:

  • Moving along the ground much slower comparatively.
  • Can the players get higher in their new landscape, or is it a pain?
  • What kind of new monsters will they fight? What CR is a rat now that it is the size of an elephant?
  • Is a human voice or music on a radio booming or normal sounding?
  • Can you see as far as you could normally? Is the other side of the room blurry like the horizon?
  • Does the voice activation on the ship still work or are your voices too squeeky? Can you get the ship to launch on auto pilot, only to find yourself unable to manually steer away from a firefight?

Figure Out Ways Around The Challenges

Knowing your challenges and playing them out is great, but the real fun of a micro sized game as a player is staring around the room and imagining how you would move on the micro scale. Sure, your grappling hook that was 100 feet probably wouldn’t really reach the top of the mantle, but…. it’s really fun to imagine that. Know when to make the players work for it and know when to just let it be or have a work around handy. For any challenge you make, have at least one counter in mind. If the players come up with something better, go with it, or let them figure out how to get around it. You should also prime them with the idea that some things wouldn’t work the same. For instance, magic. A first level mage casts a spell that can lift 5 pounds of material… does this scale or can she suddenly move the entire party with her low level spell? Imagine how useful a power that lets a player create an explosion within 25 feet becomes, even if the explosion is small. Part of this is the fun conjectural experiment of imagining someone shrunk down to size, but part of it is also the fun conjectural experiment of discovering a whole new set of abilities because powers and abilities don’t translate exactly.

Figure Out The Undo Button

Finally, unless you want your game to be a remake of Land Of The Giants, it is a good idea to know how to undo the shrink factor. Maybe it is a duration on the spell or power, or maybe the new quest is figuring out how to undo it. What happens to all that mass? For one game system, I wrote a shrink spell that turned all of the mass into a clay substance. The character shrunk had to touch the clay to reabsorb it. I then ran a quest where one PC was shrunk down to about 1/2 his size, the clay from the spell was then sent to a pottery factory and spread throughout the world. He had to track it down, bit by bit to regain his size. That is a little extreme for most games, especially short paradigm flipping sessions, so have a firm exit strategy for the shrinking. If it was an artifact, touching the artifact again or finding the artifact that reverses the effect are logical solutions that the player characters would know if they considered it. Make sure the exit strategy is accessible to the players, as it makes it easier to have a defined path for the adventure.

So, would you find room in your game world or campaign for a micro session? What other flip the paradigm types of sessions have you run? What are some of the coolest challenges and scenarios you can imagine to being shrunk down? How do you think some spells or powers could work differently in micro scale? Share your ideas in the comments, it will help other GMs who might want to run this type of session.



Categories: Game Theory & Design

Appnovation Technologies: How to add JS and CSS assets to a Drupal 8 theme

Planet Drupal - 8 January 2015 - 11:21pm

In one of my previous posts I wrote about creating a Drupal 8 theme and declaring assets (JS and CSS) associated with it.

var switchTo5x = false;stLight.options({"publisher":"dr-75626d0b-d9b4-2fdb-6d29-1a20f61d683"});
Categories: Drupal

User Relation

New Drupal Modules - 8 January 2015 - 11:02pm

Adds support for user relationships using the Relation module.

Categories: Drupal

Prediction in the Gaming Industry, Part 1: All About Prediction - by Dmitri Williams

Gamasutra.com Blogs - 8 January 2015 - 10:32pm
This article is the first in a three-part series on prediction and using predictive metrics in the gaming industry.
Categories: Game Theory & Design

2015: The Year We Get Loading Screen Mini-Games Back - by David Hoppe

Gamasutra.com Blogs - 8 January 2015 - 10:32pm
The loading screen mini-game, and Namco's patent expiring this year.
Categories: Game Theory & Design
Syndicate content


Google+
about seo