Planet Drupal

Syndicate content
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 8 hours 41 min ago

ADCI Solutions: OOP in Drupal 8 and how to use it to create a custom module

Fri, 09/29/2017 - 11:44

Drupal newbie? Or maybe you are a mature developer that’s in charge of training the youth? Then keep on reading!

The following article was written based on the experience of our junior developer Sophia. In a short term she had to learn the Drupal 8 specifics and be able to write custom modules in Drupal 8.

We’re going to examine the main OOP features that were implemented in Drupal 8 and create a module. Code samples are included.

 

Check this tutorial on writing a module in Drupal 8

 

 

Promet Source: Picture Module: Building Responsive Images in Drupal 7

Fri, 09/29/2017 - 08:30
In 2017, 77% of Americans own a smartphone, a phenomenal increase from just 35% in 2011 (source: Pew Research Center Mobile Fact Sheet). And we are not just talking about a single screen size here! There are a multitude of screen sizes to consider from different versions of iPhones, android. And outside of smartphones, you probably want to consider iPads, tablets, desktops, tvs, to name a few.

Drupal Modules: The One Percent: Drupal Modules: The One Percent — Linked Field (video tutorial)

Fri, 09/29/2017 - 05:17
Drupal Modules: The One Percent — Linked Field (video tutorial) NonProfit Thu, 09/28/2017 - 22:17 Episode 37

Here is where we seek to bring awareness to Drupal modules running on less than 1% of reporting sites. Today we'll consider Linked Field, a module which will allow you to easily wrap a link around another field.

Bay Area Drupal Camp: Session Schedule Posted, Training Classes Open for Registration!

Fri, 09/29/2017 - 03:05
Session Schedule Posted, Training Classes Open for Registration! Anne Thu, 09/28/2017 - 6:05pm Sessions Lineup Now Posted!

Ready yourselves, fellow adventurers -- this year’s session and speaker lineup have been revealed! There will be sessions spanning the worlds of development, design, strategy, project management, technology communities and everything in between.

A hearty thank you to all the valiant souls who submitted over 187 session proposals, your contributions, year after year, are what make BADCamp excellent. And for those whose hearts still burn to speak, there will be BoF opportunities throughout the event.

Drupal Training Classes

Are you prepared to gain mastery of your Drupal Skills? BADCamp has two full days of Drupal Training offered from some of the most talented leaders in the Drupal community.

Join the masters on Wednesday and Thursday while they unfold the magic. This year BADCamp offers skills training in DevOps, theming, module development, content strategy, and much more!

BADCamp has historically provided a completely free training thanks to the overwhelming generosity of our sponsors. However, this year we must charge a nominal fee of $25 to cover operating expenses as we are short on sponsorship funding. We sincerely apologize for this short notice. We needed to find ways at the last minute to break even.

This was a really difficult decision for the BADCamp organizers to make.

If you can't afford the $25 or its super complicated to get funding, please reach out to the BADCamp organizers via the contact form and we will help! We have already had generous attendees offer to donate extra seats in the classes.

Sign up for the BADCamp 2017 newsletter to stay in touch (bottom of Homepage).

Do you think BADCamp is awesome?

BADCamp is 100% volunteer run and 100% funded by our sponsors and the support of our local community. Thank you for your support.

Would you have been willing to pay for your ticket?  If so, then you can give back to the camp by purchasing an individual sponsorship at the level most comfortable for you. As our thanks, we will be handing out some awesome BADCamp swag as our thanks.

We need your help!

BADCamp is 100% volunteer driven and we need your hands! We need stout hearts to volunteer and help set up, tear down, give directions and so much more!  If you are able to help us, please sign up on our Volunteer Form.

Sponsors

A BIG thanks to our sponsors, especially Acquia & Pantheon, who have committed and supported us. Without them, this magical event wouldn’t be possible. Interested in sponsoring BADCamp? Contact matt@badcamp.net or anne@badcamp.net

Drupal Planet

Moshe Weitzman: Porting Commands to Drush 9

Fri, 09/29/2017 - 02:00

Drush 9 features a deep rewrite of our app, both user facing and internals. We created and open sourced AnnotatedCommand (example), OutputFormatters, and Config. We leveraged Symfony Console for our CLI fundamentals. For details on Drush9, see the video or slides from our Drupalcon Vienna presentation.

Jacob Rockowitz: What "About" the Webform module and the Drupal Community?

Thu, 09/28/2017 - 23:32

For the past year, I’ve been experimenting with how to integrate content within the user interface of the Webform module with a goal of improving the overall user experience. These experiments include adding inline videos, help documentation, a "How can we help you?" menu, and promotions. As I work towards a stable release, it’s time to document the lessons that I’ve learned from these experiments and decide on a final approach.

The Webform module makes it easy to build feature-rich, powerful, and flexible forms. Within this user interface, I’m aiming to provide users with user experience that helps them understand the Webform module and the Drupal community.

Providing help and documentation is a requirement for all software, including Open Source. The open source nature of Drupal led me to have three primary requirements:

  • Make users feel comfortable and supported when using the Webform module.
  • Promote the Drupal community to new and existing members. 
  • Raise awareness of my work. 

Making users comfortable

The most immediate way to make someone comfortable is to start a conversation - to talk to them, to ask questions and to listen. Early on, as part of the Webform modules development, I started producing video tutorials and demos to provide a show-n-tell experience. At the end of more recent videos, I promote myself using the question, "How can I help you?".

Overall, I’m happy with how the videos have been received by the Drupal community and I think this feature is going to remain AS-IS. Once the Webform module has a release candidate, I’m going to redo all the screencasts and apply some of...Read More

MTech, LLC: Running custom migrations via a Web UI

Thu, 09/28/2017 - 21:01
Running custom migrations via a Web UI

The Migrate API is almost stable and the majority of its basic functions and ways that folks interface with it are are to see the state of a migration, execute (import) a migration, or revert (rollback) a migration. However, until now, you had to all this via a command line interface (Drush or Drupal Console). The community has been working hard to get all these functions to run through a web user interface (UI).

Here we'll discuss some of the various options for running a migration via a web UI. There are several options that we are aware in various levels of stability.

Edys Meza Thu, 09/28/2017 - 13:01

Nextide Blog: Maestro D8 Concepts Part 3: Logical Loopbacks & Regeneration

Thu, 09/28/2017 - 20:04
Loopbacks and Regeneration

Since 2003, Maestro had the concept of "Regeneration".  Regeneration for Maestro on Drupal 7 was a rather nebulous concept if you didn't understand the complexities that exist within the original engine.  Most administrators would simply check the regeneration option to "on" and the option to "recreate all in production tasks" and never worry about what it actually meant.  Simply put, as a human reading a workflow diagram, we can understand when a logic condition causes a loop-back over already executed tasks. However, for a machine to detect when we're looping-back over already executed tasks produces a set of logical issues that are not easily overcome.

Mediacurrent: A Brief History of Google’s V8 Javascript Engine

Thu, 09/28/2017 - 18:59

Javascript has a reputation in developer circles as a terrible language. It’s classless, loosely typed, and plagued by cross browser issues. Douglas Crockford, author of JavaScript: The Good Parts, said “JavaScript contains some of the best ideas ever put into a programming language and it contains some of the worst ideas ever put into a programming language.” It was created in just 10 days in 1995, and not standardized by ECMA until almost 3 years later. Microsoft initially decided not to implement the new standards, almost putting an end to the language in its infancy.

Drop Guard: Automatic Drupal Updates - WTF or FTW?

Thu, 09/28/2017 - 10:30
Automatic Drupal Updates - WTF or FTW?

Automatic updates have been discusses since years already. The pro's and con's of letting Drupal update itself are discussed in different Drupal.org issues queues. It was not a big surprise that Dries mentioned automatic Drupal core updates as part of the strategic roadmap of Drupal in his Driesnote at DrupalCon Vienna 2017.

Drupalcon Drupal Drupal Community Drupal Planet Automation Events Driesnote

Amazee Labs: Rapid conferencing - DrupalCon Wednesday

Thu, 09/28/2017 - 10:06
Rapid conferencing - DrupalCon Wednesday

Vienna is my first #DrupalConEUR and due to family obligations, I could only attend 1.5 days out of the full week of events, so I made the most of my time. Here’s a quick recap.

Fran Garcia Thu, 09/28/2017 - 10:06

Before

Preparation - deciding which talks to attend - wasn’t as easy as you'd think. The schedule is full of interesting talks, so I needed to pick and choose the ones that I really wanted to attend. I’ll expand on the talks, which I did attend, later on.

During

I arrived in Vienna on Tuesday night and went straight to a restaurant to have dinner and meet some of my colleagues, who were already there. In the room, we had people from South Africa, Switzerland, Tunisia, Spain… We had a great time, but this was just the warm-up for Wednesday’s events.

After some sleep, my first DrupalCon experience was about to begin, where I could do some catching up, in the keynote, with colleagues and old friends. After this, we also found some time to do actual problem-solving in real life!

I finally opted to go to:

  • Tour of the 35 Symfony Components: where we learned loads about this PHP framework that empowers Drupal 8. It was really interesting to find out the components that we were already using and the ones we weren’t but could very easily hook into Drupal.
  • Building amazing searches with Search API: the creator/main maintainer of the module showed us how all the Search API modules tie together in Drupal 8 with live demos of the code. 
  • Motion design - improving UX through animations: this was a small Amazee’s gathering to view and support Sarah & Lisa in their presentation where they took us through some really cool animations and discussed dos and don'ts of good animations.
  • Power to the people - How using containers can make your life easier: given by our AmazeeIO peers, they talked about how we can use containers for our production sites, the pros and cons of them, and we had a quick peek into the possible future and the possible things we could achieve with containers.
  • CSS-in-JS: unexpected lessons for Drupal component design: a really nice and cool talk by John Albin, in which he explained lessons learned from years of working with JS and CSS, and how to nicely pack them all into components. Awesome way to close up the first DrupalCon day. 

I know I did miss some very amazing talks, but I also knew that they’d be available on YouTube so I will be catching up on those during the next weeks.

Amazee dinner

However, the day was far from over, as the night was reserved for our amazing team dinner! This was a great opportunity to catch up on our #DrupalConEUR talks and experiences so far, but also, for remote people like me, it was the time to catch up, in real life, with the people I work with every day.

The dinner was just amazing. I had my second Schnitzel in my short time in Vienna, but just found out that I was still far from Michael’s five! We were there until they literally asked us to go, chatting, laughing and sharing awesome stories with one another. It was a great bonding night for the team and we all learned new things from and about our other colleagues.

After

I’ll catch a flight in a few hours. It’s hard to believe that my DrupalCon experience took less than two days. I’m taking back loads of really nice experiences, the warmth of the Amazee team (I’ll need this in the UK…) and I can now say that I’ve gone to my first DrupalCon!

 

Short and sweet - that’s how I’ll remember it.

Appnovation Technologies: TechPong - Supporting Britannia Secondary School’s Youth

Thu, 09/28/2017 - 09:00
TechPong - Supporting Britannia Secondary School’s Youth TechPong is an annual heart-racing ping pong tournament for charity organized by Chimp, Unbounce and Science World on October 19th. For the 3rd year, Appnovation will send our best doubles team and solo team to duke it out against other Vancouver companies. This year they are expecting 1000 attendees to make it the biggest T...

Agiledrop.com Blog: AGILEDROP: Latest Drupal 8 books

Thu, 09/28/2017 - 07:17
We have published a blog post about Top Drupal 8 books before. We have looked at the best books the newest version of Drupal has to offer. That was at the beginning of this year. So, around nine months later, we decided it was time to once again look at this area and explore, which Drupal 8 books were published during that time. Drupal 8 features are being explored every day. Many Drupal modules are getting properly migrated to Drupal 8 and many more are getting developed. Nevertheless, Drupal 8 books also offer many insights, so here are some, which were published in the last nine months… READ MORE

MTech, LLC: Migration From Field Collection to Paragraphs in D8

Thu, 09/28/2017 - 00:27
Migration From Field Collection to Paragraphs in D8

If you need to migrate field collections from Drupal 7 into Drupal 8, here's a walk through of how to do it. But before you start reading, I'd like you to stop and see how you can make this process better. In this Meta issue, we have a plan to automate all parts of this process. As the heir aparent to Field collections, we are working with the larger Drupal community to include for support migrating directly into Drupal 8 from field collections.

Ada Hernández Wed, 09/27/2017 - 16:27

Ben's SEO Blog: Is Your Drupal Website Antisocial?

Wed, 09/27/2017 - 18:06

Social media needs to be a part of your search engine optimization strategy. While the level of involvement in social media can be determined by your market and your customers, ignoring social media can no longer be an option. Smart Drupal SEO strategies include building authority in social media channels.

Search engine algorithms for social media vary

Google has stated clearly that social signals such as the number of Facebook likes and Twitter followers are not factored into Google’s search algorithm. To Google, each individual tweet or Facebook post is considered a web page on its own. On the other hand, Bing says that it does look at the social authority of a user. “We look at how many people you follow, how many follow you, and this can add a little weight to a listing in... Read the full article: Is Your Drupal Website Antisocial?

Drupal blog: State of Drupal presentation (September 2017)

Wed, 09/27/2017 - 16:33

This blog has been re-posted with permission from Dries Buytaert's blog. Please leave your comments on the original post.

Yesterday, I shared my State of Drupal presentation at DrupalCon Vienna. In addition to sharing my slides, I wanted to provide some more detail on how Drupal is evolving, who Drupal is for, and what I believe we should focus on.

Drupal is growing and changing

I started my keynote by explaining that Drupal is growing. Over the past year, we've witnessed a rise in community engagement, which has strengthened Drupal 8 adoption.

This is supported by the 2017 Drupal Business Survey; after surveying 239 executives from Drupal agencies, we can see that Drupal 8 has become the defacto release for them and that most of the Drupal businesses report to be growing.

While the transition from Drupal 7 to Drupal 8 is not complete, Drupal 8's innovation continues to accelerate. We've seen the contributed modules ecosystem mature; in the past year, the number of stable modules has more than doubled. Additionally, there are over 4,000 modules in development.

In addition to growth, both the vendor and technology landscapes around Drupal are changing. In my keynote, I noted three primary shifts in the vendor landscape. Single blogs, portfolio sites and brochure sites, which represent the low end of the market, are best served by SaaS tools. On the other side of the spectrum, a majority of enterprise vendors are moving beyond content management into larger marketing suites. Finally, the headless CMS market segment is growing rapidly, with some vendors growing at a rate of 500% year over year.

There are also significant changes in the technology landscape surrounding Drupal, as a rising number of Drupal agencies have also started using modern JavaScript technologies. For example, more than 50% of Drupal agencies are also using Node.js to support the needs of their customers.

While evolving vendor and technology landscapes present many opportunities for Drupal, it can also introduce uncertainty. After listening to many people in the Drupal community, it's clear that all these market and technology trends, combined with the long development and adoption cycle of Drupal 8, has left some wondering what this all means for Drupal, and by extension also for them.

Drupal is no longer for simple sites

Over the past year, I've explained why I believe Drupal is for ambitious digital experiences, in both my DrupalCon Baltimore keynote and on my blog. However, I think it would be valuable to provide more detail on what I mean by "ambitious digital experiences". It's important that we all understand who Drupal is for, because it drives our strategy, which in turn allows us to focus our efforts.

Today, I believe that Drupal is no longer for simple sites. Instead, Drupal's sweetspot is sites or digital experiences that require a certain level of customization or flexibility — something I refer to as "richness".

Ambitious is much more than just enterprise

This distinction is important because I often find that the term "ambitious" becomes conflated with "enterprise". While I agree that Drupal is a great fit for the enterprise, I personally never loved that categorization. It's not just large organizations that use Drupal. Individuals, small startups, universities, museums and nonprofits can be equally ambitious in what they'd like to accomplish and Drupal can be an incredible solution for them.

An example of this could be a small business that manages 50 rental properties. While they don't have a lot of traffic (reach), they require integrations with an e-commerce system, a booking system, and a customer support tool to support their business. Their allotted budget is $50,000 or less. This company would not be considered an enterprise business; however, Drupal would be a great fit for this use case. In many ways, the "non-enterprise ambitious digital experiences" represent the majority of the Drupal ecosystem. As I made clear in my presentation, we don't want to leave those behind.

Addressing the needs of smaller organizations

The Drupal ecosystem majority are organizations with sites that require medium-to-high richness, which SaaS builders cannot support. However, they also don't need to scale at the level of enterprise companies. As the Drupal community continues to consider how we can best support this majority, a lot of smaller Drupal agencies and end-users have pointed out that they would benefit from the following two things:

  1. Powerful site building tools. They want easy-to-use site building tools that are simple to learn, and don't require dozens of contributed modules to be installed and configured. They would also prefer to avoid writing a lot of custom code because their clients have smaller budgets. Great examples of tools that would improve site building are Drupal's upcoming layout builder, workspaces and media library. To make some of Drupal's own administrative UIs more powerful and easier to use, I proposed that we add a modern JavaScript to core.
  2. Easier updates and maintenance. While each Drupal 8 site benefits from continuous innovation, it also needs to be updated more often. The new Drupal 8 release cycle has monthly patch releases and 6-month minor releases. In addition, organizations have to juggle ad-hoc updates from contributed modules. In addition, site updates has often become more complex because our dependency on third-party libraries and because not everyone can use Composer. Many smaller users and agencies would benefit tremendously from auto-updates because maintaining and updating their Drupal 8 sites can be too manual, too complex and too expensive.

The good news is that we have made progress in both improving site builder tools and simplifying updates and maintenance. Keep an eye on future blog posts about these topics. In the meantime, you can watch a recording of my keynote (starting at 22:10), or you can download a copy of my slides (56 MB).

State of Drupal keynote, DrupalCon Vienna from Dries Buytaert State of Drupal keynote, DrupalCon Vienna from Dries Buytaert

Lullabot: Small Ways to Conduct User Research That Can Make A Big Impact

Wed, 09/27/2017 - 14:30

We’ve worked with many amazing clients who had to be careful about their budget or needed a project completed rather quickly. You may be one of those clients. If you’re in the process of hiring a design firm to help improve your product or website but are concerned about investing in user research and testing because of budget or timeline constraints, you’re in good company. What follows are some practical ideas your designers can use to increase your chances of success without breaking the bank. 

Research to conduct during the project kickoff “People ignore design that ignores people.” - Frank Chimero, Author of The Shape of Design Conducting User and Stakeholder Interviews

A clear understanding of the problems you’re solving and who you’re solving them for is critical to the success of any design project. A site’s “users” are made up of not just the end users or target audience of the site, but also the business users: the product stakeholders, content editors, designers, and the team that will use the site over time to reach that audience. Those business users are an ideal starting point for research. The people who create and manage the content, run sales for the organization or handle customer service are often a wealth of information about the target audience they’re serving and their common needs and challenges. These same stakeholders also help clarify the true purpose and goals of the project and any potential pitfalls.

Before any collaborative workshopping, we always try to conduct individual interviews with at least a representative of each of these kinds of stakeholders (e.g., content and editorial, marketing, sales, customer service, leadership, etc.). We’ve found this process to be hugely beneficial for things like:

  • Clarifying project goals
  • Clarifying the audience and its various segments
  • Clarifying the known problem space
  • Clarifying the existing, driving assumptions about the site’s users that perhaps need more research
  • Surfacing internal conflicts that need resolution
  • Surfacing potential pitfalls for the project
undefined

This early information you easily get from these interviews can be invaluable as you begin crafting interview protocols, surveys, and other research methods to learn from the site’s audience. Conducting research with a site’s audience (the external user base) is often where the bulk of the cost lies, so getting as much clarity up front to help refine that work can save a lot of time and cost.

Sharing Relevant Documentation

Another highly effective way to reduce research costs in your project is to make sure that your design team can leverage all of the past research your team or others have already done. Designers can learn a great deal very quickly by reviewing the results of past annual surveys or support requests. Below is a list of the kinds of things you should look for and be sure to share with your design team to save time and ensure a better end product.

  • Existing internal persona documents that define your audience
  • Access to site analytics
  • Past surveys of your audience
  • Notes, audio or video of any past user tests or interviews
  • Existing user flows
  • Existing documentation or reports from customer service teams on common problems or guides for those customer service reps

Collecting your team’s knowledge about your audience and summarizing it in an audience inventory worksheet can also help save your designer time when reading through the research.

undefined Competitive Analysis

Conducting a competitive analysis of your competition can also be used to evaluate your audience and make a comparison of how your product or site stacks up against the competition. Designers can usually complete these within a day or two, if not within a few hours. They’ll use a set of heuristics such as design consistency, the grouping of common tasks, functionality, mobile friendliness, and placement of links or calls to action, to help evaluate your site against the competition. This evaluation will help set up a strong design strategy that distinguishes your site.  

Research to conduct during the design process In Process Usability Testing “To design an easy-to-use interface, pay attention to what users do, not what they say. Self-reported claims are unreliable, as are user speculations about future behavior.” - Jakob Nielsen, User Advocate and principal of the Nielsen Norman Group

Even when you think you understand the problems users have, there are times when your designers will need to ensure that the ideas they’re proposing resonate with your audience. Will they understand how to use a certain component? Does the marketing copy answer their questions? Does the visual design accurately reflect the core values and mission of the company? These are all questions your designers should be asking themselves throughout the design process. Conducting usability tests early and throughout the design process with actual users can help them answer these questions and validate that the design is on the right track.

Usability testing doesn’t have to be a long, expensive process. There are ways your designers can test their ideas with users rather quickly. Tree testing can be a quick way to test your site's IA hierarchy and navigation nomenclature without producing a bunch of artifacts such as wireframes or prototypes that are often needed for usability testing. Your designers can also use wireframes or paper prototypes to conduct efficient usability tests during the exploration phase. At Lullabot, we’ve used a combination of the above to help conduct usability tests in an efficient manner. Conducting usability tests throughout the process with help ensure that the design and strategy are on the right track, and also sets the site up for success.

undefined Research to Conduct After Launch

Your project has launched! Hopefully, everything went smoothly, and now there’s a sigh of relief. But there's still work to be done. The ultimate form of user testing is launching a site! The best designers want to keep on learning and iterating. What follows are a few affordable ways to do this. 

Conducting Surveys Placing an optional survey on the site is an inexpensive way to collect user feedback that doesn’t require a lot of time to set up. Surveying can identify if something is not working correctly on the site and can help quickly collect user feedback to address in possible future iterations.  Surveying establishes a user pool for future usability testing. Keeping surveys short (5 brief questions or less) increases the number of users who are likely to complete the survey. Tools like SurveyMonkey, Ethnio, and Typeform can easily integrate into your site. 

Another option is to place a link somewhere on the site where users can give feedback. An example of this might be if you're rolling out a restructured navigation. Placing a link titled “can’t find what you’re looking for?” in the navigation that links to a form can help users quickly give feedback on how the new structure is working for them and help to identify any changes that may need to be addressed in the new navigational structure.

Usability Testing

Conducting usability tests on a recently launched site is another way to quickly gather user feedback on how well the site is working for the audience. Since conducting usability sites on the actual launched site requires no prototyping, it can be fairly quick to set up and conduct these tests. You can also save time with recruitment by reusing the same user pool that you had gathered during the in-process usability tests.  

Post Launch Meetings

Finally, another inexpensive practice we highly recommend is scheduling regular design check-ins post-launch. Set an interval of either quarterly or biannually to ensure that there's time for real data to come in from real users, but also regular enough to perhaps take action and roll out small improvements based on the data. In these regular meetings, we recommend you do at least the following:

  • Review anything that’s gone well, and has been surprising or concerning when it comes to users interacting with the site.
  • Review any feedback that your team may collect from actual users
  • Review and discuss any changes to the goals business or the goals of the site 
  • Discuss the progress of the site in relation to the goals that were set. Are they on target?

Adding user research to your project process can be beneficial to everyone involved to help understand your audience’s behavior, their goals, and can help inform how to improve your site after it’s launched. Not every project will have an ample budget or timeline for an in-depth research process, but there are small ways to validate ideas to create a site that’s successful and communicates to your audience. If you’re concerned about how user research can affect the budget, I hope you’ll take some of the above into consideration when discussing user research with your designers and collaborate with them to find small ways to work user research into your process. If you’re interested in learning more, I’d recommend reading Just Enough Research by Erika Hall and The User Experience Team of One: A Research and Design Survival Guide by Leah Buley.

Amazee Labs: Drupalcon Europe gets going

Wed, 09/27/2017 - 14:00
Drupalcon Europe gets going

The people have arrived from all around the world. The booths have been set up. #DrupalConEUR 2017 - It has begun!

Bryan Gruneberg Wed, 09/27/2017 - 14:00

The obvious highlights of the day were the Prenote and the Keynote address.

What is the Prenote you ask? You can check it out for yourself! You may even recognise some of the people who took part!

Where are we from?

Our friends over at Pantheon ran a “from the stage” survey of the community in the room (and I guess a few people who were watching the live stream). Inky, Dania, Lees and I are from Cape Town and Mostfa is from Tunisia. I’m fairly sure that Amazee Labs people account for a large portion of the 1% from Africa.

 

What do we like?

It starts with the community of course. There is meeting people, sharing food, learning, sprinting on the project. And friends!

 

… and of course, there is beer. And people, and travel, and connections, and OIDA.

 

… and there are stickers and hugs… AND beer sessions, and networking beer, and community beer. And if you keep an eye out and stay vigilant you might just spot a beer.

 

OIDA!

Dries took to the stage to the expected applause from the room. He spent quite some time going through the product stats and if you weren’t at the Driesnote it's worth checking out the full presentation below.

At Amazee Labs, we use Drupal all the time. It supports most of what we produce, and it underpins 100% of what we do. In my team, we support, extend, and maintain a myriad Drupal 7 and 8 sites. Soon we will be onboarding some of the more ambitious Fully Decoupled Drupal-React sites that the sprint teams have been hard at work on this year into the maintenance and extension project phase. It is really helpful to have someone like Dries stand up and force us to take stock of where Drupal is a product and to highlight some of the things that the people using the product should be thinking about.

 

“The CMS Vendor Landscape is changing”

The CMS vendor landscape is undergoing a transformation. With the rapid rise and adoption of various Javascript frameworks, and patterns, CMSs are increasingly becoming (or in the case of Drupal, being used as) headless providers of data and content. This will over time inevitably change things for the Drupal project.

 

“Drupal is for Ambitious Digital Experiences”

So what is the graph telling us? It maps different potential Drupal users in two dimensions along Reach (how many people will the system touch?), and Richness (how many features will the system have?). Perhaps the most striking piece is the explicit acknowledgment that the SaaS competitive platforms are now mature and feature-rich enough to make them more appropriate for blogs, portfolio, and brochure sites.

But we can also see that Drupal isn’t only for enterprise clients. To quote Dries: “Ambitious is much more than just enterprise”. In fact, enterprise clients are only a portion of the potential Drupal market. There is plenty of space (perhaps even the majority of the market?) for feature-rich sites to be built and deployed for customers who we would not consider Enterprise. And Dries’ talk suggests that we should think about this, and start to include this in our strategies, and to help our customers to include this in their strategies.

Dries Buytaert: State of Drupal presentation (September 2017)

Wed, 09/27/2017 - 13:55

Yesterday, I shared my State of Drupal presentation at DrupalCon Vienna. In addition to sharing my slides, I wanted to provide some more detail on how Drupal is evolving, who Drupal is for, and what I believe we should focus on.

Drupal is growing and changing

I started my keynote by explaining that Drupal is growing. Over the past year, we've witnessed a rise in community engagement, which has strengthened Drupal 8 adoption.

This is supported by the 2017 Drupal Business Survey; after surveying 239 executives from Drupal agencies, we can see that Drupal 8 has become the defacto release for them and that most of the Drupal businesses report to be growing.

While the transition from Drupal 7 to Drupal 8 is not complete, Drupal 8's innovation continues to accelerate. We've seen the contributed modules ecosystem mature; in the past year, the number of stable modules has more than doubled. Additionally, there are over 4,000 modules in development.

In addition to growth, both the vendor and technology landscapes around Drupal are changing. In my keynote, I noted three primary shifts in the vendor landscape. Single blogs, portfolio sites and brochure sites, which represent the low end of the market, are best served by SaaS tools. On the other side of the spectrum, a majority of enterprise vendors are moving beyond content management into larger marketing suites. Finally, the headless CMS market segment is growing rapidly, with some vendors growing at a rate of 500% year over year.

There are also significant changes in the technology landscape surrounding Drupal, as a rising number of Drupal agencies have also started using modern JavaScript technologies. For example, more than 50% of Drupal agencies are also using Node.js to support the needs of their customers.

While evolving vendor and technology landscapes present many opportunities for Drupal, it can also introduce uncertainty. After listening to many people in the Drupal community, it's clear that all these market and technology trends, combined with the long development and adoption cycle of Drupal 8, has left some wondering what this all means for Drupal, and by extension also for them.

Drupal is no longer for simple sites

Over the past year, I've explained why I believe Drupal is for ambitious digital experiences, in both my DrupalCon Baltimore keynote and on my blog. However, I think it would be valuable to provide more detail on what I mean by "ambitious digital experiences". It's important that we all understand who Drupal is for, because it drives our strategy, which in turn allows us to focus our efforts.

Today, I believe that Drupal is no longer for simple sites. Instead, Drupal's sweetspot is sites or digital experiences that require a certain level of customization or flexibility — something I refer to as "richness".

Ambitious is much more than just enterprise

This distinction is important because I often find that the term "ambitious" becomes conflated with "enterprise". While I agree that Drupal is a great fit for the enterprise, I personally never loved that categorization. It's not just large organizations that use Drupal. Individuals, small startups, universities, museums and nonprofits can be equally ambitious in what they'd like to accomplish and Drupal can be an incredible solution for them.

An example of this could be a small business that manages 50 rental properties. While they don't have a lot of traffic (reach), they require integrations with an e-commerce system, a booking system, and a customer support tool to support their business. Their allotted budget is $50,000 or less. This company would not be considered an enterprise business; however, Drupal would be a great fit for this use case. In many ways, the "non-enterprise ambitious digital experiences" represent the majority of the Drupal ecosystem. As I made clear in my presentation, we don't want to leave those behind.

Addressing the needs of smaller organizations

The Drupal ecosystem majority are organizations with sites that require medium-to-high richness, which SaaS builders cannot support. However, they also don't need to scale at the level of enterprise companies. As the Drupal community continues to consider how we can best support this majority, a lot of smaller Drupal agencies and end-users have pointed out that they would benefit from the following two things:

  1. Powerful site building tools. They want easy-to-use site building tools that are simple to learn, and don't require dozens of contributed modules to be installed and configured. They would also prefer to avoid writing a lot of custom code because their clients have smaller budgets. Great examples of tools that would improve site building are Drupal's upcoming layout builder, workspaces and media library. To make some of Drupal's own administrative UIs more powerful and easier to use, I proposed that we add a modern JavaScript to core.
  2. Easier updates and maintenance. While each Drupal 8 site benefits from continuous innovation, it also needs to be updated more often. The new Drupal 8 release cycle has monthly patch releases and 6-month minor releases. In addition, organizations have to juggle ad-hoc updates from contributed modules. In addition, site updates has often become more complex because our dependency on third-party libraries and because not everyone can use Composer. Many smaller users and agencies would benefit tremendously from auto-updates because maintaining and updating their Drupal 8 sites can be too manual, too complex and too expensive.

The good news is that we have made progress in both improving site builder tools and simplifying updates and maintenance. Keep an eye on future blog posts about these topics. In the meantime, you can watch a recording of my keynote (starting at 22:10), or you can download a copy of my slides (56 MB).

Colorfield: PlanetDrupal.org a starter kit for newcomers

Wed, 09/27/2017 - 00:42
PlanetDrupal.org a starter kit for newcomers christophe Wed, 27/09/2017 - 00:42 Today, building a website in Drupal 8 is faster than ever, even for a beginner. Or let’s rephrase this: it can be fast when you have the right information at your fingertips. The seed of this idea was sown during the session of Dave Hall given in the DrupalCamp Antwerp on September 2017. Just have a look at what follows, it describes the adoption process of Drupal compared to other solutions like Contentful.