Drupal

Remote Site List

New Drupal Modules - 29 September 2017 - 2:11pm

This module is used for administrators who manage multiple sites, to keep track of them. It's a very simple approach without any bells and whistles, just to give a quick reference of the sites you have.

You can use it on any Drupal 7 site regardless of where it's hosted. Install the module on your own site to act as the reporting location. Then, install the module on any site you want to monitor, and configure it with your reporting site's information. Now anytime cron runs the remote sites will connect to your reporting site to call home.

Categories: Drupal

Convio Connect

New Drupal Modules - 29 September 2017 - 12:45pm

// TODO: Create Readme

Categories: Drupal

Bay Area Drupal Camp: Training Registration for BADCamp 2017 is Open!

Planet Drupal - 29 September 2017 - 11:31am
Training Registration for BADCamp 2017 is Open! Grace Lovelace Fri, 09/29/2017 - 11:31am Training Signups are Now Open!

Are you prepared to gain mastery of your Drupal Skills? BADCamp has two full days of training offered from some of the most talented leaders in the Drupal community. Join the masters on Wednesday and Thursday while they unfold the magic. This year BADCamp offers skills training in DevOps, theming, module development, content strategy, and much more!

  All courses will be all-day (approximately 8am-5pm) with a break for lunch. Signup today -- openings go quickly, and classes will fill up fast.

 

Signup Today


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

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

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

Thank you for your understanding.

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


Getting Started with Drupal - Wednesday

by Agaric & Digital Echidna with Mauricio Dinarte

This training is aimed to people just starting with Drupal. Basic concepts will be explained are later put into practice. The objective is that someone, who might not even know about Drupal, can understand the different concepts and building blocks to create a website using this CMS.

 

SEO & Accessibility - Wednesday

by Hook 42 with Aimee Degnan and Carie Fisher

SEO stands for "Search Engine Optimization." Improving your website's SEO can translate into more visitors, better conversions, and more sales.

Accessibility refers to the design of products, devices, services, or environments for people who experience disabilities.

When properly configured, Drupal is a very SEO-friendly and Accessible web framework. The trick is to know which Drupal modules you need to install and how to optimally configure them. Configuration doesn’t stop at the module level - a solid content strategy is required to make the most Accessible and optimized website. “Content is King” and our job is to make Drupal showcase content in the most effective way to all consumers and search engines.

 

Object Oriented PHP - Wednesday

by Chapter Three

With the move to Drupal 8 everyone who works in the PHP layer will be exposed to more and more to object­ oriented code. Come learn the basics of working with objects in PHP and how OOP can help you to write well­ structured code

 

Continuous Integration: From 0 to CI Hero - Wednesday

by Tandem with Alec Reynolds and Mike Pirog

Continuous Integration (CI) methodologies and tools can deliver huge efficiency gains for web development teams. However, overburdened with feature requests and new projects, many development teams never have the time to learn and implement a CI workflow. Now is that time.

In this training, we provide hands-on instruction in how to setup a continuous integration workflow for your team using Github, TravisCI, and several popular hosting platforms (Pantheon and Platform.sh).

 

Drupal Crash Course for Non-Developers - Wednesday

by Promet Source with Margaret Plett

Are you responsible for project management, content, or vendor selection and preparing to work with Drupal? This one-day training delivers all of the tools you need to get started. Delivered by an Acquia Certified Drupal Developer, this training will answer the questions you didn’t even know to ask!

 

Component-based Development in Drupal - Wednesday

by Mediacurrent with Mario Hernandez

In this training we will put into practice one of the latest latest trends in development, components. Building a website using the component-based approach can dramatically improve collaboration among teams, making code more reusable, flexibility and long term maintenance of your website. We will work on building a living styleguide which will become the single source of truth for markup, styles and javascript behaviors.

 

Component-based Theming with Twig - Thursday

by Forum One with Chaz Chumley

Join Forum One as they walk through the theming variations that started with the traditional theme-centric design and has quickly moved into component-based design. Together you will master Component-based theming with Twig as you work to identify patterns, define components, utilize command line tools such as Composer, NPM and Grunt to quickly create a PatternLab managed theme. Learn how to work smarter in developing components that can easily be integrated into project after project without having to recreate them yourself.

 

Hands on Drupal 8 Module Development using DrupalConsole - Thursday

by WeKnow with Jesus Manuel Olivas and Omar Aguirre

This training will provide an introduction to the most important changes for developers in Drupal 8, allowing students to practice Drupal OOP while at the same time providing a solid knowledge of the process of build modules for Drupal 8.

 

Theming Drupal 8 - Thursday

by Drupalize.me with Joe Shindelar

Themes combine HTML, CSS, JavaScript, and Drupal in order to make beautiful websites. Creating truly unique themes requires knowing how to use the Twig template language to manipulate HTML, how to add CSS and JavaScript assets in a way that's compatible with Drupal's caching, all while maintaining the flexibility that Drupal is known for.

 

Content Strategy for Drupal 8 - Thursday

by Evolving Web with Suzanne Deracheva

Drupal is a powerful tool for managing structured content. Many Drupal projects revolve around producing, displaying and organizing content effectively. This course will walk you through the process of creating a content strategy for your next Drupal project, and planning out how that content will be structured in Drupal. Whether you're creating a brand new site or migrating to Drupal, you'll learn techniques that will help you build a solid content strategy and a successful Drupal website.

 

Intro to Backdrop CMS - Thursday

by Nate & Jen Lampton

Backdrop CMS is for the small to medium sized business, non-profits, educational institutions, and companies or organizations who are delivering comprehensive websites on a budget. This introductory training will cover the basics of creating and administering a website with Backdrop CMS.

 

Drupal 8 Configuration System Basics - Thursday

by DrupalEasy with Mike Anello

The Drupal 8 configuration system can provide great advantages to managing the configuration of a site, but it can also cause massive headaches if used improperly. This presentation will provide an overview of how the Drupal 8 configuration system works, best practices on basic workflows to utilize it effectively, and a small sampling of some of the contributed modules available to enhance it.

  YOU make BADCamp awesome!

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

  We need your help!

Do you want a more meaningful BADCamp experience? BADCamp would not be possible without the overwhelming love and support from our community! Volunteer to help set up, tear down, take pictures, monitor rooms or so much more!  If you are local and can help us, please contact Anne at anne@badcamp.net or sign up on our Volunteer Form.

  Sponsors

A HUGE shout out of thanks to our sponsors who have helped make this magnificent event possible. Interested in sponsoring BADCamp? Contact matt@badcamp.net or anne@badcamp.net

Thank you to Pantheon & Acquia for sponsoring at the Core level to help keep BADCamp free and profoundly reverential.

 

Drupal Planet
Categories: Drupal

Updater

New Drupal Modules - 29 September 2017 - 11:00am

A Drush command to update a website instance by executing available "updaters".

An updater is a PHP function which is executed during execution of the Drush update-website command.

The Drush command keeps track of updaters already executed, so they are not executed twice on the same Drupal instance.

Updaters have access to usual Drupal APIs and other Drush commands.

Categories: Drupal

Lullabot: Fundamentals of Responsive Images

Planet Drupal - 29 September 2017 - 9:40am

As a recovering English major, I’d like to believe words alone are enough to tell a tale on the web. A text-only page is fast: even a long article can load nearly instantly. Add photos, and the web slows down. Yet great images bring emotion, a connection with others and the world around us. They’re often worth the tradeoff in time to load a page.

People don’t want to wait around longer than necessary, though. Any benefit you get from a great image vanishes once someone’s neck begins to tense up as the loading bar slowly creeps from one side of the URL bar to the other.

undefined

Images also lose their emotional impact if they’re blurry and someone has to squint to see the subject.

If you take an image that looks nice and crisp on a phone, then share that same file on a big desktop screen, it’s going to look fuzzy. Switch it around with a nice, big image that looks great on desktop, and somebody looking at the same file on a phone will grow impatient, waiting for the file to load.

We want the best of both worlds: images that look great no matter which screen they’re viewed on, while loading as quickly as possible.

Thankfully there’s a great solution to this problem due to the work of the Responsive Images Community Group. They worked with browser developers to develop new markup options such as the picture element and the sizes and srcset attributes. With these tools, we can provide a selection of image files so your browser can pick the right one depending on how someone is viewing it. This can help to make sure photos download as fast as possible while still being enjoyed in all their glory.

There are a lot of great resources that help explain the new responsive images specification. I highly recommend Jason Grigsby’s article series, Responsive Images 101, as well as Eric Portis’ Responsive Image Guide.  You can read the actual specifications for the picture element or the srcset and sizes attributes, although specs can be pretty dry reading. Understanding the specifications and syntax are important, but you still need to make a number of key decisions on how you’ll use responsive images with a particular site.

I’ve set up responsive images on a number of large sites like NYU Langone, and I also help to maintain the Responsive Image and Breakpoint modules for Drupal 8, so I wanted to share some of my experiences in working with responsive images.

In this article, I’ll be explaining some of the key concepts for responsive images, as well as providing an overview of a few different responsive image tactics. The solutions used for any particular image will vary. Understanding those options will help you to set out on the right path.

I’ll dig into more technical detail in future articles focused on some of those individual tactics. Right now, let’s start looking at the various ways we can make sure our images look awesome and load fast.

Picking the right method to make your images responsive

The biggest difference in how you’ll handle making images responsive is what you’ll do for images that are photos, versus how you’ll handle logos and icons.

Photos—often referred to as raster images—do not scale so easily. The word raster comes from the Latin word rastrum, or rake. Old cathode ray tubes created images on screens by literally drawing one line at a time, raking each across the screen. These days raster images are created by hundreds of thousands to millions of individual dots, or pixels, on a screen. It takes a lot of data to tell a browser what color each of those dots should be in order to recreate an image.

undefined

Logos and icons on the other hand often use vector graphics. These images can be specified using mathematical vectors—a series of points on lines along with information that describes the curves connecting those points. The simpler shapes and colors in vector graphics can scale really easily to a wide variety of sizes, because math can easily calculate the color needed for each pixel.

For vector graphics, you’ll want to use SVG files. SVG means Scalable Vector Graphics, and the name really says it all. SVGs are text files which use XML to describe the vectors necessary to create an image. Use an SVG plus a little CSS, and your logos and icons will be responsive.

I would not recommend using an older technique to load icons through a webfont containing multiple icons. The goal of that was to avoid multiple requests to a server: with the the advent of the http/2 protocol, that’s not as much of an issue. Icon fonts also have major accessibility issues, since they use a specific letter of a font for each icon. For people using a screen reader, that’s not so awesome.

For photos and other raster images, the techniques you use might vary a bit, depending on if the images are loaded through CSS or HTML.

There are ways to make background images added to a site through CSS responsive, but unfortunately browser support can be a bit shaky.

Thankfully, images used as content within a site, which are loaded through the HTML markup for a page, have great options that we can use. These sorts of images are generally what people are referring to when you hear the term responsive images.

So we’ll be focusing mostly on raster images that appear as content on your site. Even there, however, there a few important variations to keep in mind.

How do images vary across breakpoints?

When we’re talking about making images responsive, we mean that we want to provide some variation in how those images appear depending on how they’re viewed.

Sometimes we want an image to essentially look the same whether you’re on mobile or desktop. For example the image always appears as a square or a rectangle. It might only fill a sidebar column on desktop, while filling the full width of the screen on mobile. However, it retains the same aspect ratio—the relationship between the height and the width of the image. 

We call this use case viewport sizing, and typically this ends up being the most common way that images are made responsive.

For viewport sizing, we typically just need a good ol’ img element with two new attributes: sizes and srcset. We’ll get into how those new attributes work, but the short version is that sizes tells a browser how much space an image takes up in a site’s layout at various screen sizes, while srcset provides some image file options the browser can choose between.

<img src="small.jpg" srcset="large.jpg 1024w, medium.jpg 640w, small.jpg 320w" sizes="(min-width: 36em) 33.3vw, 100vw" alt="A swirling nebula">

Sometimes we need images to change a bit more at various screen sizes. Maybe we need a square image on mobile but a rectangle on desktop. Sometimes we also need to change the cropping of an image across breakpoints, showing a close-up image on mobile, while using a wider shot on desktop. Changes to aspect ratio and cropping are often called art direction, and they require a more complicated solution.

For art direction, we’ll need to use the picture element, which serves as a wrapper around a series of source elements, along with an img element. Each source element has its own media attribute: the media query defines the viewport size range where that source should be used to select the particular file that will be used for the img element contained inside the picture element.

You can also provide a sizes and srcset attribute on a source element so the browser has a number of files it can choose between for a particular viewport range.

<picture> <source media="(min-width: 70em)" sizes="40vw" srcset="nebula-artsy-wide-2800.jpg 2800w, nebula-artsy-wide-2240.jpg 2240w, nebula-artsy-wide-1400.jpg 1400w, nebula-artsy-wide-1120.jpg 1120w"> <source media="(min-width: 35em)" sizes="36vw" srcset="nebula-artsy-square-1120.jpg 1120w, nebula-artsy-square-900.jpg 900w, nebula-artsy-square-560.jpg 560w, nebula-artsy-square-450.jpg 450w"> <img src="nebula-artsy-tight.jpg" alt="An artsy cat"> </picture>

Using the picture element is overkill when you’re just dealing with viewport sizing. Having separate source elements is great for art direction, though, because you can provide a set of files on one source element with a certain aspect ratio or cropping level, while using a different aspect ratio or cropping level on another source element.

There’s very good browser support for the picture element, as well as the sizes and srcset attributes. IE11 is the main browser that still needs a little help, and for that you will want to make sure you’re using the Picturefill polyfill. Doing so may change what you use as a fallback src on the img inside the picture element. See the example on the Picturefill site for details.

For either viewport sizing or art direction, you’ll likely want to use the sizes and srcset attributes, so let’s dig a little deeper into what purpose those attributes are serving. In short, it’s all about pixels versus percentages.

Responsive image grudge match: Pixels versus percentages

Responsive design typically specifies a site’s layout in percentages, while raster images like photos are defined in pixels. It’s a grudge match, and our job is to serve as referees.

In one corner, we have responsive web design, where percentages define layout. By using a percentage, we allow the browser to do the heavy lifting of figuring out for an element like a sidebar exactly how many pixels wide it should be for a particular screen size. This is great, since like vector images, a browser can easily calculate layout boxes through the power of mathematics.

In our other corner, we have photographic images. Photos are more difficult to resize, because we need to give a browser detailed instructions about every single pixel in the image. As a result, photos don’t flex so easily.

undefined

Image files are essentially information with instructions detailed enough to create a photo at a particular size. A browser can figure out how to make an image smaller than its file size would suggest, because it has enough information to do so. Making an image bigger is much trickier, because if a browser doesn’t have enough detailed instructions for a larger size, it has to start guessing. And inevitably, it will guess wrong at least some of the time, which leads to images looking blurry.

However, that doesn’t mean we can just give a browser so much information that it can draw an image at any potential size. A high-res image file is going to be way bigger than necessary for a much smaller, low-res screen. More information, bigger file size, longer download time.

Because pixels matter so much, we also have to keep in mind screen resolution. Some displays use a larger number of pixels in the same amount of physical space in order to create a more detailed image. For a low-res display, a sidebar that has a layout width of 500px will use 500 physical pixels in a screen to create that width. For a high-res “retina” screen, there may be 1000 physical pixels in that same space. That means we need a higher resolution image to account for that difference.

So we want to figure out for one particular type of image how many pixels of information we need in the file for the amount of space it takes up in a percentage of the site’s layout at a certain screen size and resolution. It’s okay if the file has a few more pixels of info, although not too many more, but we definitely want to avoid having too few pixels of info, so we can avoid blurry images.

The sizes attribute helps us to tell the browser about the layout percentages for a particular image, while srcset provides information about the number of pixels in each image file. Why do we need to put this information into HTML markup, though?

Why browsers need a sizes attribute

We need sizes because of how browsers process a web page that is being loaded. Once a browser receives the HTML for a page from the server, it begins scanning the document to look for other resources it will need to load. It finds all the CSS and JS documents that need to be loaded, as well as any image files, then begins prioritizing how it will download those files.

CSS files are a top priority, because they provide so much critical information about how a page’s HTML should be styled, and because CSS files often contain links to other resources that need to also be downloaded, such as web fonts and background images. JS is also a big priority, as it can change around the order of DOM elements that will need to be styled based on CSS rules. What’s critical to understand is that browsers improve overall performance by starting to download images while the CSS and JS files are still being processed.

That’s been a big challenge for responsive images, because you can’t just use CSS and JS to select an image file with the right width for a particular image slot, as doing so would mean waiting until all of the CSS and JS has been processed to fully understand the final layout of a page and thus the width of an image slot.

We can solve this tricky problem by using a key part of the responsive images spec: the sizes attribute. This attribute on an img element (or on a source element within a picture element) tells the browser how large that element will be once layout rules are applied.

So, within our sizes attribute, we provide a set of widths and accompanying media conditions. A media condition is simpler than a media query and consists only of something like (min-width: 1000px). For our example, we could provide the following sizes attribute:

sizes="(min-width: 36em) 33.3vw, 100vw"

The first thing to note is that we’re providing the media condition for the largest possible viewport first, as the browser will pick the first option that matches.  Next, note the units we’re using:

  • Using em for widths in media conditions is a good practice, because it provides extra flexibility for people who change the settings in their browser to use larger than normal default font sizes. The typical default font size is 16px for 1em, so 36em is the equivalent of 576px. So we’re saying when the browser has a minimum width of 576px, this image takes up 33.3vw space in the layout.
  • The vw unit stands for viewport width: 1vw is equal to 1% of the width of the viewport; 33.3vw is 33.3% of the viewport width. The vw unit is used instead of percentages to make clear that this is a percentage of the viewport, not the width of the containing element.

Finally, the comma indicates the next set of media conditions and layout data. You can have as many commas as necessary within a sizes attribute. Here we just have one, so we’re saying that for viewports smaller than 576px wide, this image takes up 100% of the viewport space.

Let the browser choose with srcset

The sizes attribute needs to be paired with a srcset attribute on the same element (either an img element or a source element). This attribute will contain a comma-separated list of the URLs of image files: after each URL there is a space, then a number signifying the width of the image followed by the letter w. For example:

srcset="image235.jpg 235w, image290.jpg 290w, image365.jpg 365w, image470.jpg 470w, image580.jpg 580w, image730.jpg 730w, image940.jpg 940w, image1160.jpg 1160w"
  • The browser will take a look at these image files and use the number with the w to calculate which image file will best fit within the amount of space we’ve defined in the sizes attribute.
  • The browser knows the viewport size, so it can pick the right media condition and then use the width value next to the media condition to calculate how many pixels are needed to fill that space.
  • The browser also knows the resolution density of the screen, so it can take that into account with its calculations as well.

The browser can also in theory take into account the bandwidth you have available, providing a lower-res source if you’re on a 3G connection perhaps.

You don’t need to worry about that, though. All you need to do is provide the layout information in the sizes attribute and the possible image sources that can fit within that space, and the browser will take care of matching up the right source file with the image slot.

Make images fluid with CSS

To make images responsive, we still need to write CSS rules that will make the image flexible. For example:

img { width: 100%; height: auto; }

If you’ve provided a set of images in srcset with sufficient widths for the amount of space defined in sizes, this should be all you need. If you don’t have a way to guarantee that, you could also add a max-width: 100%; rule that ensures images are never made larger in the layout than the number of pixels within the image. This can cause design discrepancies if your images are supposed to take up a certain amount of space in a grid design, so I tend to leave off this rule.

If I want to have an image take up a certain amount of space within its container, I find it works better to put a wrapper div around the img or picture element and then set layout rules on that wrapper. That way I can have one consistent CSS rule for all images, but then modify the width of the wrapper in the situations that need that.

Next steps

Hopefully you now have a better understanding of a few different types of images and how you might make each responsive.

The sizes and srcset attributes are often key to making images responsive. In an upcoming article, I’ll talk through how to look at a particular type of image for a site, and then determine what values to use for sizes and srcset. Creating that sort of plan is really key to a successful responsive images solution.

Once you have a plan, you still need to create all the image file variations, and if at all possible you should find a way to avoid creating those image files manually. In a separate article I’ll go over how to use Drupal 8’s built-in tools to automate this process. In a decoupled site, you may find a cloud-based tool works well for that part of the process: Kris Bulman will be going over how to do that in a future article.

Other articles in this series may go over topics like how to implement art direction for responsive images in Drupal 8.

The payoff for this effort is that your images look nice and crisp at all viewport sizes, while still downloading efficiently. No more super slow mobile sites that take forever to load images! That makes a huge difference for those visiting your site. Downloading image files tends to be a big chunk of the work that browsers do when visiting a new site. Speed that up and everybody wins.

Categories: Drupal

Amazee Labs: The final day of DrupalCon Europe talks

Planet Drupal - 29 September 2017 - 9:09am
The final day of DrupalCon Europe talks

#DrupalConEur is 3 days of talks surrounded by a day of summits and a day of collaboration sprints. Thursday was the 3rd and final day of presentations.

John Albin Fri, 09/29/2017 - 18:09

Most importantly for me, Thursday was the day after I finished giving my talk, so I was able to stop tweaking my slides and focus on learning. I started my day by grabbing a hazelnut croissant and coffee in the underground and headed to the community keynote by Joe Shindelar, “Everyone Has Something to Share”.

After that I went to Everett Zufelt’s ”JavaScript and Accessibility: Don't Blame the Language”. Everett busted several myths about accessibility including the pointed “Our web application is accessible (but we’ve never tested it)” And the most useful part of his talk was describing ways that websites get accessibility right. I've now added “ARIA Live Regions” to my TO DO list and highly recommend anyone making websites to watch the video for his presentation.

While I was grabbing a quick lunch, Tamás Hajas presented, as part of the Frontend Track, “What’s new in CSS? Introduction to CSS Grid and CSS Custom Properties”. I added the video to my YouTube “to watch” list and headed to Chris Ruppel’s “Houdini, the Future of CSS”. Chris’s talk was part of the Horizons track, which focuses on the future of Drupal and the web. Houdini is a proposed API that will go into web browsers that will give CSS developers the same ability that JavaScript developers already have; the capability to polyfill proposed changes to the CSS spec. With Houdini, CSS developers could potentially create new syntax (like nested selectors or element queries) and use that in their production code.

Earlier in the week, the Drupal Association announced there would be no DrupalCon Europe in 2018 and that they had formed a committee to determine if and/or how a DrupalCon Europe 2019 could happen. So with this in mind, Théodore Biadala, whose session was scheduled in the final time slot of the day, started his ”Offline Core” presentation by saying ”Thank you for coming to the last session of the last day of the last DrupalCon Europe. Ever.” Awwwww… (Hopefully it won’t be, but that’s another blog post) The “Offline Core” session was a part of the Core Conversations track and after a short presentation about his idea for supporting Progressive Web Apps (PWA) and Service Workers in core, Théodore facilitated a lively discussion with the session attendees on multiple facets of the idea. We even solved a potentially tricky problem: how to turn off a Service Worker (code running on a user's browser) after the website owner has disabled the Service Worker's module in Drupal.

For the past six years, the closing session is followed by Drupal Trivia Night! The Drupal-related trivia questions are written by the wonderful Drupal Ireland community. I attended the first trivia night at DrupalCon Chicago 2011 and never miss it when I go to DrupalCon. Tonight was the 15th Trivia Night. I know because this was one of the trivia questions (Dang it! I wrote down "16" as my answer.)

Since I’ve been in the Drupal Community for 13 years, I know a lot of trivia, but as usual, I did horribly. But winning Trivia Night is not the goal, having fun is and the Drupal Ireland team does a great job of getting everyone involved and happy while losing badly. For example, my team won an award for "favorite team name"; the team name we picked was "We love the Irish!"

Categories: Drupal

Social Format

New Drupal Modules - 29 September 2017 - 8:56am

Provides a generic formatter that produces social media icons with a link for several input methods :

  • Text and Link Field Formatter
  • WYSIWYG text format, for any formatted field
  • Twig function

Advantages over other methods: the formatter can be applied on existing content and provides a generic behavior for the several input methods.

Use cases

Social media links defined

Categories: Drupal

Valuebound: How to create custom token to be used in default mail message template in Drupal 8

Planet Drupal - 29 September 2017 - 7:49am

Sometimes we need to do similar coding in different places, such as for account settings email templates (Welcome email template, Forget password email template, from UI to get the same results. In this scenario, it's always suggested to create a custom token and use that in different types of email templates (account setting email templates) from Drupal UI in [token:type] format.

In our previous blog, we explored about creating custom tokens in Drupal 7 and in this, we will take a brief look at what is token? How to create it in Drupal 8?

In the vein of first thing first, what is token?

Tokens are very small bits of data or text that we use or place into…

Categories: Drupal

Quick clone

New Drupal Modules - 29 September 2017 - 7:46am

This is a small module which allows cloning of node with paragraph fields.

Categories: Drupal

Feeds Paragraphs

New Drupal Modules - 29 September 2017 - 5:41am

This module allows mapping to Paragraphs fields.

Features:
---------
* Mapping to "Text" & "Long Text"
* Mapping to "Interval" field (Interval Module)
* Mapping to "Text List" & "Integer List"
* Mapping to List of type taxonomy terms

Dependencies
-------------
This module requires the following modules:

Categories: Drupal

Monolog DBLog

New Drupal Modules - 29 September 2017 - 3:54am
Categories: Drupal

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

Planet Drupal - 29 September 2017 - 2:44am

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

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

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

 

Check this tutorial on writing a module in Drupal 8

 

 

Categories: Drupal

Commerce China Payments

New Drupal Modules - 29 September 2017 - 1:47am
Integrates with Alipay and WeChat Pay
Categories: Drupal

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

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

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

Planet Drupal - 28 September 2017 - 8:17pm
Drupal Modules: The One Percent — Linked Field (video tutorial) NonProfit Thu, 09/28/2017 - 22:17 Episode 37

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

Categories: Drupal

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

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

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

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

Drupal Training Classes

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

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

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

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

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

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

Do you think BADCamp is awesome?

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

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

We need your help!

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

Sponsors

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

Drupal Planet
Categories: Drupal

Moshe Weitzman: Porting Commands to Drush 9

Planet Drupal - 28 September 2017 - 5:00pm

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

Categories: Drupal

Preferred Language Prompt

New Drupal Modules - 28 September 2017 - 3:58pm

Preferred Language Prompt (PLP) provides a way to funnel users from content in a non-preferred language to the translation of that content that matches their preferred language.

Prerequisites

This module only works with the URL Language negotiation method. Within that, it should work with both path prefix and subdomain.

Categories: Drupal

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

Planet Drupal - 28 September 2017 - 2:32pm

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

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

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

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

Making users comfortable

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

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

Categories: Drupal

Views Condition

New Drupal Modules - 28 September 2017 - 2:09pm

This provides a condition based on if the page is a view page. For example, you can use it to specify that the page title block should only show on a view page.

Similar modules
Categories: Drupal

Pages

Subscribe to As If Productions aggregator - Drupal