Development News

WPTavern: iThemes Enters the Hosting Space

Wordpress Planet - Tue, 07/17/2018 - 23:19

iThemes is getting into the hosting business after launching three plans that take advantage of its relationship with Liquid Web. The plans are finely tuned around the company’s products and come with free SSL certificates.

I reached out to Cory Miller, Founder of iThemes to figure out why they’ve entered the hosting space, what it means to be able to control the user experience of their products from the top-down, and how their plans compare to those from hosts that offer Jetpack Premium.

Interview With Cory Miller

What does it mean for you and iThemes to be able to control the user experience from the top-down?

In short, it means a better overall experience for our customers. For more than 10 years, we’ve dealt with most of the hosts, especially the ones offering catered WordPress offerings, and it has been a terribly frustrating experience for us trying to troubleshoot problems and help our mutual customers.

Additionally, we’ve long said you have to have two things to be our customer: WordPress and web hosting. Now we install WordPress for you, along with SSL, essentially with a click on our own hosting.

How would you compare iThemes hosting packages to hosts that offer Jetpack Premium services as part of their plans?

The thing that sticks out for me is having everything under one brand and team. But we think using iThemes Sync Pro as the hosting control panel gives us a significant edge for our customers to do more with their WP sites, in particular, our reporting features in Sync Pro.

Now our customers can get WP backups, security, site management and in-depth reporting all from one dashboard, along with their hosting. With our Business plan, they get BackupBuddy, our WordPress backup plugin; iThemes Security Pro, our WordPress security plugin & iThemes Sync Pro all in one. Plus they get an awesome team of WordPress pros for support if they need help or have any issues.

What are you most looking forward too offering these hosting packages specifically tuned for iThemes products and WordPress?

The actual implementation of the vision of offering the key essentials we think people want and need, along with a roadmap to do more, from our team at iThemes. It was one of the motivators for joining the Liquid Web family — the ability to finally do what we’ve always wanted to do for our customers, offering a more complete experience for them, from us.

Were there any challenges that you overcame when putting these packages together?

The main one that comes to mind is trying to ensure we offer what people actually want and will buy. But there was several months of hard work by our team and others to get this launched. Some long nights to pull all the pieces together in order to do this, with many more to come.

Prices range from $15 per month to $25 per month billed on an annual basis. New customers can take advantage of a coupon code on the site to purchase the Business plan, normally $25 for $15.

WPTavern: WooCommerce Custom Product Tables Plugin Now in Beta, Boasts 30% Faster Page Loads

Wordpress Planet - Tue, 07/17/2018 - 20:20

WooCommerce is celebrating 10th years of Woo this week. Over the past several years WooCommerce has grown to become a dominant player among e-commerce solutions on the web. E-commerce Usage Distribution stats from BuiltWith currently rank WooCommerce as the most commonly used platform for stores in the top 1 million sites.

Performance and scalability were the main focuses for the WooCommerce development team last year and these issues continue to be top priority. Version 3.0, released in April 2017, included significant performance improvements when WooCommerce switched from post meta to taxonomies for features like product visibility, featured products, and out of stock products. It also introduced CRUD (Create, Read, Update, Delete) classes for developers, making it easier to write and retrieve data from the database with less code.

Building on the CRUD work done last year, WooCommerce has just announced the beta of its new Custom Products Tables plugin. It replaces the WooCommerce product Data Store with new, dedicated product tables for significant reductions in page load time across shop, checkout, and admin pages.

“The results, so far, have been great – with improvements of up to 30% on page load times!” WooCommerce engineer Gerhard Potgieter said. “Checkout, arguably the most important part of the store experience, has seen the biggest performance gains.”

The WooCommerce development team tested the plugin’s impact on performance using two identical stores running the Storefront theme and no additional plugins. They created a data set of 500 products using the WooCommerce Smooth Generator, and both stores had 70,000 orders in the database and meta data in the range of 1.4 million rows.

image credit: WooCommerce Development Blog

The Custom Product Tables plugin is not ready for use in production but developers can download version 1 and test it against WooCommerce 3.5 dev (switch to the master branch).

Getting the plugin rolled into WooCommerce core is an exciting update on the horizon, as faster page loads generally improve conversion for store owners. WooCommerce engineers anticipate releasing the plugin on WordPress.org as the next step. They plan to include the new product tables in a major version update early next year.

mark.ie: Getting Value (URI) of a Drupal Media (File) Field from within a Twig Template

Main Drupal Feed - Tue, 07/17/2018 - 16:07
Getting Value (URI) of a Drupal Media (File) Field from within a Twig Template

To the future or to the past, to a time when thought is free, to the next time when I need to get the value of file field to use as a variable in Drupal 8 with Twig.

markconroy Tue, 07/17/2018 - 17:07

Working my way down through one of Drupal's render arrays of doom to try to get the URI of a file in a media field (in a paragraph type), I came up with this. If you can improve it, feel free to drop a note in the comments:

{% set slide_url = file_url(content.field_p_ei_speaker_slides[0]['#media'].field_m_file_file.entity.uri.value) %}

In steps:

  1. Get the {{ content }} variable
  2. Drill down into the media field (Speaker Slides - pdf, ppt, etc)
  3. Get the first element (0 - it's not a multi-value field in this case)
  4. Load up the #media object
  5. Interrogate the field on the media entity that has the file attached (the File field)
  6. Load this entity (entity here is not presented as an item in the {{ dpm() }} but it's very handy to know
  7. Get the uri.value from here
  8. Wrap it all in a file_url() function

For clarity, here's what I had in PatternLab:

  {# Begin Slides Download #}
  {% if event_slide_download %}
   
     
        {% include '@basic-elements/icons/_svg.twig'
          with {
            svgpath : '@basic-elements/icons/svg/download.svg'
          }
        %}
     

   
  {% endif %}
  {# End Slides Download #}

And here's what I have in the corresponding Drupal paragraph.html.twig tempate:

{% if paragraph.field_p_ei_speaker_slides.value %}
  {% set event_slide_download = true %}
  {% set slide_url = file_url(content.field_p_ei_speaker_slides[0]['#media'].field_m_file_file.entity.uri.value) %}
  {% set event_slide_download_link = slide_url %}
{% endif %}

{% include "@building-blocks/event-section/event-item.twig" %}

So now, my future self, you will know where to find this next time.

Phase2: Decoupled Drupal 8 + GatsbyJS: a quickstart guide

Main Drupal Feed - Tue, 07/17/2018 - 15:07

If you're not familiar with GatsbyJS, then you owe it to yourself to check it out. It's an up and coming static site generator with React and GraphQL baked in, and it prides itself on being really easy to integrate with common CMS'es like Drupal.

OpenSense Labs: Approach your Mobile-First Design with This Guide

Main Drupal Feed - Tue, 07/17/2018 - 13:51
Approach your Mobile-First Design with This Guide Harshit Tue, 07/17/2018 - 19:21

It’s always a battle when planning a website design. Your end goals, target audience, content, user experience, everything must align. It’s like a cloud of thoughts right inside your team’s head. It’s critical to optimize your website experience for the devices your audience is or will be using. 

Emarketer forecasts, approximately 83% of internet users will use a mobile phone to go online by 2021. 

Since now that we’ve established the fact that mobile is where the future lies, a mobile-first redesign is a way to go. We’ll dive into what a mobile-first approach entails, including tips for creating a seamless experience for visitors from mobile devices. 

In 2018, it is critical to analyze what’s the right way to go about it. 

1. Shoot for the least 

Without compromising the functionalities, it is definitely a challenge to pull everything into such a limited real estate. The difference in the screen space of various devices should tell you the varied approach to design. 

Minimalism begins by removing every element one by one.

After listing down all the elements, prioritizing is key. Sort out the cruciality of every element and how would they hierarchically sit in the interface. This should be in a way that the most important elements are displayed prominently. 

If after this exercise there’s still space for more, carefully add some elements in order of importance without overdoing it. Doing this would make sure every inch is utilised to the fullest. 

Content Repository 

The approach to this should be by drafting a document or a spreadsheet containing all the content elements you want the interface to entail. 

List down the page titles, navigation titles and be open to comments from peers. An example is given below:

An example of a content repository2. Analyse the Important Interaction Points

Comparing smartphones from 2008 to the ones in 2018,  a lot has changed since then. The user experience is no more frustrating. Earlier you had to touch the exact alphabet in the keyboard now the smart devices can read your movement through sensors. Keyboards differ according to the smartphone size, button space and overall sensitivity. And so your mobile design should be approached in the same manner. 

Unfortunately, many websites are still lagging behind when it comes to the user experience which leads to weak engagement, poor sessions and doubled bounce rates. 
Make sure the important elements are not missed. 

This includes: 

  • Make button more clickable
  • Make CTAs more appealing and responsive
  • Choose the right color combination for the user to read on the sunny noon
  • Give hyperlinks plenty of space
  • Keep the tabs in the drop down manner
Good vs Bad UX design The number of mobile phone users in the world is expected to pass the five billion mark by 2019, according to Statista.  3. Optimize Your Images

When it comes to loading size, images make up nearly 64% of an average web page. Outlining the “why”, it is now important to know how you can optimize your images to deliver an optimum and engaging experience to your user, without hogging on those extra kilobytes of data. 

Hacks to Optimize Images
  • Use correct image dimensions for faster loading
  • Use the correct image format. JPEG image would be a lot lighter than the PNG.
  • Compress your image with lossless compression
  • Use Lazy loader to keep the user engaged
4. Content is all that matters

Devising content around mobile is time-consuming as it requires due thinking and goes through numerous iterations along the course of finalizing the content itself. 

Taking the limited space aside for a while, there are more added difficulties when it comes to mobile web development. 

There comes screen rotation, device to device compatibility, text and image overlaps and what not. These factors have everything to make your content look very less appealing. What do you do for cutting these hurdles off? 

Think from an app perspective

Mobile users are accustomed to motion and a modicum of control in their experience. Think about off-canvas navigation, expandable widgets, AJAX calls, or other elements on the screen with which users can interact without refreshing the page. This would help you always maintain the right threshold for user experience. 

Screen and remove all the distracting elements, make the content as precise as possible while catering to actual product or service display. 

Landscape photos and complex graphics don't show well when your screen is reduced by half. Take into account the mobile user with pictures that are comprehensible on handheld screens.

5. Be a User, Before Presenting to the User

Our industry standard for approaching design is devising wireframes first. During wireframing or prototyping, use adaptive breakpoints reference. It streamlines the process of moving to different screen sizes, starting with the least real estate. 

Hover is off the table

Interactive interfaces from 2018 mostly utilize hover effects. UX designers go bonkers over them. But that’s a desktop only thing as we do not have the finger-hover technology in town. You will have to forget hover' existence when going mobile. 

Having trouble configuring your site? Check out services by OpenSense Labs.

6. Opt for Accelerated Mobile Pages

Your users are likely to bounce off your website if it doesn’t load within 3 seconds. With mobile, the standard has been set high (or rather less). Since the internet has been taken for granted, people have become second sensitive these days. 

AMP does bring you speedy pages and is a great way to boost your SEO and stop losing out of potential customers. It’s important to note that Google has gone lengths to identify and promote AMP pages.

If your web pages follow AMP standards, it becomes eligible to be cached by Google and appear in the search results and carousels with the AMP logo, indicating that they offer a fast experience. 

A standard built on top of existing technologies to speed up the loading of web pages on mobile devices.

How to go about it?

Configure AMP in your website

7. Make engagement on Mobile Simple 

Whether it’s deciding between a “hamburger” style menu or a more visible-style on the front end or how to display forms on specific pages, don’t make engagement paths more abstract than they need to be. Engagement should be extremely crisp and effective in nature.


Set the Display Order

Now, after listing down all the elements, prioritizing is key. Sort out the cruciality of every element and how would they hierarchically sit in the interface. This should be in a way that the most important elements are displayed prominently. 

8. Test It Before You Sell It

Even after having the final product in your hands, recommendations and tweaks will keep flowing in. Change is evergreen. With changes being made, you need to be testing them as soon as they are deployed. 

Nothing beats discovering for yourself how usable a website is (or isn’t). Step away from your computer desktops and load up your product on a real phone or tablet. 

Test it in a real devices 

Using testing tools, you can conduct A/B tests. Some tests may be like, an orange CTA vs a Yellow CTA, Button size changes, block layout tweaks and etc. Tests can range from regular functionality checks to user experience tests.

Tap through pages. Is the site easy to navigate? Does it load in a timely fashion? Are the text and graphics easy to read?

It's as clear as the skies that the future of the internet is dependent on mobile experiences. Responsive web design is a must if you run your business online or attend to your customers for any purpose. 

The tips above will help you build what you are looking at while making the least possible amount of mistakes. 

If you need any further recommendations, we are here. Hook with us at hello@opensenselabs.com or tweet us at @OpenSenseLabs and our mobile development team will save you the trouble.

blog banner blog image Mobile first Mobile friendly  User experience Drupal Web Redesign Drupal websites Mobile approach Websites Mobile first approach Webpages Design Ideas Design Ideology Design Blog Type Articles Is it a good read ? On

Web Wash: Live Training: Managing Media Assets using Core Media in Drupal 8

Main Drupal Feed - Tue, 07/17/2018 - 13:30

In the video above, you'll learn how to build powerful media management functionality using Drupal 8.5. I start the webinar with a review of what's new in Drupal 8 and then jump right into a live demo.

If you prefer text, then read our tutorial on "Managing Media Assets using Core Media in Drupal 8".

Blair Wadman: How to add page templates for content types in Drupal 8

Main Drupal Feed - Tue, 07/17/2018 - 07:49

This weeks tutorial will dive into how you can add page templates for a specific content type in Drupal 8. Sometimes you need to create a page template for a specific content type so that you can customise it. Drupal allows you to create content types for node templates out of the box by following the naming convention node--content-type.html.twig. But things aren’t so simple for page templates. Drupal does not automatically detect page templates for content types purely based on the naming convention. Fortunately it just takes a few lines of code and you can create a page template for any content type you choose....

Mark Shropshire: Demystifying Decoupled Drupal with Contenta CMS Presentation at Drupal Camp Asheville

Main Drupal Feed - Tue, 07/17/2018 - 02:24

It was a pleasure to present "Demystifying Decoupled Drupal with Contenta CMS" with Bayo Fodeke at Drupal Camp Asheville 2018 on July 14th, 2018. I want to thank the organizers, volunteers, attendees, presenters, and sponsors for making another awesome year in the beautiful North Carolina mountains. This is one great camp that gets better and better each year. Below you will find the video for my talk and slide deck::

"Demystifying Decoupled Drupal with Contenta CMS".

Blog Category: 

WPTavern: New WordPress Feature Plugin Adds Support for Progressive Web Apps

Wordpress Planet - Tue, 07/17/2018 - 00:16

WordPress contributors are working on getting support for Progressive Web Apps (PWA) into core. A new PWA feature plugin is now available on WordPress.org, spearheaded by the teams at XWP, Google, and Automattic.

Progressive Web Apps are applications that run on the web but provide a speedy app-like experience inside a mobile browser. Google describes them as having the following three qualities:

  • Reliable – Load instantly and never show the downasaur, even in uncertain network conditions
  • Fast – Respond quickly to user interactions with silky smooth animations and no janky scrolling
  • Engaging – Feel like a natural app on the device, with an immersive user experience

The plugin adds support for technologies that PWAs require, including Service Workers, a Web App Manifest, and HTTPS. These technologies support functions like background syncing, offline content, push notifications, mobile home screen icon, and other PWA features.

XWP CTO Weston Ruter said the purpose of the feature plugin is to curate PWA capabilities for proposed merging into core. The idea is to merge them piece by piece. Core tickets are already in process for adding support for web app manifests and support for service workers, as well as bringing improvements to HTTPS.

“This PWA feature plugin is intended to equip and facilitate other plugins which implement PWA features,” Ruter said. “It’s not intended to negate any existing plugins with these features, but rather to allow such plugins (and themes) to work together seamlessly and expand upon them.”

The first release of the plugin on WordPress.org (v0.1.0) adds support for web app manifests and initial support for allowing theme and plugin developers to register scripts for service workers via wp_register_service_worker(). It also includes an API for detecting whether HTTPS is available.

“A next step for service workers in the PWA feature plugin is to integrate Workbox to provide a declarative WordPress PHP abstraction for managing the caching strategies for routes, with support for detecting conflicts,” Ruter said. Anyone who is interested to contribute to PWA support for WordPress can check out the discussions and plugin on GitHub.

In the past, app-like experiences were only available for sites and services that had their own native mobile apps, but native apps can be costly to develop and maintain. Progressive web apps use the greater web as their platform and are quick to spin up. They make content easier to access on mobile even without an internet connection. It’s also far easier to tap a home screen icon than to enter a URL on mobile, and this makes users more likely to engage with their favorite sites.

PWA Stats is a site that features case studies of progressive web apps that have significantly increased performance, engagement, and conversion. A few compelling examples include:

PWA support in WordPress will enable the plugin and theme ecosystems to work together in providing site owners with more engaging ways to connect with their visitors. Once the market starts building on core support, site owners should soon be able to offer better experiences for mobile users without having to become experts in the technologies that power progressive web apps.

Drupal core announcements: Drupal 8.6.0 will be released September 5; alpha begins week of July 16

Main Drupal Feed - Mon, 07/16/2018 - 15:20
Drupal 8.6.0-alpha1 will be released the week of July 16

In preparation for the minor release, Drupal 8.6.x will enter the alpha phase the week of July 16, 2018. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release. (More information on alpha and beta releases.)

  • Developers and site owners can begin testing the alpha next week.

  • The 8.7.x branch of core has been created, and future feature and API additions will be targeted against that branch instead of 8.6.x. All outstanding issues filed against 8.6.x will be automatically migrated to 8.7.

  • All issues filed against 8.5.x will then be migrated to 8.6.x, and subsequent bug reports should be targeted against the 8.6.x branch.

  • During the alpha phase, core issues will be committed according to the following policy:

    1. Most issues that are allowed for patch releases will be committed to 8.6.x and 8.7.x.

    2. Drupal 8.5.x will receive only critical bugfixes in preparation for its final patch release window on August 1. (Drupal 8.4.x and older versions are not supported anymore and changes are not made to those branches.)

    3. Most issues that are only allowed in minor releases will be committed to 8.7.x only. A few strategic issues may be backported to 8.7.x, but only at committer discretion after the issue is fixed in 8.7.x (so leave them set to 8.7.x unless you are a committer), and only up until the beta deadline.

Drupal 8.6.0-beta1 will be released the week of July 29

Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.

The release candidate phase will begin the week of August 13, and we will post further details at that time. See the summarized key dates in the release cycle, allowed changes during the Drupal 8 release cycle, and Drupal 8 backwards compatibility and internal API policy for more information.

Dev Blog: Quarterly Updates | Q2 2018

Wordpress Planet - Mon, 07/16/2018 - 14:50

To keep everyone aware of big projects and efforts across WordPress contributor teams, I’ve reached out to each team’s listed representatives. I asked each of them to share their Top Priority (and when they hope for it to be completed), as well as their biggest Wins and Worries. Have questions? I’ve included a link to each team’s site in the headings.

Accessibility
  • Contacted: @rianrietveld, @joedolson, @afercia
  • Priority: Working to make sure that Gutenberg is reasonably accessible prior to merge. ETA is before 5.0
  • Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. The team is doing outreach to help solve this problem.
  • Big Win: Interest from companies like The Paciello Group and Tenon.io to help out with Gutenberg code review and testing tools.
CLI
  • Contacted: @danielbachhuber, @schlessera
  • Priority: Very first global Hack Day is coming up July 20. Version 2.0.0 is still in progress (new ETA is end of July).
  • Struggle: The team continues to need new contributors. The current team is tiny but tough.
  • Big Win: WP-CLI is currently one of the project’s four main focuses, as mentioned in the Summer Update at WordCamp Europe.
Community
  • Contacted: @francina, @hlashbrooke
  • Priority: Focusing on smoothing out the processes in our community management by building up our team of volunteers and establishing what tools we need to keep things running well. ETA is ongoing.
  • Struggle: Our two biggest struggles at the moment are tracking what we need to get done, and making final decisions on things. There is current work on the tools available to assist with tracking progress.
  • Big Win: After making a concerted effort to get more contributors on the Community Team, we now have a much larger group of volunteers working as deputies and WordCamp mentors
Core
  • Contacted: @jeffpaul
  • Priority: Following the WordCamp Europe summer update (and the companion post here), the team is getting Gutenberg (the new WordPress editing experience) into a strong state for the 5.0 release. Potential ETA as soon as August.
  • Struggle: Coordinating momentum and direction as we start seeing more contributors offering their time. Still working our way through open issues. The team is starting multiple bug scrubs each week to work through these more quickly and transparently.
  • Big Win: Had a sizable release in 4.9.6 which featured major updates around privacy tools and functionality in Core.
Design
  • Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski
  • Priority: Better on-boarding of new contributors, especially creating better documentation. ETA is end of July.
  • Struggle: It’s hard to identify reasonably small tasks for first-time contributors.
  • Big Win: The team is much more organized now which has helped clear out the design backlog, bring in new contributors, and also keep current contributors coming back. Bonus: Joshua Wold will co-lead the upcoming release.
Documentation
  • Contacted: @kenshino
  • Priority: Opening up the work on HelpHub to new contributors and easing the onboarding process. No ETA.
  • Struggle: Some blockers with making sure the code and database can be ready to launch on https://wordpress.org/support/
  • Big Win: The first phase of HelpHub creation is complete, which means content updates (current info, more readable, easier discovery), internal search, design improvements, and REST API endpoints.
Hosting
  • Contacted: @mikeschroder, @jadonn
  • Priority: Preparing hosts for supporting Gutenberg, especially support questions they’re likely to see when the “Try Gutenberg” callout is released. ETA July 31st, then before WordPress 5.0
  • Struggle: Most contributions are still made a by a small team of volunteers. Seeing a few more people join, but progress is slow.
  • Big Win: New team members and hosting companies have joined the #hosting-community team and have started contributing.
Marketing
  • Contacted: @bridgetwillard
  • Priority: Continuing to write and publish case studies from the community. ETA is ongoing.
  • Struggle: No current team struggles.
  • Big Win: Wrote and designed a short Contributor Day onboarding card. It was used at Contributor Day at WCEU and onboarding time went down to 1 hour instead of 3 hours.
Meta (WordPress.org Site)
  • Contacted: @tellyworth, @coffee2code
  • Priority: Reducing manual work around the contributor space (theme review, GDPR/privacy, plugin review). ETA for small wins is end of quarter, larger efforts after that.
  • Struggle: Maintaining momentum on tickets. There are also some discussions about updating the ticket management process across teams that use the Meta trac system.
  • Big Win: The new About page launched and has been translated across most locale sites.
Mobile
  • Contacted: @elibud
  • Priority: Getting Gutenberg in the mobile applications. ETA is late December.
  • Struggle: Consuming the Gutenberg source in the ReactNative app directly. More info can be found here: https://make.wordpress.org/mobile/2018/07/09/next-steps-for-gutenberg-mobile/
  • Big Win: The WordPress mobile applications now fully support right-to-left languages and are compliant with the latest standards for accessibility.
Plugins
  • Contacted: @ipstenu
  • Priority: Clearing ~8,000 unused plugins from the queues. Likely ETA is September.
  • Struggles: Had to triage a lot of false claims around plugins offering GDPR compliance.
  • Big Win: Released 4.9.6 and updated expectations with plugin authors. Huge thanks to the Core Privacy team for their hard work on this.
Polyglots
  • Contacted: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa
  • Priority: Keep WordPress releases translated to 100% and then concentrate on the top 100 plugins and themes. ETA is ongoing.
  • Struggle: Getting new PTEs fast enough, and complex tools/systems. Overall, the volume of strings awaiting approval.
Support
  • Contacted: @clorith
  • Priority: Getting ready for the Gutenberg callout (it got pushed last quarter). Needing a better presence on the official support forums, and outreach for that is underway, ETA end of July. 
  • Struggle: Keeping contributors participating post-contributor days/drives. Considering the creation of a dedicated post-contributor day survey to get some insight here.
  • Big Win: The increase in international liaisons joining for weekly meetings, helping bring the wider support community together.
Theme Review Tide
  • Contacted: @valendesigns (but usually @jeffpaul)
  • Priority: Storing PHPCompatibilty results inside the WordPress.org API and building a UI to display those results, an endpoint to request an audit is required for this work to continue.
  • Struggle: Development has dramatically slowed down while team members are on leave or pulled into internal client work.
  • Big Win: Migration to Google Cloud Platform (GCP) from Amazon Web Services (AWS) is complete and the audit servers have all been rewritten in Go. (This allows us to be faster with greater capacity and less cost.)
Training
  • Contacted: @bethsoderberg, @juliek
  • Priority: Lesson plan production. ETA is ongoing.
  • Struggle: The workflow is a little complex, so recruiting and training enough contributors to keep the process moving is a struggle.
  • Big Win: WordCamp Europe’s Contributor Day was very productive. New tools/workflow are in place and two team representatives were there to lead and help.

Interested in updates from the first quarter of this year? You can find those here: https://make.wordpress.org/updates/2018/04/24/quarterly-updates-q1-2018/

Quarterly Updates | Q2 2018

Wordpress News - Mon, 07/16/2018 - 14:50

To keep everyone aware of big projects and efforts across WordPress contributor teams, I’ve reached out to each team’s listed representatives. I asked each of them to share their Top Priority (and when they hope for it to be completed), as well as their biggest Wins and Worries. Have questions? I’ve included a link to each team’s site in the headings.

Accessibility
  • Contacted: @rianrietveld, @joedolson, @afercia
  • Priority: Working to make sure that Gutenberg is reasonably accessible prior to merge. ETA is before 5.0
  • Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. The team is doing outreach to help solve this problem.
  • Big Win: Interest from companies like The Paciello Group and Tenon.io to help out with Gutenberg code review and testing tools.
CLI
  • Contacted: @danielbachhuber, @schlessera
  • Priority: Very first global Hack Day is coming up July 20. Version 2.0.0 is still in progress (new ETA is end of July).
  • Struggle: The team continues to need new contributors. The current team is tiny but tough.
  • Big Win: WP-CLI is currently one of the project’s four main focuses, as mentioned in the Summer Update at WordCamp Europe.
Community
  • Contacted: @francina, @hlashbrooke
  • Priority: Focusing on smoothing out the processes in our community management by building up our team of volunteers and establishing what tools we need to keep things running well. ETA is ongoing.
  • Struggle: Our two biggest struggles at the moment are tracking what we need to get done, and making final decisions on things. There is current work on the tools available to assist with tracking progress.
  • Big Win: After making a concerted effort to get more contributors on the Community Team, we now have a much larger group of volunteers working as deputies and WordCamp mentors
Core
  • Contacted: @jeffpaul
  • Priority: Following the WordCamp Europe summer update (and the companion post here), the team is getting Gutenberg (the new WordPress editing experience) into a strong state for the 5.0 release. Potential ETA as soon as August.
  • Struggle: Coordinating momentum and direction as we start seeing more contributors offering their time. Still working our way through open issues. The team is starting multiple bug scrubs each week to work through these more quickly and transparently.
  • Big Win: Had a sizable release in 4.9.6 which featured major updates around privacy tools and functionality in Core.
Design
  • Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski
  • Priority: Better on-boarding of new contributors, especially creating better documentation. ETA is end of July.
  • Struggle: It’s hard to identify reasonably small tasks for first-time contributors.
  • Big Win: The team is much more organized now which has helped clear out the design backlog, bring in new contributors, and also keep current contributors coming back. Bonus: Joshua Wold will co-lead the upcoming release.
Documentation
  • Contacted: @kenshino
  • Priority: Opening up the work on HelpHub to new contributors and easing the onboarding process. No ETA.
  • Struggle: Some blockers with making sure the code and database can be ready to launch on https://wordpress.org/support/
  • Big Win: The first phase of HelpHub creation is complete, which means content updates (current info, more readable, easier discovery), internal search, design improvements, and REST API endpoints.
Hosting
  • Contacted: @mikeschroder, @jadonn
  • Priority: Preparing hosts for supporting Gutenberg, especially support questions they’re likely to see when the “Try Gutenberg” callout is released. ETA July 31st, then before WordPress 5.0
  • Struggle: Most contributions are still made a by a small team of volunteers. Seeing a few more people join, but progress is slow.
  • Big Win: New team members and hosting companies have joined the #hosting-community team and have started contributing.
Marketing
  • Contacted: @bridgetwillard
  • Priority: Continuing to write and publish case studies from the community. ETA is ongoing.
  • Struggle: No current team struggles.
  • Big Win: Wrote and designed a short Contributor Day onboarding card. It was used at Contributor Day at WCEU and onboarding time went down to 1 hour instead of 3 hours.
Meta (WordPress.org Site)
  • Contacted: @tellyworth, @coffee2code
  • Priority: Reducing manual work around the contributor space (theme review, GDPR/privacy, plugin review). ETA for small wins is end of quarter, larger efforts after that.
  • Struggle: Maintaining momentum on tickets. There are also some discussions about updating the ticket management process across teams that use the Meta trac system.
  • Big Win: The new About page launched and has been translated across most locale sites.
Mobile
  • Contacted: @elibud
  • Priority: Getting Gutenberg in the mobile applications. ETA is late December.
  • Struggle: Consuming the Gutenberg source in the ReactNative app directly. More info can be found here: https://make.wordpress.org/mobile/2018/07/09/next-steps-for-gutenberg-mobile/
  • Big Win: The WordPress mobile applications now fully support right-to-left languages and are compliant with the latest standards for accessibility.
Plugins
  • Contacted: @ipstenu
  • Priority: Clearing ~8,000 unused plugins from the queues. Likely ETA is September.
  • Struggles: Had to triage a lot of false claims around plugins offering GDPR compliance.
  • Big Win: Released 4.9.6 and updated expectations with plugin authors. Huge thanks to the Core Privacy team for their hard work on this.
Polyglots
  • Contacted: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa
  • Priority: Keep WordPress releases translated to 100% and then concentrate on the top 100 plugins and themes. ETA is ongoing.
  • Struggle: Getting new PTEs fast enough, and complex tools/systems. Overall, the volume of strings awaiting approval.
Support
  • Contacted: @clorith
  • Priority: Getting ready for the Gutenberg callout (it got pushed last quarter). Needing a better presence on the official support forums, and outreach for that is underway, ETA end of July. 
  • Struggle: Keeping contributors participating post-contributor days/drives. Considering the creation of a dedicated post-contributor day survey to get some insight here.
  • Big Win: The increase in international liaisons joining for weekly meetings, helping bring the wider support community together.
Theme Review Tide
  • Contacted: @valendesigns (but usually @jeffpaul)
  • Priority: Storing PHPCompatibilty results inside the WordPress.org API and building a UI to display those results, an endpoint to request an audit is required for this work to continue.
  • Struggle: Development has dramatically slowed down while team members are on leave or pulled into internal client work.
  • Big Win: Migration to Google Cloud Platform (GCP) from Amazon Web Services (AWS) is complete and the audit servers have all been rewritten in Go. (This allows us to be faster with greater capacity and less cost.)
Training
  • Contacted: @bethsoderberg, @juliek
  • Priority: Lesson plan production. ETA is ongoing.
  • Struggle: The workflow is a little complex, so recruiting and training enough contributors to keep the process moving is a struggle.
  • Big Win: WordCamp Europe’s Contributor Day was very productive. New tools/workflow are in place and two team representatives were there to lead and help.

Interested in updates from the first quarter of this year? You can find those here: https://make.wordpress.org/updates/2018/04/24/quarterly-updates-q1-2018/

Dropsolid: Our Dropsolid CTO featured on the Modern CTO Podcast

Main Drupal Feed - Mon, 07/16/2018 - 11:29
16 Jul Our Dropsolid CTO featured on the Modern CTO Podcast Nick Veenhof Drupal Drupal conferenties

Recently, I was invited to go on the Modern CTO podcast as a guest. We talked about developer culture, how to measure efficiency and velocity and, more importantly, how you can make the teams as independent as possible without losing that team and company feeling.

Modern CTO is the place where CTOs hang out. Listen in on our weekly podcast while we hang out with interesting Fortune 500 CTO’s in Aerospace, Artificial Intelligence, Robotics + Many more industries. As of 2018: 72k listeners we are incredibly grateful to each and everyone one of you.

It was a real honour to talk to Joel Beasley and have this back-and-forth conversation about how we transformed Dropsolid into a great place to work, but measurable and technically innovative!

 

 

Some of the topics that we talked about in the podcast were also seen at the presentation I gave at Drupal Developer Days in Lisbon.  Feel free to scroll through the slides to get more context out of the podcast!

 

Drupal Developer Days - One Flew Over The Developers Nest 2018 by Nick Veenhof

OpenSense Labs: Use Elasticsearch to Indexing in Drupal

Main Drupal Feed - Mon, 07/16/2018 - 08:59
Use Elasticsearch to Indexing in Drupal Raman Mon, 07/16/2018 - 14:29

Modern applications are expected to be equipped with powerful search engines. Drupal provides a core search module that is capable of doing a basic keyword search by querying the database. When it comes to storing and retrieving data, databases are very efficient and reliable. They can be also used for basic filtering and aggregating of data. However, they are not very efficient when it comes to searching for specific terms and phrases.


Performing inefficient queries on large sets of data can result in a poor performance. Moreover, what if we want to sort the search results according to their relevance, implement advanced searching techniques like autocompletion, full-text, fuzzy search or integrate search with RESTful APIs to build a decoupled application?

This is where dedicated search servers come into the picture. They provide a robust solution to all these problems. There are a few popular open-source search engines to choose from, such as Apache Solr, Elasticsearch, and Sphinx. When to use which one depends on your needs and situation, and is a discussion for another day. In this article, we are going to explore how we can use Elasticsearch for indexing in Drupal.

What is Elasticsearch?

Elasticsearch is a highly scalable open-source full-text search and analytics engine. It allows you to store, search, and analyze big volumes of data quickly and in near real time.” – elastic.co 

It is a search server built using Apache Lucene, a Java library, that can be used to implement advanced searching techniques and perform analytics on large sets of data without compromising on performance.

“You Know, for Search”

It is a document-oriented search engine, that is, it stores and queries data in JSON format. It also provides a RESTful interface to interact with the Lucene engine. 

Many popular communities including Github, StackOverflow, and Wikipedia benefit from Elasticsearch due to its speed, distributed architecture, and scalability.

Downloading and Running Elasticsearch server

Before integrating Elasticsearch with Drupal, we need to install it on our machine. Since it needs Java, make sure you have Java 8 or later installed on the system. Also, the Drupal module currently supports the version 5 of Elasticsearch, so download the same.

  • Download the archive from its website and extract it
$ wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.6.10.tar.gz $ tar -zxvf elasticsearch-5.6.10.tar.gz
  • Execute the “elasticsearch” bash script located inside the bin directory. If you are on Windows, execute the “elasticsearch.bat” batch file
$ elasticsearch-5.6.10/bin/elasticsearch

The search server should start running on port 9200 port of localhost by default. To make sure it has been set up correctly, make a request at http://localhost:9200/ 

$ curl http://localhost:9200

If you receive the following response, you are good to go

{   "name" : "hzBUZA1",   "cluster_name" : "elasticsearch",   "cluster_uuid" : "5RMhDoOHSfyI4a9s78qJtQ",   "version" : {     "number" : "5.6.10",     "build_hash" : "b727a60",     "build_date" : "2018-06-06T15:48:34.860Z",     "build_snapshot" : false,     "lucene_version" : "6.6.1"   },   "tagline" : "You Know, for Search" }

Since Elasticsearch does not do any access control out of the box, you must take care of it while deploying it.

Integrating Elasticsearch with Drupal

Now that we have the search server up and running, we can proceed with integrating it with Drupal. In D8, it can be done in two ways (unless you build your own custom solution, of course).

  1. Using Search API and Elasticsearch Connector
  2. Using Elastic Search module
Method 1: Using Search API and Elasticsearch Connector

We will need the following modules.

However, we also need two PHP libraries for it to work – des-connector and php-lucene. Let us download them using composer as it will take care of the dependencies.

$ composer require 'drupal/elasticsearch_connector:^5.0' $ composer require 'drupal/search_api:^1.8'

Now, enable the modules either using drupal console, drush or by admin UI.

$ drupal module:install elasticsearch_connector search_api

or

$ drush en elasticsearch_connector search_api -y

You can verify that the library has been correctly installed from Status reports available under admin/reports/status.

Viewing the status of the library under Status ReportsConfiguring Elasticsearch Connector

Now, we need to create a cluster (collection of node servers) where all the data will get stored or indexed.

  1. Navigate to Manage → Configuration → Search and metadata → Elasticsearch Connector and click on “Add cluster” button
  2. Fill in the details of the cluster. Give an admin title, enter the server URL, optionally make it the default cluster and make sure to keep the status as Active.Adding an Elasticsearch Cluster
  3. Click on “Save” button to add the cluster
Adding a Search API server

In Drupal, Search API is responsible for providing the interface to a search server. In our case, it is the Elasticsearch. We need to make the Search API server to point to the recently created cluster.

  1. Navigate to Manage → Configuration → Search and metadata → Search API and click on “Add server” button
  2. Give the server a suitable name and description. Select “Elasticsearch” as the backend and optionally adjust the fuzzinessAdding a Search API server
  3. Click on “Save” to add the serverViewing the status of the newly added server
Creating a Search API Index and adding fields to it

Next, we need to create a Search API index. The terminologies used here can be a bit confusing. The Search API index is basically an Elasticsearch Type (and not Elasticsearch index). 

  1. On the same configuration page, click on “Add Index” button
  2. Give an administrative name to the index. Select the entities in the data sources which you need to indexAdding the data sources of the search index
  3. Select the bundles and language to be indexed while configuring the data source, and also select the indexing order.Configuring the added data sources
  4. Next, select the search API server, check enabled. You may want to disable the immediate indexing. Then, click on “Save and add fields”Configuring the search index options
  5. Now, we need to add the fields to be indexed. These fields will become the fields of the documents in our Elasticsearch index. Click on the “Add field” button.
  6. Click on “Add” button next to the field you wish to add. Let’s add the title and click on “Done”Adding the required fields to the index
  7. Now, configure the type of the field. This can vary with your application. If you are implementing a search functionality, you may want to select “Full-text”Customizing the fields of the index
  8. Finally, click on “Save Changes”
Processing of Data

This is an important concept of how a search engine works. We need to perform certain operations on data before indexing it into the search server. For example, consider an implementation of a simple full-text search bar in a view or a decoupled application. 

  1. To implement this, click on the “Processors” tab. Enable the following and arrange them in this order.
    1. Tokenization: Split the text into tokens or words
    2. Lower Casing: Change the case of all the tokens into lower
    3. Removing stopwords: Remove the noise words like ‘is’, ‘the’, ‘was’, etc
    4. Stemming: Chop off or modify the end of words like  ‘–-ing’, ‘–uous’, etc

      Along with these steps, you may enable checks on Content access, publishing status of the entity and enable Result Highlighting
  2. Scroll down to the bottom, arrange the order and enable all the processes from their individual vertical tabs.Arranging the order of Processors
  3. Click on “Save” to save the configuration.

Note that the processes that need to be applied can vary on your application. For example, you shouldn’t remove the stopwords if you want to implement Autocompletion.

Indexing the content items

By default, Drupal cron will do the job of indexing whenever it executes. But for the time being, let’s index the items manually from the “View” tab.

Indexing the content items

Optionally alter the batch size and click on “Index now” button to start indexing.

Wait for the indexing to finish

Now, you can view or browse the created index using the REST interface or a client like Elasticsearch Head or Kibana. 

$ curl http://localhost:9200/elasticsearch_drupal_content_index/_search?pretty=true&q=*:* Creating a view with full-text search

You may create a view with the search index or use the REST interface of Elasticsearch to build a decoupled application.

Example of a full-text search using Drupal viewMethod 2: Using Elastic Search module

As you may notice, there is a lot of terminology mismatch between Search API and Elasticsearch’s core concepts. Hence, we can alternatively use this method.

For this, we will need the Elastic Search module and 3 PHP libraries – elasticsearch, elasticsearch-dsl, and twlib. Let’s download the module using composer.

$ composer require 'drupal/elastic_search:^1.2'

Now, enable it either using drupal console, drush or by admin UI.

$ drupal module:install elastic_search

or

$ drush en elastic_search -y Connecting to Elasticsearch Server

First, we need to connect the module with the search server, similar to the previous method.

  1. Navigate to Configuration → Search and metadata → Elastic Server
  2. Select HTTP protocol, add the elastic search host and port number, and optionally add the Kibana host. You may also add a prefix for indices. Rest of the configurations can be left at defaults.Adding the Elasticsearch server
  3. Click on “Save configurations” to add the server
Generating mappings and configuring them

A mapping is essentially a schema that will define the fields of the documents in an index. All the bundles of entities in Drupal can be mapped into indices.

  1. Click on “Generate mappings”
  2. Select the entity type, let’s say node. Then select its bundles. Optionally allow mapping of its childrenAdding the entity and selecting its bundles to be mapped
  3. Click on “Submit” button. It will automatically add all the fields, you may want to keep only the desired fields and configure them correctly. Their mapping DSL can also be exported.Configuring the fields of a bundle
Generating index and pushing the documents

Now, we can push the indices and the required documents to the search server.

  1. For that, move on to the indices tab, click on “Generate New Elastic Search Indices” and then click on “Push Server Indices and Mappings”. This will create all the indices on the server.
  2. Now index all the nodes using “Push All Documents”. You may also push the nodes for a specific index. Wait for the indexing to finish.Managing the indices using the admin UI
Conclusion

Drupal entities can be indexed into the Elasticsearch documents, which can be used to create an advanced search system using Drupal views or can be used to build a decoupled application using the REST interface of Elasticsearch. 
While Search API provides an abstract approach, the Elastic Search module follows the conventions and principles of the search engine itself to index the documents. Either way, you can relish the flexibility, power, and speed of Elasticsearch to build your desired solution.

blog banner blog image Blog Type Tech Is it a good read ? On

Agiledrop.com Blog: AGILEDROP: Drupal community interview - Renato Goncalves de Araújo

Main Drupal Feed - Sun, 07/15/2018 - 23:20
Agiledrop is highlighting active Drupal community members through a series of interviews. Learn who are the people behind Drupal projects. This week we talked with Renato Goncalves de Araújo. Read about what are the two things he loves about Drupal, what he thinks the future will bring for Drupal, and what are projects he is involved into.    1. Please tell us a little about yourself. How do you participate in the Drupal community and what do you do professionally? About me: I have been a software developer for eleven years now. I studied Computer Science at the University of Campinas (… READ MORE

Axelerant Blog: Drupal Dev Days Lisbon 2018: Retrospectives

Main Drupal Feed - Sat, 07/14/2018 - 04:18


Drupal Developer Days Lisbon
was valuable, nicely organized, and full of energy. Two Axelerant team members attended to contribute a workshop and a session on two key topics, and they wanted to share key highlights with you, to thank the volunteers, and to encourage more developers from around the world to make it in 2019.

WPTavern: WordCamp Europe 2018 Draws 2,085 Attendees, Organizers Look Ahead to 2019 in Berlin

Wordpress Planet - Sat, 07/14/2018 - 00:24
photo credit: WCEU Photography Team

WordCamp Europe closed out a successful event in Belgrade with 2,085 attendees from 76 countries. More than 800 others joined via livestream for a total audience of nearly 3,000 participants. A record-setting Contributor Day kicked off the event, followed by two days of conference sessions and workshops from 65 speakers.

A team of 54 organizers and 170 volunteers made WCEU possible, with 10 different organizing teams. Last year WordCamp Europe added a PR team and this year the event introduced an Attendee Services team to fill gaps in the organization. The operation ran smoothly, despite the conference being spread out across many rooms in the sprawling Sava Centar venue.

WordCamp Europe’s PWA (progressive web app) was the highlight of the new features and services introduced this year. It was a central hub for keeping attendees informed on what was happening at any given moment. Organizers also added new amenities, including a site health check station, Community Room, and info booth to handle attendee questions.

Gutenberg and Progressive web apps were the hot topics of this year’s WordCamp Europe. In addition to Matt Mullenweg unveiling a roadmap for Gutenberg’s inclusion in core, a strong contingent of designers and engineers from the team were present to educate attendees on Gutenberg’s architecture and the vision behind the project.

Many attendees were visiting Serbia for the first time and Belgrade delivered with its renowned hospitality and captivating nightlife. Attendees found no shortage of delicious options for food and drink.

Berlin to Host WordCamp Europe 2019

At the conclusion of the event, organizers announced Berlin as the next host city for WordCamp Europe, June 20-22, 2019. The conference, Contributor Day, and the after party will all be held at the Estrel Hotel and Congress Center, a venue with a capacity for 12,000 attendees.

Organizers said that Berlin’s accessibility, reasonable prices, and strong community were the final deciding factors for its selection as the next host city.

Behind the Scenes at WordCamp Europe 2018 with Lead Organizers Jenny Beaumont and Milan Ivanović

Hosting a volunteer-led event at this scale requires an enormous amount of effort from the organizers, especially those taking the lead for multiple years in a row. There is nearly no down time as the team is already planning for the next edition of the camp.

I sat down with lead organizers Jenny Beaumont, the global lead, and Milan Ivanović, the local lead, to get a look behind the scenes at what is involved in bringing WordCamp Europe to thousands of WordPress enthusiasts in one weekend. We interviewed them at the conclusion of WCEU 2017 in Paris. Over the past two years these leaders have developed a strong working relationship built on encouraging each other and keeping a positive outlook for their teams.

Beaumont said she was hesitant going into a third year for this role, as Paris was the project that captured her heart and motivation. After going through this event as the global lead, she said she discovered what she could bring to the role and how she could serve the team.

“The event has been their project,” Beaumont said. “My project this year has been the team, how I can really concentrate on this team, on its growth, on its health, on its sustainability. That’s what I learned in Paris – the importance of making sure that was part of the project.”

Beaumont and Ivanović explained the difference between the global and local lead roles, a structure that works well for flagship WordCamps.

“The local team is really about making it a good experience in this new place that everybody is going to be discovering for the first time,” Beaumont said. “It’s the hard work, it’s the logistics, it’s all of the small details, everything that’s behind the scenes that make it so you walk in as an attendee and it just feels like you’re at home. They do all of that hard work. The global role, as it has evolved, is really about being that sort of team care-giver, making sure that there is good communication happening, making sure the team is healthy and happy and motivated. Because you’ve got to get up and do this every day while you’re also doing your day job, and that takes a lot.”

WordCamp Europe had a strong impact on the local community with more than 400 Serbian attendees and 20 Serbian organizers. They worked to build awareness of WordPress in the local community ahead of the event.

“We used this event to grow our community and used our community to promote the event,” Ivanović said. “When we announced last year in Paris that Belgrade is going to be next, at that time we had five or six cities for WordPress meetups. Currently, we are in 14 cities and starting the 15th in July. WordCamp Europe and the conference itself was such a win for the whole community.”

Ivanović will return next year as the global lead for WCEU in Berlin. Beaumont is taking some time off after three years organizing WordCamp Paris and WordCamp Europe, but she hopes to return in some capacity in the future. They are working together with their team to publish a WordCamp Europe handbook that covers some of the important specifics of the event for upcoming teams. Check out the full interview in the video below.

Drupal.org blog: What's new on Drupal.org? - June 2018

Main Drupal Feed - Fri, 07/13/2018 - 22:39

Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.

Announcements Last chance to vote in the Drupal Association board election

Elections for the Drupal Association board end on July 13th, 2018 at 5pm Pacific (in just over an hour at the time this is posted). There are nine candidates from 7 countries across six continents representing a wide variety of perspectives from the Drupal community. Anyone user who has been active in the last year and registered before the elections began is welcome to cast a ballot.

We encourage you to vote today and help guide the future of the Drupal Association.  

Reminder: Drupal Europe is coming up soon

Drupal Europe is coming up in less than 60 days! Drupal Europe will be the largest gathering of the Drupal community in Europe and is a reimagining of this important community event as both technical conference and family reunion. The Drupal Association engineering team will be attending to connect with the community, provide updates on Drupal.org, and listen to some of the incredible speakers who will be in attendance.

Join the community in Darmstadt, Germany from September 10-14, 2018. Make sure to register, book your travel, and secure accommodation: http://drupaleurope.org/

Project maintainers: Change your git remote configuration

Git authentication methods for Drupal.org hosted projects are changing as we approach upgrading our developer tooling stack. In particular we will be:

  • Deprecating password authentication for git

  • Deprecating the git remote format <username>@git.drupal.org/project/<yourproject>.git in favor of git@git.drupal.org:project/<yourproject>.git

We have updated the version control instructions for Drupal.org projects, and put a message in the git daemon for any user who makes a push using the deprecated format.

For more information, please review: https://drupal.org/gitauth

Drupal.org Updates Ecommerce industry page launched

Since last year, one of our ongoing initiatives has been to develop more content on Drupal.org focused on specific industries. Drupal is an incredible powerful tool for building ambitious digital experiences, but it's flexibility can sometimes be overwhelming. These industry specific pages help Drupal evaluators discover how Drupal can be tailored for their specific needs, and highlight successful case studies of Drupal in the wild.

The Drupal Association has launched our sixth industry page promoting the power of Drupal for Ecommerce. We want to thank Commerce Guys for their contributions to getting this page off the ground.

Display project screenshots in a more user friendly way

For every new Drupal project that a developer or site-builder undertakes, time is spent evaluating distributions, modules, and themes to find integrations that will accelerate launching the project.

To improve the user experience for users evaluating modules on Drupal.org, we've implemented a new lightbox-style display for project screenshots.

Here's an example of a screenshot from the Token project:

Granted more maintainers the ability to give contribution credit

Since the introduction of contribution credits at the end of 2015, they've become an important part of the way the Drupal community recognizes individual and organizational contributions to the project. The Drupal Association Engineering team regularly reviews the contribution credit system to make small tweaks and adjustments to make the experience even better.

For our most recent update, Drupal.org now grants all project maintainers with the 'maintain issues' permission the ability to grant contribution credit, instead of just those users with 'Write to Version Control' permissions. This means that a much wider group of maintainers can now participate in granting credit.

Showing maintainer photos on top level Docs guides

Documentation is critically important to the Drupal project To make it easier for potential contributors to find out who they should reach out to for issues that affect the top levels of documentation, we've added maintainer information to the top level documentation guides.

Email confirmation when creating an organization node

To help more organizations that work with Drupal join our community, we now send an email confirmation to any user who creates an organization profile with information about becoming listed as a service provider, details about the contribution credit system, and information about becoming a Drupal Association member or supporting partner.

We encourage everyone in the Drupal community to ask your clients to create a Drupal.org organization profile. Bringing end-users into the contribution journey will be a key part of Drupal's long term health and success.

Contributing to the Open Demographics Initiative

One of our goals on the Drupal Association engineering team is to adopt the Open Demographics Initiative in our user registration process. As part of our effort to work towards that goal, we have contributed a machine readable version of the demographic questions and and answers to the ODI project.

We're hopeful that can be reviewed and committed soon, and be used as the basis for an ODI Drupal module.

Security Improvements Added PSA and SAs to the /news feed

To increase the visibility of security notifications, Public Security Announcements and Security Advisories will now be included in the https://drupal.org/news feed.

Multi-value CVE field for Security Advisories

We've also updated the security advisory content type so that an advisory can be associated with multiple CVEs.

Infrastructure Updates DrupalCI: Converted core javascript tests to use Chrome driver

The DA Engineering team has worked together with Core to convert the Core javascript tests from using PhantomJS to using Chrome Webdriver. This provides much more powerful and better supported tools for javascript development in Drupal.

DrupalCI: Reduced disk space usage of the DrupalCI dispatcher

One of the most important services the Drupal Association provides for the project is DrupalCI, the suite of tools used to test all of Drupal's code. These tools are very powerful, but also expensive to maintain, and something we have to monitor carefully. In June, we spent some time automating disk space management for the DrupalCI dispatcher, to help reduce the maintenance cost of keeping it running smoothly.

———

As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who make it possible for us to work on these projects. In particular we want to thank:

  • OPIN - Renewing Signature Supporting Partner
  • Srijan - Renewing Signature Supporting Partner
  • Lullabot - Renewing Premium Supporting Partner
  • Aten - Renewing Premium Supporting Partner
  • Phase2 - Renewing Premium Supporting Partner
  • WebEnertia - *NEW* Premium Supporting Partner
  • Pantheon - Renewing Premium Hosting Supporter
  • Datadog - Renewing Premium Technology Supporter
  • Promet Source - Renewing Classic Supporting Partner
  • Evolving Web - Renewing Classic Supporting Partner
  • ImageX - Renewing Classic Supporting Partner
  • Adapt - Renewing Classic Supporting Partner
  • Green Geeks - Renewing Hosting Supporter
  • Microserve - Renewing Classic Supporting Partner
  • ThinkShout - Renewing Classic Supporting Partner
  • Amazee Labs - Renewing Classic Supporting Partner
  • Four Kitchens - Renewing Classic Supporting Partner
  • Access - Renewing Classic Supporting Partner
  • Appnovation - Renewing Classic Supporting Partner
  • Studio Present - Renewing Classic Supporting Partner
  • undpaul - Renewing Classic Supporting Partner
  • Position2 - Renewing Classic Supporting Partner
  • Blend Interactive - Renewing Classic Supporting Partner

If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.

Follow us on Twitter for regular updates: @drupal_org, @drupal_infra

Ashday's Digital Ecosystem and Development Tips: Omeda and Drupal: A Perfect Relationship (Manager)

Main Drupal Feed - Fri, 07/13/2018 - 19:00

As you may have figured out by now, Drupal is a great platform for 3rd party integrations. Whether it’s eSignatures with Hellosign, more sophisticated search with Solr, or a host of other options, Drupal works best when it’s not trying to reinvent every wheel and is instead used to leverage existing business tools by tying them all together into a robust and useful package. Today, we’re going to take a look at a new set of integration modules that Ashday has just contributed back to the Drupal community: Omeda, Omeda Subscriptions and Omeda Customers.

Palantir: Help Us Modernize the Admin UI of Drupal

Main Drupal Feed - Fri, 07/13/2018 - 18:16
Help Us Modernize the Admin UI of Drupal brandt Fri, 07/13/2018 - 13:16 Sarah Lowe Jul 13, 2018

Take this survey to help us make Drupal the best platform for content editors and managers to use everyday.

Help us modernize the admin UI of Drupal.

Do you use Drupal? Before working at Palantir, I used Drupal only once: to help a legacy client with their Drupal 6 website. They had a support contract with my company, so if they had an issue or question I would do my best to help them, even though the original team who built the site had moved on to other jobs, and even though my company focused on WordPress sites.

I remember scrutinizing every menu item of the admin section, trying to familiarize myself with the platform while careful not to misclick and mess up something on the client’s site. Some of the terms I could understand—users, taxonomy—but some were new or vague, and not very clear to their meaning such as nodes, views, and blocks. While I was able to help the client at the time, I felt Drupal was too obtuse of a platform for me.

Redesign planned for Drupal

Now that I’m at Palantir, and knowing Drupal is a bigger part of my job, I’m still struck by how user unfriendly the platform can be out-of-the box, especially to a non-developer. While add-on modules like Workbench and Content Moderation can mitigate some of this complexity, installing and configuring those requires specialized knowledge. From talking to current clients, I know that I’m not the only one who feels intimidated by Drupal’s default administrative interface.

The Drupal community is also aware of the high learning curve to Drupal, and is in the process of modernizing the look and feel of the admin experience to make it more intuitive. Given how big the changes are, it’s the perfect time to include the people who work with Drupal every day to make sure Drupal is a system everyone feels comfortable using.

Therefore, I am working with fellow Palantir web strategist Michelle Jackson, Drupal front-end designer Cristina Chumillas, co-founder and front-end lead at Evolving Web Suzanne Dergacheva, project manager Antonella Severo, design consultant Roy Scholten, folks from the Drupal Association and other interested volunteers to conduct research on popular content management systems and web platforms such as Drupal, WordPress, Squarespace, and Joomla in order to learn how best to update Drupal.

Here’s where you come in

We want to make Drupal the best platform for content editors and managers to use everyday. Therefore, if your job involves updating the company blog, swapping out images, tagging content to group related information, or some other way you interact with your website, we want to hear from you.

We put together a quick, 5-10 minute survey that asks about your general familiarity with Drupal. For example, we want to know common tasks you perform on the platform as well as frustrating pain points. This way we can target our redesign efforts to make Drupal work better for you.

In addition to the opportunity to shape the future of Drupal, at the end of the survey you’ll have the opportunity to enter into a drawing for two great prizes: 1 full conference ticket to the (new) DrupalCon Content Marketing track at DrupalCon Seattle 2019 - $695 value (flight and hotel not included), or 1 two-day, online Drupal 8 training session from fellow Drupal agency Evolving Web.

Take the Survey So what happens next?

This survey is step one of our research efforts. After reviewing the common tasks, we’ll ask folks who had provided their email address if they are willing to participate in card sort exercises to determine the best label for grouping common tasks together. Next we’ll design solutions to address the biggest pain points and ask participants to validate our assumptions through usability tests.

Looking at the long term, we are interested in comparing Drupal with other popular systems such as WordPress and Squarespace. We plan to reach out to people who use those platforms to find out what they find easy or difficult about them, which may inform the direction of the Drupal redesign. No matter which direction our research takes, we want to ensure we’re building a product with you, the content editor, in mind.

More ways to help

We want to make the new Drupal as intuitive as can be on a global scale, but as a small team of volunteers, there’s only so much we can do on our own. If you develop or design for Drupal, and are interested in our research efforts, there are a number of ways to get involved. First, check out the Admin UI and JavaScript Modernization initiative on Drupal.org. Then, reach out to us on the #admin-ui channel on Slack. We can show you how to copy the survey so you can run your own tests. We’re especially grateful if you’re able to translate it and test users in Africa, Asia, and Latin America.

It shouldn’t take specialized knowledge to update and maintain a website on Drupal. With your help, we can make Drupal a more approachable platform for content editors. I can’t wait to hear from you!

Community Drupal People

Pages