Subscribe to feed Planet Drupal - aggregated feeds in category Planet Drupal
Bijgewerkt: 3 uur 37 sec geleden <a href="/blog/use-of-drupal-in-product-companies">Use of Drupal in Product Companies</a>

wo, 2016/12/07 - 1:14pm
Drupal is seen as a framework for building solutions to the complex business problems. Product companies have been using Drupal for quite a while now for numerous use cases such as Intranet, Developers’ Discussion Forum, Corporate Blogging Platform etc.   E-commerce Vertical  Product websites whether selling physical products or virtual products are dependent on seamless shopping experience; this happens via seamless user experience in the site. Drupal commerce has significantly been used by both the small companies as well as the enterprises and it clearly delivers just the kind of digital shopping experience that these product companies intend to create. Moreover, ecommerce product companies are also using Drupal for optimizing their day to day operations with solutions such as PIM (Product Information Management) or a multichannel publishing platform, built in Drupal. Enterprises in ecommerce that are already using solutions such as Demandware, Magento or BigCommerce are sometimes integrated with Drupal system to manage all of their internal processes and operations.   Collaboration Platform for Developers Drupal is widely used by the hi-tech product companies to create a collaboration and discussion platform for their developers. Some of the very well-known tech companies have adopted Drupal for creating such a platform. Prominent ones are eBay Developers Programme, Twitter Developer Community, Intel Developer Zone, Nvidia Developer Community and many others. Many of the Drupal’s out of the box features such as Organic Groups, Forum features, Taxonomy along with the ability to integrate with the third party softwares makes it an ideal framework to build such a platform.   What makes Drupal a good fit for Product Companies? Drupal comes with an array of features and out of the box functionalities that make it an ideal fit for the requirements of the product companies.   Highly Scalable While delivering the world’s greatest digital experiences for the users it is also critical for the web platform to be able to handle the high traffic situations. Drupal has been trusted by the likes of, Grammy and Time Inc. to handle Traffic Spikes in the times of acute weather change or Grammy awards etc. Whether it is traffic spikes of constant high traffic, Drupal has the ability to scale such traffic situations and keep the show going.   Mobile First Drupal is out of the box responsive. Hence, it has the ability to create beautiful and seamless mobile experiences. Mobile web services such as REST are in core and hence Drupal has the ability to integrate with the mobile apps on the front end whilst managing the content, media, users etc. all at the backend. Now with Drupal 8, even the Admin interface is out of the box responsive. This gives the ability to carry out all admin related tasks easily via mobile.   Flexible Content Architecture Drupal gives the ability to create the right content architecture using the Admin Interface itself. What this means is that even the non-tech product or program managers can easily use Drupal to create the content architecture as needed. Drupal’s wide array of Display Tools such and Views ensure that the content appropriate for each context only is displayed. Drupal includes a variety of media types (images, video, pdfs, etc.) and content types, pretty much everything a product company may require to build a robust content platform. Customizable menus create a comfortable user experience, creating paths to content across multiple devices.   Integrate with the Digital Ecosystem Drupal has the ability to integrate with a wide variety of third party applications, business solutions and other digital marketing technology products too. Use of such disparate kind of software systems to create a robust digital ecosystem, now-a-days is a norm in the product companies. Drupal easily integrates with this ecosystem.   Conclusion Above discussed are just some of the many features that Drupal provides that make it a preferred framework among product companies to build their digital solutions. Moreover, with the advancements that Drupal 8 has brought along, we believe, Drupal’s adoption in product companies spread across numerous industries is just going to increase with time.  
Categorieën: <a href="/blog/excited-to-be-at-drupalcon-new-orleans-2016">Excited to be at DrupalCon New Orleans 2016</a>

wo, 2016/12/07 - 1:14pm
Apart from the conferences, music festivals, amazing food, sporting events, parties and after parties, here is the rundown of what DrupalCon New Orleans has in store for you:   
  • 130 sessions
  • 15 training opportunities
  • 13  educational  session tracks
  • 91 BOF meetings
  Inspirational keynotes and countless networking opportunities   Faichi has always been proactively supporting Drupal Community. This year we are sponsoring a Birds of Feather (BoF) room at DrupalCon New Orleans. BoFs are a great way for folks to get together and discuss interesting topics in an informal setting and hence getting a sense of  trends in the world of Drupal.   There are some great BoFs scheduled in Faichi sponsored room:   Day 1 Accessibility, Drupal 8 - Core, Contrib & JavaScript Frameworks Integrated Living Style Guides The Future of Drupal Marketing Tools Are you a smaller Drupal shop? Let's get together and share ideas some ideas!   Day 2 Managing Large-scale Drupal Projects Decoupled Blocks brainstorm session Drupal-Native Booking and Availability Management   Day 3 Hosting Drupal SaaS applications Migration -- D6 to D7 or D8 Integrating machine learning with Drupal   With such an amazing lineup of sessions at the Faichi BOF room, we look forward to witness the community synergy and new information being consumed at DrupalCon NOLA. We all are super excited to connect with fellow Drupalers and get inspired and contribute to the future of Drupal.  
Categorieën: Drupal 6: Are You Out of Time?

wo, 2016/12/07 - 1:35am
Do you still operate a Drupal 6 website? Are you getting questions from your management team, technical teams or even board of directors on pending upgrades? Are they afraid of the Drupal 6 "End of Life"? What should you do? What should you tell them? Read more to hear some brief thoughts on the big decision!

Drupal core announcements: Coding standards ratified changes and ongoing proposals

di, 2016/12/06 - 9:06pm

The TWG coding standards committee is announcing three coding standards changes for final discussion. These appear to have reached a point close enough to consensus for final completion. The process for proposing and ratifying changes is documented on the coding standards project page. A change to this process is being proposed to streamline the interaction between the coding standards body, Drupal Core, and the Coder project, please provide any feedback on that issue.

Announced for final discussion: Official coding standards updates now ratified: Formerly announced issues that need an issue summary update

These issues have a lot of support but need an update to formalize the proposal so that they can be ratified and applied.

- [Agree on a property naming pattern]( - [Coding standards for breaking function calls, function declarations, and language constructs across lines]( - [Add type hinting to function declaration coding standards](

These proposals will be re-evaluated during the next coding standards meeting currently scheduled for December 20th. At that point the discussion may be extended, or if clear consensus has been reached one or more policies may be dismissed or ratified and moved to the next step in the process.


Drupal Modules: The One Percent: Drupal Modules: The One Percent — Masonry Views (video tutorial)

di, 2016/12/06 - 1:43pm
Drupal Modules: The One Percent — Masonry Views (video tutorial) NonProfit Tue, 12/06/2016 - 06:43 Episode 10

Here is where we bring awareness to Drupal modules running on less than 1% of reporting sites. Today we'll consider Masonry Views, a module which will help cleanup the display of our Views grids.


valechatech: Switching from custom installation profile to lightning on existing drupal sites

di, 2016/12/06 - 1:38pm
Switching from custom installation profile to lightning on existing drupal sites naveenvalecha Tue, 12/06/2016 - 18:08
Categorieën: Animate Your Site in Drupal 8

di, 2016/12/06 - 12:59pm

Palantir:'s Guide to Digital Governance: Private Websites, Intranets and Portals

di, 2016/12/06 - 12:56am's Guide to Digital Governance: Private Websites, Intranets and Portals's Guide to Digital Governance brandt Mon, 12/05/2016 - 17:56 Scott DiPerna Dec 5, 2016

This is the eleventh installment of’s Guide to Digital Governance, a comprehensive guide intended to help get you started when developing a governance plan for your institution’s digital communications.

In this post we will cover...
  • Questions you should consider specifically related to private websites
  • Why you should think about whether your private site should be a part of your public site
  • Why it's important to serve the needs of site users

We want to make your project a success.

Let's Chat.

Most organizations these days have some form of private area for only staff, group members, constituents, partners, vendors, etc. These sites are sometimes guarded behind a firewall and a user authentication system, sometimes just user authentication, and sometimes simply hidden by obscurity. Most often, though, you can identify one of these types of sites because it requires a login and password and is not generally accessible by the public.

Most of the previous questions, regarding content, organization and design are relevant to internal Web properties as well, but here are a few questions you may want to ask yourself specifically with regard to private websites, intranets, and internal-facing portals:

  • Who owns each one? If they are shared responsibilities, what are the parts and who owns each part?
  • How are accounts distributed and access granted?
  • Who determines access and account creation?
  • What is the process for account creation?
  • What is the criteria for gaining access via an account?
  • Do user accounts have different roles with different permissions?
  • Who are the content editors and creators within the site?
  • How is the site edited and maintained?
  • Are there any workflows or approval processes for content?
  • What distinguishes content that is appropriate for external channels from content that is only appropriate for internal channels?
  • Who will be responsible for determining what is appropriate? And how will they enforce those rules?

Public vs Private

Another important consideration for private websites and intranets, especially if you are planning to build one or redevelop your public website, is whether or not an intranet (or a private website) should be a part of your public website. In other words, should the same system for administering and maintaining your public website be the same system as your intranet or private website?

On the surface, the simple answer may appear to be, “Of course! Wouldn’t that be the most simple and streamlined approach?” Once you dig into the requirements of what you need for your private site, and compare that with the purpose of your public site, you may determine otherwise.


The most common purpose for a public website is to communicate information about your organization to a range of audiences, many of whom are not currently part of your organization. In fact, the primary purpose of your public website, specifically, may be to attract those who are not part of your organization in order to convince them to become part of it. In short, your public website’s primary purpose is likely to be a marketing tool for expanding your message and growing your constituency (membership, clientele, user-base, however you think of them). There is not typically a lot of functional interaction that happens between user and website at this stage, aside from asking visitors to contact you, sign-up up for something, attend an event, purchase a product, or some other interaction that is typically managed by a relatively basic form.

In other words, the necessary functionality for a public, marketing website tends to be fairly light in terms of the weight of its programming logic and requirements.

Intranets and private websites tend to be a different animal. Being private, by definition, means they need to support accounts for users. Having a lot of users logging into a system presents a number of challenges and requirements that can become quite complex. A heavier set of tools are often required, adding more software to the system.

Given that users and authentication credentials are involved, often integrations with user databases or user management systems may be involved, and almost certainly, a higher level of security and encryption becomes necessary.

Usually, when you have a private site or intranet, the needs of users become more transactional than consumption marketing information. Once a user is a member, they no longer need to be sold on the organization; they need to “do” things through the website – use tools, access account information, transmit or receive private data, etc. All of these things require deeper levels of programming, security, and the infrastructure to support it – a lot more heft and complexity than what you need for your marketing website, which probably benefits most from being nimble and quick to deliver relevant content.

Perhaps most important, though, is the organization of information – and this is where many projects that aim to combine a public website with a private intranet get bogged down. Since the two sites address the needs of largely different audiences, the menuing and navigation in sites that aim to serve both public and private needs are often in conflict with themselves. 

Rarely do you want to show navigation, menuing, or content to the public which is meant only for private users. However, how do you then present the private content and way-finding to authenticated users without breaking a design that, in theory, looks appropriate for only the public content and navigation?

As you get into the details of accommodating both public and private needs on a website, what you often find is that you make odd compromises to things you ordinarily wouldn’t (like usability of the site), in order to make the two work together. In truth, given that the audiences for the two sites may have very different needs, and the websites need to serve very different purposes, it is often wise to separate the two, even if that means support of two separate systems. In the end, it is better to serve the needs of the users, such that they can be successful using your websites.


This post is part of a larger series of posts, which make up a Guide to Digital Governance Planning. The sections follow a specific order intended to help you start at a high-level of thinking and then focus on greater and greater levels of detail. The sections of the guide are as follows:

  1. Starting at the 10,000ft View – Define the digital ecosystem your governance planning will encompass.
  2. Properties and Platforms – Define all the sites, applications and tools that live in your digital ecosystem.
  3. Ownership – Consider who ultimately owns and is responsible for each site, application and tool.
  4. Intended Use – Establish the fundamental purpose for the use of each site, application and tool.
  5. Roles and Permissions – Define who should be able to do what in each system.
  6. Content – Understand how ownership and permissions should apply to content.
  7. Organization – Establish how the content in your digital properties should be organized and structured.
  8. URL Naming Conventions – Define how URL patterns should be structured in your websites.
  9. Design – Determine who owns and is responsible for the many aspects design plays in digital communications and properties.
  10. Personal Websites – Consider the relationship your organization should have with personal websites of members of your organization.
  11. Private Websites, Intranets and Portals – Determine the policies that should govern site which are not available to the public.
  12. Web-Based Applications – Consider use and ownership of web-based tools and applications.
  13. E-Commerce – Determine the role of e-commerce in your website.
  14. Broadcast Email – Establish guidelines for the use of broadcast email to constituents and customers.
  15. Social Media – Set standards for the establishment and use of social media tools within the organization.
  16. Digital Communications Governance – Keep the guidelines you create updated and relevant.

Appnovation Technologies: 4 Tips to be an Efficient Tester

ma, 2016/12/05 - 11:55pm

To err is human, and coders too, like us are humans and are bound to make mistakes while coding, especially if the needs of the project are complex and if they adhere to the true meaning of agile.


OpenConcept: Inline Form Errors - What They Are and Why they Matter

ma, 2016/12/05 - 8:01pm

This article was initially posted as a guest blog on The Digital Echidna Blog on December 2, 2016.

Lots of organizations are working hard to see that their IT is accessible to their visitors and staff. Reducing barriers for effective two-way communications is really important for businesses that want to engage fully with their community. Unfortunately, many organizations overlook the many challenges with online web forms.

Organizations who adopted Drupal 7 benefit from having semantic labels associated with their web forms automatically. This is a particular problem with custom built web-forms, but the Drupal community made an effort towards solid accessibility defaults and continues to do so.

Drupal 8 takes web forms further, adding WAI-ARIA to provide additional semantic markup around descriptive text. Drupal 8 is the first CMS to embrace the HTML5 details/summary elements. These elements allows Drupal 8 forms to use fieldsets for what they are intended and avoids the problem of nested fieldsets, which were inevitable in earlier versions of Drupal.

Adding other HTML5 tags to Drupal Core helps build more semantic sites. Users are encouraged to use tags with meaning which help screen-reader users as well as search engines.

The Accessibility Team wasn’t satisfied with this and realized that we needed to address Guideline 3.3 of WCAG 2.0 AA, which states that all users need to:

  • Be aware that an error has occurred and understand what is wrong
  • Be given suggestions for correction of an input error if it is possible
  • Be provided with safeguards to avoid serious consequences resulting from mistakes
  • Have their input checked for errors and be provided an opportunity to correct them.

These really don’t sound that difficult, but unfortunately they are. Brandon Bowersox-Johnson spearheaded this back in 2012 outlining what needed to happen.

This required many changes to Drupal’s Form API, which is used on almost every Drupal admin page and with all of its web forms. An issue to address this was started later that year in the Drupal issue queue and Inline form errors for accessibility and UX resulted in over 600 comments over four years.

It also got into Drupal Core, although not for very long. It became clear that there were a number of regressions which were major enough that Drupal 8 could not be released without their being fixed. Rather than continue to hold up the release, the community decided to roll this back into an Experimental Core module.

This was absolutely the right call for 8.0. More attention has gone into the many sub-issues and several of them have been fixed. Drupal Core needs to be stable and predictable. Several developers have been very active in trying to fix these issues. In no particular order I’d like to highlight just some of the folks who have contributed to addressing these issues: Pieter Frenssen, Tim Plunkett, Baris Wanschers, Daniël Smidt, and Scott Carpenter.

There has been a lot of effort from some really smart folks going into this very important issue. Unfortunately it isn’t enough. Inline Form Errors need to be enabled by default. Everyone benefits from this better UI. Right now only a small fraction of Drupal 8 sites have enabled this module, because it is an optional Experimental Module and there are serious warnings included with it.

This module is also slated to be removed from Core and brought in as a regular Contrib module. There are good reasons to do this, but it makes it less likely that this improved pattern will ever get into Core.

This is not a trivial request, but it is an important one. For all agencies who are legally required to meet WCAG 2.0 AA, this is an area where your site likely fails. Although there are workarounds that can be done for individual sites and specific modules, we really need a centralized solution for this.

Please consider investing time or money in addressing this outstanding Drupal 8 meta issue and seeing that Drupal remains a leader in this space.

Topic: Primary Image: 

Drupal core announcements: Global virtual UX sprint day on December 9, 2016

ma, 2016/12/05 - 5:22pm
Start:  2016-12-09 (All day) Europe/Amsterdam Organizers:  yoroy Event type:  Sprint

On Friday, December 9 we are organizing a global virtual Drupal UX sprint. As always, many different features and projects are currently worked on. We'll use this day to work on issues that need UX input or feedback.

What will happen that day?

Join the #ux channel on (get an invite automatically at to participate all day.

  • UX mentors will be available to help onboard designers who want to contribute
  • We'll pair designers and devs (as available) to work on actionable tasks
  • Planning to do some ad hoc usability testing
  • An introduction to the main strategic initiatives and their UX components will be provided
Join the team

You can join us even after the global UX sprint. We have meetings every Tuesday at 9pm CEST and every Wednesday at 9am CEST on the #ux Slack channel at (get an invite automatically at Bring your issues there to discuss! CEST is the timezone observed in Amsterdam.


Drupal Modules: The One Percent: Drupal Modules: The One Percent — Markup (video tutorial)

ma, 2016/12/05 - 4:56pm
Drupal Modules: The One Percent — Markup (video tutorial) NonProfit Mon, 12/05/2016 - 09:56 Episode 9

Here is where we bring awareness to Drupal modules running on less than 1% of reporting sites. Today we'll consider Markup, a module which allows you to insert additional markup on the node/edit form just for content authors.


drunomics: Drupal IronCamp Prague 2016

ma, 2016/12/05 - 12:46pm

The first Drupal IronCamp took place in the beautiful capital of the Czech Republic in Prague at the end of November 2016. More than 200 attendees from 27 countries took part in four days of sprints and two days of sessions.

In such a relatively small group of people I could get in touch with everyone I liked to, keynote speakers, CEOs, friends and other drupalists.

So here is my summary of the sessions I have attended and which I found of interest.

KEYNOTE - Michael Schmid (@Schnitzel): The Future of Drupal

Michael showed us what people had in mind at the beginning of the 20th century when they wanted to predict the future now. It was both interesting and predictalbe, but also showed us that we still have not reached everything those people had in mind. The focus of this keynote was on Personalisation, Decoupled, Microservices and Containers - four fields, in which Drupal is already prepared for the future but not yet fully developed.

  • Personalisation: Websites won't be looking the same anymore. For disabled persons or based on a user's preferences websites will display only partial content or different content. This results in complex testing scenarios.
  • Decoupled: Drupal already consists of third party components, like Symfony or Twig. Also, Drupal already works great with decoupled frontends and technologies like node.js, React and other javaScript frameworks.
  • Microservices: Split up larger tasks into smaller ones, but keep an eye on coding standards and used programming languages and libraries.
  • Containers: A consistent website environment for development, testing and live will be achieved with the use of docker containers.


Fabian Bircher (@fabianbircher): Configuration Management: Theory and Practice

Fabian had one of the most interresting talks of this camp, which resulted in many discussions and talks in person with Fabian Bircher, Wolfgang Ziegler (@the_real_fago) and me (@KnudFrank).

The core theme of this presentation was the introduction of a new Drupal 8 module Configuration Split, where you can easily use Drupal 8s configuration managemen and split configurations for the use of different environments or different use cases.

[Fabian' blog post and slides] [Module: Configuration Split]

KEYNOTE - Larry Garfield (@Crell): Software Management Lessons from the 1960s

Has project management, described in "The Mythical Man Month" by Frederick P. Brooks Jr. in 1975 and 1995 changed in today's world? Most of the thesis described by the pioneers of modern computer architects and project management are still true. Larry and the audience had to admit this with no regret, but with relief. So project and software management has a steady and solid fundament to build upon and to rely on. This is good for companies working in collaboration with other companies and especially for the open source community to work together in such a large project as Drupal.


Théodore Biadala (@nod_), Mathieu Spillebeen (@MathieuSpil): Offline-Drupal

Comparing the approaches of Google's AMP, Facebook's instant articles, Appcache and Serviceworkers with real-world examples. Some techniques have limitations in browser support. Serviceworkers seems to be the most promising technology for caching websites in the browser, but unfortunately this still lacks support from Apple Safari. 
What's interesting about those "Progressive web apps" is that they do not necessarily require a front-end developed in Javascript. There is even a Drupal module: Progressive Web App.


KEYNOTE - Janez Urevc (@slashrsm): Ask Not What the Community Can Do for You, Ask What You Can Do for the Community

Only 0.5% of the users of Drupal contribute to the community. In this keynote Janez engaged the listeners to contribute to the community as well. He also showed the pros and cons of free software and propriety software and the processes in development with too many discussions and too few releases and too few contributers and missing functionalities. Engagement of developers is the core key for a community driven development.

Tamás Hajas (@eccegostudio): Short Twig recipes for Drupalers

Basics and advanced examples of Twig templates, inheritance, embedding, including and other useful recipes around Twig. An interesting talk but sadly a small crowd.


Wolfgang Ziegler: Efficient development workflows with Composer

Wolfgang had quite a big audience and lots of talk after the session. It seems that many developers have not worked so intensly with composer yet. But  this session provided an overview of possible workflows and showed practical solutions for building and deploying composer-managed projects. Wolfgang shared his experiences with handling Drupal projects and focued in his talk on approaches that can be shared across projects and team members.



A beautiful city but cloudy weather. Nevertheless the christmas market at night was shiny and also the after-parties had some surprises like the Cinema Zapping on Friday or the secret visit to Unijazz on Saturday. In two years the event will be back in Belgrad and I'm sure to be there too.

Categorieën: Blog: AGILEDROP: Drupal Camps in Middle America

ma, 2016/12/05 - 11:09am
As promised in one of our previous blog posts, the area between North and South America will not be forgotten. Therefore we present you Drupal Camps in Middle America. We already guided you through Drupal Camps, which were organized in Africa, Asia, North America, Europe and South America. Since our expectations were so wrong last time, we'll say that we expect Middle America to be ranked between South America and Africa in our world tour ranking table, which measures the quantity of organized Drupal Camps. Let's clear up first the geographic part of view. Term Middle America can also be… READ MORE