Drupal Planet

Subscribe to Drupal Planet feed
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 4 hours 13 min ago

wishdesk.com: A simple tour on using Drupal 8 Views contextual filters

April 4, 2019 - 20:06

Views added to Drupal core is one of the most frequently mentioned Drupal 8 benefits. Drupal Views gives us a UI for creating data collections based on any desired criteria. One of the ways to fine-tune the results is to use Drupal Views filters. A level higher from regular filters stand contextual filters that accept dynamic values. This helps us create flexible and interesting solutions. Let’s review Drupal 8 Views contextual filters in more detail.

Agiledrop.com Blog: 6 remote staffing challenges and how to tackle them

April 4, 2019 - 17:07

Due to the constantly evolving nature of the digital, outsourcing has become a very viable solution for managing projects. But, naturally, outsourcing work to remote partners brings about its own unique challenges. In this post, we'll take a look at some of the biggest challenges of remote staffing and the ways to tackle them.

READ MORE

Web Wash: Create Pages using Gutenberg (WordPress Editor) in Drupal 8

April 4, 2019 - 17:00

Gutenberg is the new editor for WordPress 5.0. It’s a new style of editor/page builder. Instead of writing text in a single text area, you build a page using blocks. A block could be something simple such as a paragraph or an image. Or more complex blocks like a “Media & Text” or adding in columns.

The editor itself is written in Javascript, more specifically React. This is what makes it possible to be used in Drupal. But I’m sure extra works was required to get it working in Drupal.

In this tutorial, you’ll learn to install and configure the Gutenberg module, and you’ll learn how to use it on the Page content type.

If you’re keen to have a play with the editor without configuring a Drupal site go to https://drupalgutenberg.org/demo.

Commerce Guys: Enabling headless Drupal Commerce while improving its core

April 4, 2019 - 12:40

The Drupal community has been abuzz for the past two years with talk of "Becoming Headless" or "Decoupling All The Things." The trend raises reasonable questions from end users who feel this means Drupal is moving into a space that no longer represents them. We hear similar concerns from Drupal Commerce users when we talk about delivering headless commerce. However, we don't believe anyone should be worried that improving support for Drupal as a REST API server will detract from efforts to improve its utility as a traditional CMS.

From our perspective, you can (and we do) support at the same time both traditional applications, where Drupal itself provides the front end, and headless applications, where a JavaScript application renders data served from a Drupal powered REST API. In fact, in this post I'll demonstrate how supporting the latter has actually improved Drupal (and Drupal Commerce) for everyone. Headless initiatives help uncover bugs and fine-tune the underlying application architecture.

Drupal core, API-First, and headless commerce

When you remove the default presentation layer from a system, you are bound to find interesting problems. How much logic is embedded in a Drupal field formatter or field widget? What happens when those are not used to render or manipulate an entity’s values? As a quick example, work in the API-First Initiative related to taxonomy terms turned up a validation bug where code restricting parent terms to the same vocabulary only executed in the context of the default entity form. Fixing that bug to prevent invalid relationships via API updates contributed to improving Drupal core overall even though the issue wasn't affecting traditional Drupal usage.

We're looking for similar wins as we explore improving Drupal Commerce to support headless commerce applications. Not only will it make our code more disciplined, it will help us improve the user experience of the standard modules themselves through the use of JavaScript. I will be speaking about the process a little at DrupalCon Seattle in a session titled Delivering Headless Commerce.

In early 2018 I wrote about why Drupal Commerce needs the API-First initiative and JavaScript Modernisation Initiatives. The outcome a short time later was our progressively decoupled Cart Flyout module which provided a JavaScript enabled take on managing cart interactions. By the end of last summer, the module included an complete replacement for the Add to Cart form that just used JavaScript. This module does not require a fully decoupled architecture but still provides important performance and scalability enhancements to every Drupal Commerce user. However, it did come from our efforts to support a fully headless architecture.

Consider a couple examples of our work toward a fully headless Drupal Commerce improving the modules more generally:

Cart should grant "view" access to orders available from a user's cart session

While working on the Cart API module to find ways to use JSON:API, I realized we were missing some entity access control for carts to allow anonymous users to view their orders tracked in their session. With query-level entity access landing in Entity API, fetching orders over JSON:API or GraphQL automatically restricted the returned orders to carts belonging to authenticated users. We realized we needed to update Commerce Cart to support this use case for traditional and headless use cases.

Provide a constraint on the Coupons field to verify referenced coupons are available

I set a goal earlier this year to support coupon redemption through our Cart API. I ran into a problem early on while evaluating our code to remember where / how we validate coupons. I knew the code existed and expected it'd be pretty simple to reuse. Unfortunately, it turned out we only put validation logic in the default coupon checkout pane code, meaning a coupon redemption endpoint in the Cart API would have to reproduce the code to support client-side coupon validation. That sort of duplication is bound to lead to bugs or out of sync logic.

What was the solution? Add a validation constraint to our coupon reference field on orders. This constraint contains the code that validates a coupon for an order and ensures its related promotion applies. RESTful Web Services module and JSON:API automatically run validation against entities when they're modified, triggering this check and allowing invalid coupons to be detected right away. This in turn let us simplify our coupon redemption form as well. The final patch is still in progress, but once landed, it will make it easier for any Drupal Commerce site, headless or not, to add their own customizations on top of the default coupon redemption form or write their own.

What’s next for 2019?

We've been pretty busy preparing Centarro Toolbox for release at DrupalCon Seattle, so first I expect I'll take a deep breath and celebrate the Drupal 8.7 release. We're planning now how to ensure Drupal Commerce users can harness the power of Layout Builder and Media, and we'll be integrating them into our Belgrade based demo.

Second, we'll continue to improve the developer experience with Drupal Commerce over the various API based modules. Headless Drupal Commerce is already working in the wild. The team behind Spark POS uses JSON:API and Drupal Commerce to handle ZKungFu’s billion dollar business. 1xINTERNET has been pushing React based front-ends for a while and will even be presenting their work at DrupalCon. As project maintainers, we want to empower teams to build similar applications and move our support from product catalog navigation and shopping cart manipulation through to checkout completion and order management.

Tandem's Drupal Blog: Migrating a Drupal 7 File To a Drupal 8 Media Entity

April 4, 2019 - 07:00
April 04, 2019 Media has been in core since 8.3. As of this blog post, no migration path exists yet for a Drupal 7 File to a Drupal 8 Media Entity. Use Case Recently I was involved with migrating a site that had numerous file based widgets on their Drupal 7 site. The technical stakeholder was aware of the media module in Drupal 8. The client ...

Electric Citizen: Citizens to DrupalCon Seattle

April 4, 2019 - 00:00

Electric Citizen is heading to DrupalCon Seattle next week! We're pleased to sponsor again this year, and send several members of the team to represent.

Look for us in the exhibit hall in booth #209, where we'll be sharing some cool EC swag, and looking to make new friends and connections in the Drupal community. This year we'll have some awesome knit hats, handmade in Minnesota, as well as some other goodies.

Keep an eye out for Citizen Dan, Citizen Tim, Citizen Aundrea (DrupalCon newbie!) and Citizen Adam, as we make our way through another DrupalCon.

Axelerant Blog: Unlocking Value, Together: Meet Us At DrupalCon Seattle

April 3, 2019 - 21:26


Axelerant is going to DrupalCon Seattle. Between the 8-12th of April, the Drupal community will get together in Seattle for a slightly different DrupalCon experience, this time with a new focus on content-rich opportunities, bringing in diverse speakers, and greater exchange of information. 

Drudesk: Combining Drupal and GatsbyJS for high website speed

April 3, 2019 - 19:47

JavaScript frameworks have raised the bar of website speed to the sky. Still, it’s just the beginning. GatsbyJS, a tool based on React and GraphQL, impresses the world with fast websites and applications it creates. Let’s take a look at combining Drupal and GatsbyJS to achieve high website speed.

OPTASY: Drupal Multisite Setup: Are There (Still) Any Valid Reasons to Use It? Should It Get Removed in Drupal 9.x?

April 3, 2019 - 18:58
Drupal Multisite Setup: Are There (Still) Any Valid Reasons to Use It? Should It Get Removed in Drupal 9.x? radu.simileanu Wed, 04/03/2019 - 11:58

Why would you still want to opt for a Drupal multisite setup? What strong reasons are there for using this Drupal 8 feature?

I mean when there are so many other tempting options, as well:
 

  • you could use Git, for instance, and still have full control of all your different websites, via a single codebase
  • you could go with a Composer workflow for managing your different websites
     

One one hand, everyone's talking about the savings you'd make — of both time and money — for keeping your “cluster” of websites properly updated. And yet, this convenience comes bundled with certain security risks that are far from negligible.

Just think single point of failure...

Amazee Labs: Webinar Recap: CSS Modules

April 3, 2019 - 02:38
Webinar Recap: CSS Modules

Amazee Labs webinars allow us to share our knowledge and experience with the community. Last week we discussed the challenges in choosing the right CSS-in-JS solution and the advantages of using CSS modules.

Philipp Schmid Tue, 04/02/2019 - 21:38

After a couple of years of building decoupled sites, the Amazee Labs team has tried several different CSS-in-JS solutions and found this one to be best suited to the needs of our development team.

CSS Modules is a mature project with a syntax that is a superset of CSS, similar to Sass. It makes it easy for you to “think in components” without having to worry about BEM class naming. It automatically generates locally-scoped CSS class names, so you can use “.wrapper” in multiple files without conflict.

It also allows integration of “global” class names from other code (like JS libraries or 3rd party CSS). With CSS Modules you get automatic dead-code elimination as only the CSS used on the page is ever sent to the browsers. Best of all CSS Modules can be used with any JavaScript framework, including React, Angular and Vue.js.

Watch the webinar recording online to learn about:
  • Components without BEM

  • Locally-scoped class names

  • Dead-code elimination

  • Multi-platform support

  • Nested rulesets

  • Cross-component composition

  • Sharing variables between your JavaScript and your CSS


Catch up on our previous webinars here:

Sharing knowledge and learnings is a key value at Amazee Labs. Keep an eye out for future webinars here!

myDropWizard.com: Drupal 6 in the year 2022 (and what's coming for Drupal 7)

April 2, 2019 - 23:59

When we originally announced that we'd be providing Drupal 6 Long-Term Support, we committed to supporting our customers until at least February 2017.

Each year in the spring, we've taken a look at the state of Drupal 6 and decided whether we'll extend support for another year, and if we need to make any changes to our offering. Here's the articles from 20162017, and 2018 where we announced an additional year each time and any new concerns (for example, PHP 7 support).

Today, we're announcing that we'll be extending our Drupal 6 Long-Term Support two more years until at least February 2022!

I'm sure there will come a time, when it no longer makes business sense to pour resources into Drupal 6 for the few remaining sites, however, it's already clear to us that there's enough demand for a couple more years.

Also, now that we know when Drupal 7 will reach it's End-of-Life, we've started to plan for that, and decided that we'd like D6LTS to last at least until then (which is why we're announcing an additional 2 years this time, rather than just 1).

Regarding Drupal 7: we've officially applied to be a Drupal 7 Extended Support vendor and have been accepted. :-)

Read on to find out more!

Sooper Drupal Themes: EU Article 13 and Article 11 - How can Drupal save the day?

April 2, 2019 - 22:32
Article 13: Copyright re-invented

The European Union has not updated the copyright laws since 2001. Now they are aiming to change that and bring the copyright laws in line with the “digital era”. Most of these changes are uncontroversial, however, Article 13 will have a huge impact on the way that content is shared on the internet. What it basically means is that, hosting platforms will be responsible to make sure that the content that is uploaded is going to be in line with the copyright laws.

How Article 13 shifts the balance of power for creators and publishers

The goal of article 13 is to fix the problem of value distribution amongst a certain set of industries, especially the music industry. The problems with the Article 13 is with the services towards which it is addressed, while also suffering from having a broad yet vague goal. Problem is that it will apply to all types of copyrighted works. On top of that, there is no reason for an article that is intended to strengthen the bargaining power of the music industry to impose costly responsibilities on platforms that have nothing to do with sharing music. Additionally, since the article seems so vague, there are bound to be misunderstandings and misinterpretations which will lead to the need of taking legal action for the matter to be settled.

Buckle up for the consequences of Article 13

So how are hosting platforms going to tackle this new challenge? Basically, human reviewing is going to be out of the question. The reason for this is that consistently monitoring huge amounts of data that is being uploaded in a timely manner is virtually impossible, unless you have a small army at your disposal. What this means, is that platform will have to put automated filters in place in the forms of BOTs or AI. Ok, so where is the problem?

Big corporations win, small companies lose

One of the problems is that a system like this will be extremely expensive to adopt. What this means is that smaller platforms will not be able to adopt such a system and might be forced to opt out of the game altogether. Basically, this will stifle the emergence of innovation in the EU, brought by new small competitors on the market. On top of that, already established giants in the tech industry will be able to afford such a system, meaning that they will be able to hold even more power.

Another problem with this approach, is that an AI or BOT is not going to be able to tell the difference between truly copyrighted content and content that is meant for humour.

Is this goodbye to the meme culture?

What this means is that if a funny picture is based on a scene from a movie, the filtering system will regard this as copyrighted content and remove it from the internet.

Although the EU has made it clear that the exceptions to the rule will be content that is meant to be a “quotation, criticism, review, caricature, parody or pastiche”, the problem with how these contents will be told apart from real copyright infringements by filtering systems still remains the same.

“There is a module for that”...

Commerce Guys: Introducing Centarro Toolbox at DrupalCon Seattle

April 2, 2019 - 18:04

Commerce Guys is joining forces with some of our Technology Partners and a variety of contributors to promote Drupal Commerce at DrupalCon Seattle from April 9-11, 2019.

We're excited to introduce the Drupal community to Centarro Toolbox, a collection of SaaS products and support packages that help Drupal Commerce teams build with confidence. First revealed at MidCamp last month, we can't wait to show it off to the community at large while also connecting about all things Commerce 2.x.

Come demo Centarro Toolbox (and grab some sweet swag)

There's a lot to see inside Centarro Toolbox!

It includes three of our own SaaS tools designed to complement any Drupal Commerce site. They provide update automation, code quality monitoring, and a sales and analytics dashboard that delivers key insights to merchants. We've also bundled in offers from our partners at Avalara, Human Presence, and Lockr, and we'd love to share all about them.

We'll be handing out some exclusive swag this year, including our first pressing of custom coins ... no clue why it took us a decade to think that up! We're also stocking the booth with some rad sweatbands to keep your brows clean at the after parties Dave Grohl style. Finally, visitors to the booth can enter to win:

  • 1 of 3 copies of Preston So's book, Decoupled Drupal in Practice (winner chosen at random each day)
  • An Xbox One courtesy of PayPal (winner chosen at random Thursday afternoon)

Drupal Commerce in the spotlight

There's a lot to be said about how Drupal Commerce is making merchant and agency teams more productive, and you don't just have to take our word for it. Add the following sessions to your schedule to learn more:

Last but not least, if you've made it this far, chances are you're really into what we're doing with Drupal Commerce. If that's you, we'd like to invite you to an exclusive reception at Avalara's HQ. We'll enjoy food and beverages from the 18th floor looking out over downtown Seattle. The party will be from 6:30 - 8:30 PM Wednesday, but space is limited! Reach out in advance or find us early at the show to reserve your spot.

Schedule Time to Meet

If you're heading to DrupalCon, we'd love to chat about Drupal Commerce with you. Use our meeting request form to get on our calendar to discuss a particular project or need, or subscribe to our newsletter to be kept in the loop more generally.

Manifesto: So long Drupal 7, welcome Drupal 9

April 2, 2019 - 17:03

Drupal 7 was released back in 2011. Having served the Drupal Community and its users for more than 8 years, it’s now due to reach end-of-life (EOL) in November 2021. Meanwhile, Drupal 9 is due to be released in 2020, which means Drupal 8 will also reach EOL at the same time as Drupal 7.. Continue reading...

The post So long Drupal 7, welcome Drupal 9 appeared first on Manifesto.

Promet Source: WCAG 2.1 in 7 Perspectives

April 2, 2019 - 06:05
For those who don’t work in the trenches of digital accessibility, the guidelines can seem confusing or overwhelming. The fact is, it’s not necessary to know the details associated with the 73 individual Web Content Accessibility Guidelines (WCAG) 2.1 success criterion in order to make design decisions and ultimately contribute to a website planning session.   

Mobomo: DOI’s Drupal Developer Support Services BPA awarded to Mobomo, LLC

April 2, 2019 - 01:03

Vienna, VA March 19, 2019—Mobomo,

Mobomo, LLC is pleased to announce our award as a prime contractor on the $25M Department of Interior (DOI) Drupal Developer Support Services BPA . Mobomo brings an experienced and extensive Drupal Federal practice team to DOI.  Our team has launched a large number of award winning federal websites in both Drupal 7 and Drupal 8, to include www.nasa.gov, www.usgs.gov, and www.fisheries.noaa.gov.,These sites have won industry recognition and awards including the 2014, 2016, 2017 and 2018 Webby Award; two 2017 Innovate IT awards; and the 2018 MUSE Creative Award and the Acquia 2018 Public Sector Engage award.

DOI has been shifting its websites from an array of Content Management System (CMS) and non-CMS-based solutions to a set of single-architecture, cloud-hosted Drupal solutions. In doing so, DOI requires Drupal support for hundreds of websites that are viewed by hundreds of thousands of visitors each year, including its parent website, www.doi.gov, managed by the Office of the Secretary. Other properties include websites and resources provided by its bureaus  (Bureau of Indian Affairs, Bureau of Land Management, Bureau of Ocean Energy Management, Bureau of Reclamation, Bureau of Safety and Environmental Enforcement, National Park Service, Office of Surface Mining Reclamation and Enforcement, U.S. Fish and Wildlife Service, U.S. Geological Survey) and many field offices.

This BPA provides that support. The period of performance for this BPA is five years and it’s available agency-wide and to all bureaus as a vehicle for obtaining Drupal development, migration, information architecture, digital strategy, and support services. Work under this BPA will be hosted in DOI’s OpenCloud infrastructure, which was designed for supporting the Drupal platform.

The post DOI’s Drupal Developer Support Services BPA awarded to Mobomo, LLC appeared first on .

TC Drupal News: Submit a Session for 2019 Twin Cities Drupal Camp

April 1, 2019 - 23:05

Twin Cities Drupal Camp is the perfect opportunity to share your experiences and expertise with the community, and session submission for our 2019 camp is now open!

Share what you've learned about Drupal, business and other Web topics such as project management, favorite modules, development processes, design/UX, SEO, content strategy, backend wizardry, front-end tips or whatever subject interests you. Our Drupal Camp is attended by eager learners and people who have something to share. This year we are asking for 45-minute session submissions.

If you have a session proposal, please submit it. Presenters have their registration fees waived, in addition to the heartfelt thanks of the community! (fame and fortune optional).

The end is near, session submissions will close on April 29th at Midnight CDT.  Submit your session today!

Kalamuna Blog: Scaling Content Moderation with Artificial Intelligence

April 1, 2019 - 22:45
Scaling Content Moderation with Artificial Intelligence Rob Loach Mon, 04/01/2019 - 08:45

Don’t miss the DrupalCon Seattle session, “Hot Dog/Not Hot Dog: Artificial Intelligence with Drupal” by Rob Loach, Director of Technology at Kalamuna.

Categories Drupal Guidance Pantheon Author Andrew Mallis Crispin Bailey Rob Loach

Jacob Rockowitz: Drupal is frustrating

April 1, 2019 - 19:00

Proceeding every article or blog post about the future of Drupal, there are always a few comments that express a high-level of frustration when it comes to Drupal 8. From missing modules, to completely rewritten APIs, to new design patterns, and even complaints about the restructuring of sessions and tracks at DrupalCon….People are frustrated with change. The entire Drupal community understands peoples’ frustration, which is why we are continually trying to improve the software and community. Our most significant strides happen at DrupalCons, where everyone comes to together to share codes, ideas, and passion.

Introspection before DrupalCon

Before last year’s DrupalCon I wrote a blog post titled, Drupal is the worst Content Management System except for all those other solutions in which I talked about Drupal adoption, sustainability, and mentorship. DrupalCon provides the Drupal community with an opportunity for everyone to take stock of where we are at and where we are going. Every year we have discussions with actionable items to improve our community, which is continually changing.

Each year, I get something different out of DrupalCon. Last year I became more aware of diversity and inclusion issues within the Drupal and software community. I was also inspired to address webform related accessibility issues. The overarching thing I have learned at DrupalCons is contributing to Open Source is more than writing code, it’s about collaboration and community.

What I like about this quote is it acknowledges two key aspects to Drupal - the code and community - with the code being the “what” that brings us together. The code might also be what is most frustrating to people coming and staying with Drupal....Read More

Drupal.org Featured Case Studies: Rapid Rollout of 11 Brand Websites for a Leading Publishing Conglomerate

April 1, 2019 - 18:40
Completed Drupal site or project URL: https://www.autonews.com/

The Client is one of the largest privately owned business media companies with 55 leading business, trade and consumer brands in North America, Europe and Asia.

Key Highlights:
  • Rapid brand rollouts
  • Engineering team’s time is freed up - the first brand was able to set up around 50 landing pages without needing any developer intervention
  • All brands share best practices across analytics, SEO (meta tags, etc.), performance (Drupal Cache, Varnish, Cloudflare), media management etc as these are part of the Core platform