Menu Based Landing Page

New Drupal Modules - 25 January 2018 - 11:55am
Menu Landing Page Views What This Module Does

This module helps you generate landing pages based on your existing menu and page structure.
This is especially helpful for websites trying to convert form dropdown menus to a flat menu
linking to landing pages of it's other pages. This module can help you make that transition in a
matter of minutes, rather than recreating your content neccessarily. Of course, it can also be used by new websites
that are setting up the same type of landing pages.

Categories: Drupal

Promet Source: How to Set Up Responsive Images in Drupal 8

Planet Drupal - 25 January 2018 - 10:56am
Responsive images are great! If I wanted to quickly introduce what responsive images are to some, I would say: On mobile? Small images. Tablet? Medium images. Desktop? Large images. This article is a complete "how to" in setting up responsive images in Drupal 8.  If you are using Drupal 7, check out my previous article here: Picture Module: Building Responsive Images in Drupal 7.
Categories: Drupal

Phase2: Decoupled Drupal: A Guide for Marketers

Planet Drupal - 25 January 2018 - 9:58am

If you are considering a move to Drupal 8, or upgrading your current Drupal platform, it’s likely that you’ve come across the term “decoupled Drupal”, aka “headless Drupal”. But do you know what it means and what the implications of decoupled Drupal are for marketers? In this guide we will define decoupled Drupal and share three reasons why marketers should consider a decoupled architecture as they evolve their digital experience platforms.

Categories: Drupal

External Page Redirect

New Drupal Modules - 25 January 2018 - 9:40am

Drupal 7 theme to create pages that are content but redirect immediately to external links.

This is especially useful for menu links that should be featured and displayed among other internal content, but need to link to an external source.

Git clone or download this module. Enable this module.

Under Structure > Content Types you will see a new content type 'External Link'.

Categories: Drupal

BYU Hero

New Drupal Modules - 25 January 2018 - 9:17am

This is the start of a module to apply the byu-hero-banner web componenet.

Categories: Drupal

Acro Media: Drupal Commerce 2: Set up Product Attributes using Rendered Fields

Planet Drupal - 25 January 2018 - 8:53am

In part one of this Acro Media Tech Talk video series, we covered how you set up a new product attribute in Drupal Commerce 2. A product attribute is used to define options that customers would select when buying a product. For example, a hat might have various sizes (small, medium, large) and colours available. These are attributes.

In part two, we'll now take a colour attribute that was set up in part one, but change it into a "rendered attribute". By default, the customer would select the option by seeing the name of the colour. A rendered attribute lets us instead show a colour swatch. So, instead of seeing the work "blue", the customer would see the actual colour. Cool!

This entire video series, when complete, will show you how to set up a new product in Drupal Commerce 2, from start to finish. The video is captured using our Urban Hipster Commerce 2 demo site.

Next week we'll post part 3: Set up a Product Variation Type with Custom Fields

Its important to note that this video was recorded before the official 2.0 release of Drupal Commerce and so you may see a few small differences between this video and the official release now available.

Urban Hipster Commerce 2 Demo site

This video was created using the Urban Hipster Commerce 2 demo site. We've built this site to show the adaptability of the Drupal 8, Commerce 2 platform. Most of what you see is out-of-the-box functionality combined with expert configuration and theming.

More from Acro Media Drupal modules used in this video

Categories: Drupal

BYU Views Card

New Drupal Modules - 25 January 2018 - 8:47am


* Introduction
* Installation
* How to use


Current Maintainer: Katria Lesser, BYU Drupal Users Group

Views BYU Card module uses the styling of the
web componenet BYU-card to display nice cards in views.
You can see the byu-card project in github as well:


Categories: Drupal

Drupal Association blog: DrupalCon Nashville and Tennessee’s Discrimination standing

Planet Drupal - 25 January 2018 - 7:51am

As many already know, DrupalCon North America 2018 will be held in Nashville, TN. The Drupal Association puts a lot of time and effort into choosing a site for DrupalCon North America - a two to three year process that involves request for proposals, several rounds of interviews, site visits and contract negotiations. We do not take this lightly and we include both logistically important and socially relevant questions for review.

Unfortunately, sometimes things happen outside of our control, despite our great lengths of planning. In April 2016, after a 5-month RFP and interview process, we signed a contract with the City of Nashville to host DrupalCon North America 2018. A few weeks later, the State of Tennessee introduced and passed a new law that Drupal Association does not support, and as many community members have pointed out - prevents public employees from the State of California from attending DrupalCon if sponsored by their employer.

For those who have asked, the timeline of events transpired as follows:

  • April 2016: Drupal Association contracted with Nashville, TN to host DrupalCon North America 2018
  • Early May 2016: Tennessee enacted the Amendment Senate Bill No. 1556 House Bill No. 1840
  • January 2017: California enacted restrictions banning state sponsored travel to TN in response to SB1556/HB1840.

Specifically, May 2, 2016. SB1556/HB1840 as enacted, declares that no person providing counseling or therapy services will be required to counsel or serve a client as to goals, outcomes, or behaviors that conflict with the sincerely held principles of the counselor or therapist; requires such counselor or therapist to refer the client to another counselor or therapist; creates immunity for such action; maintains liability for counselors who will not counsel a client based on the counselor's religious beliefs when the individual seeking or undergoing the counseling is in imminent danger of harming themselves or others.

It is unfortunate that this bill became law. The Nashville Convention & Visitors Corporation, who we worked with to contract DrupalCon Nashville, and the greater Nashville business community including the Nashville Mayor’s office believe discrimination has no place in their home state.

In response to this bill and in anticipation of other potential discrimination bills in the future, Nashville Convention & Visitors Corporation became a founding and leading member of Tennessee Thrives, a business coalition of now more than 400 companies across Tennessee who believe that in order for Tennessee businesses and communities to thrive they must be diverse and welcoming for all people, regardless of race, sex, national origin, ethnicity, religion, age, disability, sexual orientation or gender identity. You can read more here about Tennessee Thrives and the Nashville Metro area’s history of social advancements, as well as a statement from the Nashville Convention and Visitors Corporation.

Here is the Tennessee Thrives pledge:

We believe that equal treatment of all Tennesseans and visitors is essential to maintaining Tennessee’s strong brand as a growing and exciting home for business innovation, economic development, a best-in-class workforce, and dynamic entertainment, travel and tourism industries.

In order for Tennessee businesses to compete for top talent, we believe our workplaces and communities must be diverse and welcoming for all people, regardless of race, sex, national origin, ethnicity, religion, age, disability, sexual orientation or gender identity.

As signers of the Tennessee Thrives pledge, we are committed to promoting an attractive, prosperous, and economically vibrant Tennessee. A united Tennessee is a thriving Tennessee.

Tennessee Thrives identified 12 discriminatory bills that were filed in the General Assembly in 2017, and with their efforts only two were approved.

As a further measure of welcome for our Drupal community, the Mayor of Nashville, has extended a Statement of Welcome to the DrupalCon community. They are very excited that DrupalCon has chosen Nashville as their 2018 North American location, and hope we can see past the politics of the larger state to see the welcoming intent of the City of Nashville.

In response to the Drupal community concerns with Nashville as a DrupalCon city, the Nashville Convention & Visitors Corporation offered this statement:

Nashville is an open, welcoming city that respects and embraces the differences among us. We believe that our differences make our community stronger. A sampling of Nashville’s social advancements in contradiction to the actions of TN legislature include:

  • In 2016, the Metro Nashville Council unanimously voted to approve a resolution asking the state legislature to oppose bills opposing the U.S. Supreme Court’s decision on marriage equality. The resolution’s lead co-sponsor was Councilwoman Nancy Van Reese, who is openly gay.
  • On March 21, 2016, Mayor Megan Barry issued an executive order requiring training of all employees of the Metropolitan Government in diversity issues and sexual harassment awareness and prevention.
  • In May, 2016, Nashville hosted the International Gay Rugby Bingham Cup. Mayor Megan Barry served on the Host Committee to bring the Bingham Cup to Nashville.
  • While a mayoral candidate, Mayor Megan Barry officiated the first same-sex marriage in Nashville just hours after the Supreme Court ruled that same-sex marriage is allowed in all 50 states. (During her inauguration in September, 2015, Mayor Barry invited Nashville in Harmony to perform. The group is Tennessee’s first and only musical arts organization specifically created for gay, lesbian, bisexual, and transgender people – and their straight allies. The group performed at events hosted by the previous Nashville Mayor, as well.)
  • While a mayoral candidate, Mayor Megan Barry received the Ally Award from the Nashville LGBT Chamber of Commerce in 2015.
  • In 2011, Nashville extended nondiscrimination protections to employees of the city and contractors.  (Unfortunately, state government nullified the local decision.)
  • In 2009, the Metro Nashville Council passed an ordinance that protects Metro employees from discrimination based on their sexual orientation or gender identity. (Sponsored by then Council Member-At-Large Megan Barry, who now serves as Mayor of Nashville)
  • In 2008, the Metro Nashville School Board approved sexual orientation and gender identity protections for students and staff.

For those concerned about a Tennessee Bathroom Bill, please know that Tennessee has never passed the bathroom bill, it gets killed in process every time it comes up for a vote, including this past March. There is no “Bathroom Bill” in the state of Tennessee. There are also all-gender restrooms offered at the Nashville Music City Center for use during DrupalCon. We understand people's concern with a state that submits this kind of law for consideration. We can possibly all relate to the idea that the actions of lawmakers are not always representative of the greater population, particularly in the greater population of a metro area, and Nashville shares this same concern.

At our core, the Drupal Association believes in community, collaboration, and openness. We work hard throughout the process of DrupalCon planning to be sure that not only the complicated logistics are addressed, but also an accessible space for everyone in our community to feel safe, welcome and comfortable.

In addition to our core DrupalCon programming, we also include the following services at DrupalCon for those who need it.

  • Our Code of Conduct
  • Registration grants and scholarships
  • Interpreters (for the hard of hearing)
  • Special meals: Kosher, Halal, vegan, vegetarian, gluten-free, etc
  • New mother’s room
  • Quiet room and prayer space
  • Venue accessibility and mobility assistance
  • Local AA Meeting information
  • Speaker inclusion fund
  • No-photograph lanyards and communication preference stickers
  • All-gender restrooms
  • Women in Drupal events
  • Inclusion BOFs
  • On-site contacts for incident reporting

You can learn more about all of these services on our DrupalCon Nashville website under On-site Resources.

We believe, despite the current legislative challenges that the City of Nashville is working to overcome at a state level, that we will have a safe, diverse, celebratory space for our community in Nashville this spring. We’re excited to bring DrupalCon to the city of Nashville, and we’re confident it will be an amazing event.

We want to hear about your experiences at DrupalCon and in the cities we visit. Please participate in our post-Con surveys so that we can follow with both our internal teams and host cities if there are areas where the events can be improved for attendees.

Categories: Drupal

Instagram Display

New Drupal Modules - 25 January 2018 - 6:32am

This module can be customized to pull from any Instagram account.

It creates a block showing images from Instagram posts, linked back to the original post.

You can see the block featured on the byu homepage: https://www.byu.edu/about

Categories: Drupal

aleksip.net: Data inheritance in Pattern Lab

Planet Drupal - 25 January 2018 - 4:26am
When Pattern Lab renders a pattern, it does not by default include the data for any included patterns. There are plugins that can be used to include this data, but the many different ways to include patterns within another and to implement data inheritance can cause confusion.
Categories: Drupal

Plaintext Encoder

New Drupal Modules - 25 January 2018 - 3:53am

This module provides Plaintext text format.

It can be used at views_data_export project for export views to txt format.

Categories: Drupal

erdfisch: Drupalcon mentored core sprint - part 3 - what happens next?

Planet Drupal - 25 January 2018 - 3:36am
Drupalcon mentored core sprint - part 3 - what happens next? 25.01.2018 Michael Lenahan Body: 

Hi there! This is the third and final part of a series of blog posts about the Drupal Mentored Core Sprint, which traditionally takes place every Friday at Drupalcon.

If you want to read what came before, here you go:
Part one is here
Part two is here

In this blog post, I would like to show you a little of what happens behind the scenes at the Drupalcon Friday contribution sprint.

The live core commit

The day is completed by the core live commit. This is where one issue that was worked on during the day is committed to Drupal's git repository.

In Vienna, the issue that got committed was https://www.drupal.org/node/2912636, the contributors on Friday were gido and wengerk. They were mentored by the wonderful valthebald, who we met in part two.

This is the moment, when lauriii committed the code to the 8.5.x branch of Drupal, ably assisted by webchick:

Here's the thing about the live commit: anybody in the room could have been up there on stage. Behind the scenes, the mentoring team has been working hard with the core committers to ensure that a commit can be safely made. This is a difficult task: Drupal is a complicated system, it's interesting to see just how much thought needs to go into a seemingly simple commit.

Below is a list of some other issues that were worked on during the Friday sprint at Vienna. Some have since been committed, others still being worked on, even now. The point here is that progress was made on these issues and new contributors helped to move them forward (take a look at what happened in these issues on 29 September, 2017):

Coding Standards
DbLog erroring
SettingsTray disappearing
Add @internal to Form classes
Table drag
Batch missing title on screen
Url alias for private file uploads
Remove #size
Views DISTINCT multilingual
Toolbar uncacheable page

The live commit is a chance for us to celebrate the success of one team, but really all those who worked on the issues above deserve to be celebrated. Our measure for how successful the day has been is whether or not the participants return to the issues after the day is over, and keep using their contribution skills.

Sign up to be a mentor

Are you coming to Nashville? Are you thinking, "maybe I have the skills to be a mentor"? That's great!

Sign up to be a mentor here.

After that, you will get regular emails with instructions on how to prepare for the Mentored Core Sprint.

Don't feel that you need to know the answers to everything in order to be a mentor. You will always have other mentors around you, people you can ask for help when you get stuck.

In the Mentored Core Sprint, we are using a really well-tested process, which we have refined and improved over many years.

The key thing to remember is this: you don't need to fix the issue for the participants. Your job is to teach them how the issue queue works.

Understanding the value of finding the solution is far more important than finding the solution itself.

What to do at Drupalcon

In the exhibition hall, there is a Mentors' Table. Go and say hello, it's a good place to hang out. We have stickers for you, and mentoring cards explaining all the different tasks on offer ...

Keep an eye out on the BoFs board during the week. There are special meetings to prepare first-time mentors, plus a meeting to do issue triage to determine good Novice issues.

Here's a clue: Novice does NOT mean trivial or easy. It means that the steps on the issue are well-defined, and actionable.

Then, show up bright and early on sprint day and have a great time

You'll be wearing the best t-shirt in town.

Here is Rachel, briefing the team before the day starts.

Every year, after it's all over, we meet at a nice restaurant for the mentors' dinner. Thank you to some wonderful companies in the Drupal Community sponsored us last September in Vienna.

So, that's a wrap!

There's a lot more to be said on this topic, but I'll leave it there. I hope I've been able to persuade you to give the Friday core sprint a try, as a participant or as a mentor. It's worth it.

If you're going to Nashville (lucky you), then make sure you stay for the Friday as well.

We're currently planning Drupal Europe. We will most definitely include a Mentored Contribution Day! See you there!

Credit to Amazee Labs and Roy Segall for use of photos from the Drupalcon Vienna flickr stream, made available under the CC BY-NC-SA 2.0 licence.

Schlagworte/Tags:  planet drupal-planet drupalcon mentoring code sprint Ihr Name Kommentar/Comment Kommentar hinzufügen/Add comment Leave this field blank
Categories: Drupal

Layout blocks

New Drupal Modules - 25 January 2018 - 3:35am
Categories: Drupal

Commerce layout blocks

New Drupal Modules - 25 January 2018 - 3:35am
Categories: Drupal

Layout builder enhancer

New Drupal Modules - 25 January 2018 - 3:33am
Categories: Drupal


New Drupal Modules - 25 January 2018 - 2:26am

IndieAuth is an identity layer on top of OAuth 2.0 [RFC6749], primarily used to obtain an OAuth 2.0 Bearer Token [RFC6750] for use by [Micropub] clients. End-Users and Clients are all represented by URLs. IndieAuth enables Clients to verify the identity of an End-User, as well as to obtain an access token that can be used to access resources under the control of the End-User. – https://www.w3.org/TR/indieauth/#abstract-p-1

Categories: Drupal


New Drupal Modules - 25 January 2018 - 2:09am

The Micropub protocol is used to create, update and delete posts on one's own domain using third-party clients. Web apps and native apps (e.g., iPhone, Android) can use Micropub to post and edit articles, short notes, comments, likes, photos, events or other kinds of posts on your own website. – https://www.w3.org/TR/micropub/#abstract-p-1

Categories: Drupal

Site Audit Collector

New Drupal Modules - 24 January 2018 - 1:45pm

Provides a remote JSON endpoint to collect report from site_audit.

Categories: Drupal

TXT Serialization

New Drupal Modules - 24 January 2018 - 1:02pm

This module provides a TXT encoder for Drupal 8 Serialization API. This enables the TXT format to be used for data input and output in various circumstances.

For example:
Drupal 8's REST module can accept or return data in TXT format
Views can output TXT data via a 'REST Export' view
Module developers may leverage TXT as a format when using the Serialization API

Categories: Drupal

Lullabot: Local Drupal Development Roundup

Planet Drupal - 24 January 2018 - 12:35pm

If you’d asked me a decade ago what local setup for web development would look like, I would have guessed “simpler, easier, and turn-key”. After all, WAMP was getting to be rather usable and stable on Windows, Linux was beginning to be preinstalled on laptops, and Mac OS X was in its heyday of being the primary focus for Apple.

Today, I see every new web developer struggle with just keeping their locals running. Instead of consolidation, we’ve seen a multitude of good options become available, with no clear “best” choice. Many of these options require a strong, almost expert-level of understanding of *nix systems administration and management. Yet, most junior web developers have little command line experience or have only been exposed to Windows environments in their post-secondary training.

What’s a developer lead to do? Let's review the options available for 2018!

1. The stack as an app: *AMP and friends

In this model, a native application is downloaded and run locally. For example, MAMP contains an isolated stack with Apache, PHP, and MySQL compiled for Windows or macOS. This is by far the simplest way to get a local environment up and running for Mac or Windows users. It’s also the easiest to recover from when things go wrong. Simply uninstall and reinstall the app, and you’ll have a clean slate.

However, there are some significant limitations. If your PHP app requires a PHP extension that’s not included, adding it in by hand can be difficult. Sometimes, the configuration they ship with can deviate from your actual server environments, leading to the “it works on my local but nowhere else” problem. Finally, the skills you learn won’t apply directly to production environments, or if you change operating systems locally.

2. Native on the workstation

This style of setup involves using the command line to install the appropriate software locally. For example, Mac users would use Homebrew and Homebrew-PHP to install Apache, PHP, and MySQL. Linux users would use apt or yum - which would be similar to setting up on a remote server. Windows users have the option of the Linux subsystem now available in Windows 10.

This is slightly more complicated than an AMP application as it requires the command line instead of using a GUI dashboard. Instead of one bundle with “everything”, you have to know what you need to install. For example, simply running apt install php won’t give you common extensions like gd for image processing. However, once you’ve set up a local this way, you will have immediately transferable skills to production environments. And, if you need to install something like the PHP mongodb or redis extensions, it’s straightforward either through the package manager or through pecl.

Linux on the Laptop

Running a Linux distribution as your primary operating system is a great way to do local development. Everything you do is transferable to production environments, and there are incredible resources online for learning how to set everything up. However, the usual caveats around battery life and laptop hardware availability for Linux support remain.

3. Virtual Machines

Virtual machines are actually really old technology—older than Unix itself. As hardware extensions for virtualization support and 4GB+ of RAM became standard in workstations, running a full virtual machine for development work (and not just on servers) became reasonable. With 8 or 16GB of memory, it’s entirely reasonable to run multiple virtual machines at once without a noticeable slowdown.

VirtualBox is a broadly used, free virtual machine application that runs on macOS, Linux, and Windows. Using virtual machines can significantly simplify local development when working on significantly different sites. Perhaps one site is using PHP 5.6 with MySQL, and another is using PHP 7.1 with MariaDB. Or, another is running something entirely different, like Ruby, Python, or even Windows and .Net. Having virtual machines lets you keep the environment separate and isolated.

However, maintaining each environment can take time. You have to manually copy code into the virtual machine, or install a full environment for editing code. Resetting to a pristine state takes time.


Clearly, there were advantages in using virtual machines—if only they were easier to maintain! This is where Vagrant comes in. For example, instead of spending time adding a virtual machine with a wizard, and manually running an OS installer, Vagrant makes initial setup as easy as vagrant up.

Vagrant really shines in my work as an architect, where I’m often auditing a few different sites at the same time. I may not have access to anything beyond a git repository and a database dump, so having a generic, repeatable, and isolated PHP environment is a huge time saver.

Syncing code into a VM is something Vagrant handles out of the box, with support for NFS on Linux and macOS hosts, SMB on Windows hosts, and rsync for anywhere. This saves from having to maintain multiple IDE and editor installations, letting those all live on your primary OS.

Of course, someone has to create the initial virtual machine and configure it into something called a “base box”. Conceptually, a base box is what each Vagrant project forks off of, such as ubuntu/zesty. Some developers prefer to start with an OS-only box, and then use a provisioning tool like Ansible or Puppet to add packages and configure them. I’ve found that’s too complicated for many developers, who just want a straightforward VM they can boot and edit. Luckily, Vagrant also supports custom base boxes with whatever software you want baked in.

For Drupal development, there’s DrupalVM or my own provisionless trusty-lamp base box. You can find more base boxes on the Vagrant website.

4. Docker

In many circles, Docker is the “one true answer” for local development. While Docker has a lot of promise, in my experience it’s also the most complicated option available. Docker uses APIs that are part of the Linux kernel to run containers, which means that Docker containers can’t run straight under macOS or Windows. In those cases, a lightweight virtual machine is run, and Docker containers are run inside of that. If you’re already using Docker in production (which is its own can of worms), then running Docker for locals can be a huge win.

Like a virtual machine, somehow your in-development code has to be pushed inside of the container. This has been a historical pain point for Docker, and can only be avoided by running Linux as your primary OS. docker-sync is probably the best solution today until the osxfs driver gets closer to native performance. Using Linux as your primary operating system will give you the best Docker experience, as it can use bind mounts which have no performance impact.

I’ve heard good things about Kalabox, but haven’t used it myself. Kalabox works fine today but is not being actively developed, in favor of Lando, a CLI tool. Pantheon supports taking an existing site and making it work locally through a Kalabox plugin. If your hosting provider offers tooling like that, it’s worth investigating before diving too deeply into other options.

I did some investigation recently into docker4drupal. It worked pretty well in my basic setup, but I haven’t used it on a real client project for day-to-day work. It includes many optional services that are disabled out of the box but may be a little overwhelming to read through. A good strategy to learn how Docker works is to build a basic local environment by hand, and then switch over to docker4drupal to save having to maintain something custom over the long run.

ddev is another “tool on top of docker” made by a team with ties to the Drupal community. It was easy to get going for a basic Drupal 8 site. One interesting design decision is to store site files and database files outside of Docker, and to require a special flag to remove them. While this limits some Docker functionality (like snapshotting a database container for update hook testing), I’ve seen many developers lose an hour after accidentally deleting a container. If they keep focusing on these common pain points, this could eventually be one of the most friendly Docker tools to use.

One of the biggest issues with Docker on macOS is that by default, it stores all containers in a single disk image limited to 64GB of space. I’ve seen developers fill this up and completely trash all of their local Docker instances. Deleting containers often won’t recover much space from this file, so if your Mac is running out of disk space you may have to reset Docker entirely to recover the disk space.

When things go wrong, debugging your local environment with Docker requires a solid understanding of an entire stack of software: Shells in both your host and your containers, Linux package managers, init systems, networking, docker-compose, and Docker itself.

I have worked with a few clients who were using Docker for both production and local development. In one case, a small team with only two developers ended up going back to MAMP for locals due to the complexity of Docker relative to their needs. In the other case, I found it was faster to pull the site into a Vagrant VM than to get their Docker containers up and running smoothly. What’s important is to remember that Docker doesn’t solve the scripting and container setup for you—so if you decide to use Docker, be prepared to maintain that tooling and infrastructure. The only thing worse than no local environment automation is automation that’s broken.

At Lullabot, we use Docker to run Tugboat, and for local development of lullabot.com itself. It took some valiant efforts by Sally Young, but it’s been fairly smooth since we transitioned to using docker-sync.

What should your team use?

Paraphrasing what I wrote over in the README for the trusty-lamp basebox:

Deciding what local development environment to choose for you and your team can be tricky. Here are three options, ordered in terms of complexity:

  1. Is your team entirely new to PHP and web development in general? Consider using something like MAMP instead of Vagrant or Docker.
  2. Does your team have a good handle on web development, but are running into the limitations of running the site on macOS or Windows? Does your team have mixed operating systems including Windows and Linux? Consider using Vagrant to solve all of these pain points.
  3. Is your team using Docker in production, or already maintaining Dockerfiles? If so, consider using docker4drupal or your production Docker containers locally.

Where do you see local development going in 2018? If you had time to completely reset from scratch, what tooling would you use? Let us know in the comments below.

Categories: Drupal


Subscribe to As If Productions aggregator - Drupal