Authoritarian structure in Drupal: a case study

Posted by Chocolate Lily - 5 May 2017 at 19:37 UTC

In the current context of a Drupal leadership crisis and debate about project governance, it's important to reflect on ways the dictatorship structure has shaped and continues to shape the culture of the project. In this vein, response to a 2007 post by Drupal contributor Gus Geraghty makes for a fascinating, if disturbing, case study.

I recommend reading (or rereading) that thread before continuing here. I've deliberately chosen an example from earlier days to emphasize how tensions in the project, and patterns of response, have persisted and shaped the project at key junctures. I also hope that some distance may help to set those events in a reflective light, where the focus is not on who did what but on what we can learn about the overall organizational culture.

Those who raise critical questions are making a valuable contribution. Particularly in an authoritarian structure, speaking up is risky.

In his post and followup comments, Geraghty directly questioned the dictatorship power structure of Drupal, focusing on the then-new commercial interests of Drupal founder and dictator for life, Dries Buytaert, and his company, Acquia. Geraghty proposed a concrete alternative: reorganizing the project along cooperative lines. In follow-up comments, he pointed to the Linux Foundation as a possible model, structured to ensure no one company could attain dominance in the software project:

it fosters the growth of Linux by focusing on protection, standardisation and providing a neutral forum for collaboration and promotion. It also sponsors the work of Linus Torvalds, as opposed to a commercial interest paying Linus.

The response was immediate, pointed, and overwhelming.

The Process for Evolving Community Governance

Posted by Drupal Association blog - 5 May 2017 at 18:59 UTC
Discover > Plan > Build > Iterate

There comes a time when we must all recognize that what got us here won't get us there. Now is that time for Drupal. The governance models that were put in place to support the needs of the community years ago are no longer working as well as they should. The Drupal community has reached a level of maturity that requires greater clarity, integrity, and resilience.

An effort is underway to evolve Drupal’s community governance. The Drupal community is in the driver’s seat. The Drupal Association is helping navigate and get the community where it wants to go by providing the structure, support, and resources that are desperately needed to make progress. I, Whitney Hess, have been engaged to be a neutral facilitator of this process.

We are proposing a multi-phase approach to redesign Drupal’s community governance models, management, and decision-making practices: Discover > Plan > Build > Iterate. In this first phase, our goal is to gain a deeper understanding of the needs of the Drupal community. We are conducting this research through a variety of methods: one-on-one interviews with select individuals; mediated group discussions; surveys and feedback forms.

We held seven hour-long Community Discussions over three days of DrupalCon. There were 6-10 participants per session. Though every session had its own energy and topics varied, all discussions were fruitful and impactful. Many participants said they left feeling better than when they arrived.

While there was some discussion about recent events in the sessions, the focus quickly shifted to brainstorming ideas for how to improve Drupal’s community governance. As mediator, it is my role to help people articulate their needs, and to support the community in devising strategies to better get those needs met. Please read the meeting summaries if you would like to get a sense of what was discussed.

There are currently seven online sessions scheduled over the next two weeks at a variety of times for the global community to participate in these facilitated discussions, and more will be scheduled if needed. If you want your voice heard, I strongly encourage you to join us. If you have questions or concerns about the sessions, you’re welcome to contact me directly at whitney@whitneyhess.com.

Once these sessions are completed, we will be conducting a short survey and other types of feedback forms to have the widest possible reach. We want to ensure that people have a variety of ways to constructively contribute to making Drupal the best it can be. We expect to launch these in late-May.

At the conclusion of the Discovery phase, we will move into Planning. We are at the earliest stages of conceiving a Governance Summit over 1-2 days in June to take all of the learnings from Discovery, and craft a strategy for specifically how to change Drupal’s community management and governance. As of today, we do not yet have dates, location, or participant information. We are waiting to see what comes out of Discovery before we devise any framework for how this can be achieved effectively and equitably. Again, the Drupal Association’s role here is to be a support, and to create space for the community to decide how it wants its governance to change.

I have very clearly heard a need for greater transparency into this process and how decisions are being made. I take that responsibility seriously, and will continue to share our progress along the way. Next up, please look out for a summary of our Discovery findings, to be shared in late-May/early-June.

With gratitude,

Whitney

Baltimore DrupalCon - Favorites From Charm City

Posted by Hook 42 - 5 May 2017 at 18:50 UTC
The girls from Hook 42 at DrupalCon Baltimore

Every year DrupalCon brings the community together. This year we were fortunate enough to have eleven of our team come together in Baltimore! We had a ton of fun while Drupaling and want to share a few of our favorite moments!

Competitive Analysis: The Key to a Woman’s Healthy Heart - Part 2

Posted by Palantir - 5 May 2017 at 17:23 UTC
Competitive Analysis: The Key to a Woman’s Healthy Heart - Part 2 brandt Fri, 05/05/2017 - 12:23 Michelle Jackson May 5, 2017hand holding red heart

Competitive user testing can validate the conclusions that are made from a preliminary competitive analysis.

In this post we will cover...
  • How health systems can conduct competitive usability testing

  • How navigation organization and prioritization impacts the ability of people to find information on specific health topics such as heart disease and its impact on women’s health

  • How competitive analysis can help health systems improve information architecture to better serve people suffering from critical illnesses

  • How looking at peer competitors can help health systems better serve the needs of patients and their caregivers

We want to make your project a success.

Let's Chat.

Heart disease is the No. 1 cause of death for women in the United States. We are homing in on on DrupalCon-host city Baltimore, which has launched several initiatives to combat cardiovascular disease. Johns Hopkins Medicine and the University of Maryland Medical Center are two large university hospitals local to Baltimore that have centers dedicated to women and heart disease. Using women’s heart health as our focus, we compared select search outcomes, menu hierarchy, labeling, and landing pages.

Step 1 was a cursory competitive analysis of two health system websites that we covered in part 1. Step 2 is competitive user testing to validate the conclusions that we made from the preliminary competitive analysis.

Competitive user testing is a useful way to see how your site measures up against your competitors’ sites. By taking a look at how patients may interact with your site and competitor sites, you can compare their experience and make changes that allow you to better serve patients’ specific needs. You can implement competitive usability testing even if you have not completed a preliminary competitive analysis.

Since we last discussed websites and women’s heart health, we held two user tests to compare site visitors’ experiences when navigating the Hopkins Medicine and University of Maryland Medical Center (UMMC) health system websites.

We chose tasks based on actions that people might perform on a health system website. We also considered the type of information women look for when seeking information on heart disease.

For our user tests, we asked two women who are Maryland residents between the ages of 40 and 70 to complete several tasks on both the Hopkins Medicine and University of Maryland Medical Center websites without using search.

Tasks we asked participants to perform:

  1. Learn if you are at risk for heart disease
  2. Share information about the risks of heart disease
  3. Find a physician
  4. Schedule an appointment
  5. Find directions
  6. Pay a bill
  7. Find a program or center related to women and heart health
Select Findings

We found:

  • “Health” and “Healthy Heart” labels provide users with a quick pathway to heart health risk information
  • Users successfully completed the majority of top tasks (i.e. schedule an appointment)
  • Finding programs and information about risks associated with women’s heart health is challenging
  • Multi-level navigations and redundant label terminology created complex pathways for users

table 1

table 2

The experiences of these two women revealed some challenges that might be experienced by other site visitors. Our findings warrant additional usability testing to further evaluate, compare how these and other health system websites help patients seeking information about programs and centers that address women’s heart health.

“I would never [pay my bill] this way, I would pay it online [through my bank].”

Highlights and Challenges

“Health” and “Healthy Heart” labels provide users with a quick pathway to heart health risk information.

On the Hopkins Medicine’s health system website, both the first and second participants successfully found “know your risks” on the Healthy Heart landing page (see Figure 2) when looking for information about heart disease risk. The second participant said Hopkins Medicine performed better than its UMMC counterpart in describing the factors that put people at risk for heart disease.

When navigating the UMMC website, the second participant navigated to the Women’s Heart Health Program landing page and said the description of risks were symptoms associated with heart disease and not actual risks. “They don’t say, blood pressure, overweight, sleep apnea,” she commented. The first user did not locate risks for heart disease on the UMMC website.

Figure 1: Hopkins Medicine Healthy Heart navigation menu

 Hopkins main and secondary navigation labelsHopkins Medicine’s main and secondary navigation labels (Health > Healthy Heart) gave users quick access to information on heart disease risk.

Figure 2: Hopkins Medicine Healthy Heart landing page

 Hopkins Medicine Healthy Heart landing page“Know Your Risks” featured prominently within Healthy Heart local navigation makes heart disease risks easily accessible to users.

Figure 3: UMMC Women’s Heart Health Program landing page

 UMMC Women's Heart Health Program landing pageUMMC’s women’s heart program landing page does not present information about heart disease risks that is easily accessible.

Participants successfully completed the majority of top tasks (i.e. schedule an appointment). 

Both users successfully completed the majority of top tasks such as find a physician, schedule an appointment, find directions, and pay a bill. The first participant did not find a way to get physician on the UMMC homepage and Heart & Vascular Center landing page. This may have been because of the placement of the calls to action in the sidebar (Figure 5), adjacent competing content (Figure 5) and the utility navigation and the “Find a Doctor” call to action button similarity in color (Figure 4).

“If I wanted to find a physician I woul[d] ...call a heart specialist first.”

Figure 4: UMMC main navigation and “Find a Doctor” call to action button

 UMMC main navigationCalls to action for top tasks such as “Make an appointment” and “Find a doctor” blend in with utility navigation colors, which could make it hard for users to see these key buttons

Figure 5: UMMC Heart and Vascular Center landing page

 UMMC Heart and Vascular Center landing pageCalls to action for top tasks such as “Make an appointment”  and “Find a Doctor” compete with UMMC Cardiologists video and hero news story “One Family, Two Heart Transplants” content.

Finding programs and information about risks associated with women’s heart health is challenging.

The first participant did not find either the Hopkins Medicine or UMMC’s programs nor centers related to women and heart health, even when visiting pages that were dedicated to cardiology or cardiovascular health. The first participant visited UMMC’s programs listing page, which contained separate links to women’s health and heart and vascular health pages, but did not list the Women’s Heart Health Program under either of these headers (see Figures 6 and 7).

After the first participant clicked on the Heart and Vascular Center landing page, she scanned Services, but did not find the Women’s Heart Health Program because the secondary navigation extends below the top half of the page masking the Women’s Heart Health Program. The first participant also was unsuccessful in finding a program or center related to women and heart health information on the Hopkins Medicine health system website. “I can find heart stuff, I just can’t find anything on women,” she said.

The second participant was able to find the Women’s Heart Health Program on the UMMC site; however, she remarked that it was challenging to locate: “It’s not intuitive how you would find a program here. Now I see it, but not before I’ve gone through too many exercises.” 

Figure 6: UMMC programs landing page

 UMMC programs landing pageWomen’s Health section on programs landing page has no mention of the women’s heart health program

Figure 7: UMMC programs landing page

 UMMC programs landing pageHeart and Vascular Center section on programs landing page has no mention of the women’s heart health program

Figure 8: UMMC Heart & Vascular Center landing page

 UMMC Heart & Vascular Center landing pageThe local navigation for the Heart and Vascular Center landing page has items under “Services” that extend beyond the top of the page. One user stopped at Pulmonary Hypertension and missed the last item in the “Services” dropdown, “Women’s Heart Health.”

Multi-level navigations and redundant label terminology created complex pathways for users.

Participants had difficulty remembering how they got to specific pages because of redundant label terminology and deeply nested pages. When looking for information on risks for heart disease, the first participant had trouble using the main, secondary and local navigation to find this information, selecting Health information > Medical encyclopedia > Look up a symptom > Medical Encyclopedia > Your Health only to go back to the main navigation to click on Centers and Services and Patients and Visitors.

“I would always call because half the time it gets lost when you do it through the portal.”

Takeaways

We can gain a more nuanced understanding of how diverse patient demographics navigate and use health system websites by conducting competitive usability tests and focusing on a specialized medical issue such as women’s heart health.

While this study warrants additional research and usability testing given the small number of users, it does reveal challenges that are faced by many of our clients in the health care industry like navigation and findability.

To better serve patients and their caregivers, health system websites can take several steps to improve the experience for site visitors:

  • Simplify their menu structure so that there are fewer levels and sub-navigations
  • Remove competing content from areas of the page and improve color contrast, helping users access key buttons like “make an appointment” and “find a doctor”
  • Reference and cross link to women’s heart health centers and programs on program pages
  • Provide related content on pages that have resources on heart health and women’s health to improve findability
  • Revisit alphabetizing navigation items in favor of featuring top specialities and health areas that are of primary importance to patient audiences.

In the health care field, meeting the needs of patients can be a matter of life and death. It is important for health systems to continually evaluate how their websites are meeting the needs of patient and caregivers and how they can improve the experience for patients and caregivers and best facilitate access to information about health services and resources.

We want to make your project a success.

Let's Chat.

Creating an Events Calendar in Drupal 8

Posted by Evolving Web - 5 May 2017 at 16:53 UTC
Calendar

If you have ever worked with sites that deal with events, you've probably been asked to create some type of calendar display. In this article, we'll discuss how to set up a basic events calendar using the Calendar (8.x-1.x-dev) for Drupal 8.

Configure the event content type

In our example, to handle events, we create a new content type called Event. You can put any content type in a calendar as long as it has a Date field. Though we might need date ranges to handle multi-day events, at the time of writing this article, there is no support for using the date range field with the calendar module, so we will use a simple date field for this example.

Event node formThe Event node form. Right now, events only have a title, description and a date field labelled Schedule.

Configuring the "events" view

With the node type in place, the next step will be to display the nodes using a view, using calendar display settings. To create a view with the calendar settings in place, you can go to Structure > Views > Add view from template page (admin/structure/views/template/list). Here, we choose the template which allows us to create a calendar for our date field.

We click the Add button corresponding to the date field (which we called Schedule).

The template provides you some options to configure certain aspects of the calendar to be generated, namely:

  • View name
  • Description
  • Base view path: The base path to use for the calendar pages and tabs. In our example, we choose events as the base so the calendar will generate paths like:
    • events/day: For a day-wise view
    • events/week: For a week-wise view
    • events/month: For a month-wise view
    • events/year: For a year-wise view

From the views configuration page, we can also configure the path for our calendar page(s) and create blocks with mini-calendars.

Calendar view generation optionsSome settings for the calendar to be generated.

Once done fine-tuning, we save the view and visit the relevant front-end page, which in this example is events/month. Here's how the calendar looks out of the box with the Bartik theme.

How the calendar looks in front-end

Conclusion

The calendar module will be a great contrib module while working with calendars. However, it may or may not serve your needs depending on your project requirements. Here are certain points (at the time of writing this article) which might affect the usability of this module:

  • No support for date range: Lack of support for date ranges makes it hard to work with multi-day event scenarios.
  • No support for start & end date: Though we can setup two separate date fields for start and end date, multi-day events are not visible as multi-column rows in the calendar.

 

+ more awesome articles by Evolving Web

How can we help you?

Posted by Jacob Rockowitz - 5 May 2017 at 16:39 UTC

Within the Drupal community, we’re all familiar with the problem "How can I support myself writing free software?" For me, I am passionate about Open Source because it allows online communities to openly collaborate and build amazing software. In short, Open Source is about collaboration and community and "free" software is a bi-product and possibly a misnomer. Perhaps this “free” bi-product should be viewed differently - Open Source developers should get paid for their hard work.I am now facing this challenge.

I’ve decided to start experimenting with getting people to sponsor/hire me by asking, "How can I help you with Webform and Drupal 8?" This question is on my website, my business card, and at the end of every Webform-related screencast. Along with this inquiry , I’m trying to provide what I hope is a high level of quality, value, and user experience within the Webform module. This experience includes inline videos, maintained documentation, and a 24-hour response time for most issues. In essence, I’m seeking to create opportunities that will result in financial gain for my hard work. At the same time, I want to emphasize that I am respectful of the Drupal community's feedback. This ticket, from YAML Form module's issue queue, is the best example of me responding to constructive criticism, which helped me to properly embed YouTube videos within the Webform module.

My journey towards, for lack of a better word, "profitability" is ongoing. At the same time, I feel a respectful and grateful obligation to also take the Drupal community with me on this journey.

First off, the single most significant ongoing source of pride I get for the maintaining the Webform module is being able to welcome new users to the Drupal community. I’ve even started to tweet welcome messages to new users.

At DrupalCon, I had a few...Read More

Beyond Code - Contributing to Community Spirit

Posted by Acquia Developer Center Blog - 5 May 2017 at 15:07 UTC
//www.flickr.com/photos/lifeisaprayer/33452519983/

How the DrupalCon Prenote helps us laugh, learn, and be a community. Four other Acquians joined me on stage in the DrupalCon Baltimore Prenote, helping spread a little joy and silliness. Drupal gets better when companies, organizations, and individuals build or fix something they need and then share it with the rest of us. Our community becomes better, stronger, and smarter when others take it upon themselves to make a positive difference contributing their knowledge, time, and energy to Drupal. Acquia is proud to play a part, alongside thousands of others, in making tomorrow’s Drupal better than today’s.

Tags: acquia drupal planetdrupalconBaltimorecontributioncommunity

Getting Started With Drupal Commerce 2.x - Part 1

Posted by Valuebound - 5 May 2017 at 14:59 UTC

Drupal Commerce 2.x overview

E-commerce in Drupal 8 is a very interesting topic for many developers and this blog is the right place to start with E-commerce in drupal 8.

Drupal Commerce 2.x is the module for creating online stores of varying complexity. This blog provides an overview of the Commerce 2.x module for Drupal 8.

In this blog, we will be focusing on following things

Installing Drupal E-Commerce 2.x

To install Drupal Commerce, make sure that your server has a Composer dependency manager installed. In Drupal 8,…

Using the CiviCRM Entity Reference Field submodule with Inline Entity Form

Posted by CiviCRM Blog - 5 May 2017 at 14:15 UTC

CiviCRM Entity Reference Field is a submodule of the CiviCRM Entity project. One of the many advantages of installing the CiviCRM Entity module is the ability to use Drupal’s Entity Reference module to reference CiviCRM data from nodes, terms, or other entity types. Many people are using the Inline Entity Form module, which provides field widgets that allow you to create, edit, or delete a referenced entity from the parent form.

If you reference CiviCRM contacts via an Entity Reference field and use Inline Entity Form, you’ll often want to include the ability for the user to create or edit subsidiary CiviCRM entity types, such as the email, phone, and address entities. This can get tricky with CiviCRM integration. A regular entity reference field stores a target entity id in a Drupal field table of the Drupal database.  CiviCRM Addresses are stored in the CiviCRM database, and can be created by different types of users and in many different ways. In addition, Drupal and CiviCRM reference data in opposite ways.  Drupal’s field model, “forward references,”  which means the entity stores the ids of the child entities. CiviCRM generally uses “backreferences,” meaning the child entity will store the parent entity’s id.  To make the situation even more interesting, this pattern is not consistently followed in CiviCRM, and you’ll occasionally have a “forward reference”. For example, events store a location block id, and the location block references addresses.

We want the convenient and familiar interface of the Inline Entity Form/Entityreference combination, but we want to use the existing data from the CiviCRM tables, and not store target ids in Drupal field tables, while at the same time being flexible enough to go both ways. We want to make a square peg to fit into a round hole. What we needed was a “remote reference field”.

The Drupal Field API is very powerful, and it allows you to make field types that are disconnected from the standard Drupal field tables. The solution is CiviCRM Entity Reference Field, which adds a new field type that can be added to any CiviCRM entity type.

We’ve successfully used this module for a variety of use cases, including:

  • Referencing emails, addresses, phones from contacts
  • Referencing participants from events
  • Referencing relationships from contacts
  • Referencing activities from contacts
  • Referencing contacts from activities
  • Referencing contacts from relationships

It is also possible to have CiviCRM Entity Reference (CER) fields on entities referenced by CER fields. For example, In CiviCRM, Events reference location blocks, which in turn reference addresses. To edit profiles on Events, you need to reference UFJoin from Events.  The UFJoin entity type needs a UFGroup reference field which needs to reference UFField. That case is especially interesting as that “line of reference” runs both forward and backwards from the UFGroup entity.

That’s the what and the why, to see an example of how to use it, please continue reading this article on Skvare.com.

ToolsCiviCRMDrupalExtensions

How to create a headless Drupal site

Posted by ADCI Solutions - 5 May 2017 at 08:52 UTC

Once upon a time there was a trend of headless Drupal websites. But time passed and we realised that the Decoupled Drupal approach is more than the trend. It makes a developer’s life easier since back-end and front-end teams can work separately. Decoupled websites are able to serve content on different platforms better.

 

So why don’t we try to build a decoupled website on our own? For the front-end part we’ll use React, for the back-end - Drupal.

 

Read the tutorial.

 

Accelerated Mobile Pages (AMP) with Google’s Paul Bakaus

Posted by Lullabot - 4 May 2017 at 22:00 UTC
Mike and and Matt are joined by Paul Bakaus, who is the AMP developer advocate at Google, as well as Lullabot senior developer (and AMP module creator) Matthew Tift to talk all things Accelerated Mobile Pages.

Dries, Acquia, and the Drupal Association--Some Essential History

Posted by Chocolate Lily - 4 May 2017 at 21:31 UTC

In recent weeks Drupal community members have raised many questions about the Drupal Association (DA). Can the DA serve as an effective balance to the powers of the project's dictator for life, Dries Buytaert? Why does Buytaert have his name written into the bylaws with a reserved board seat? Is the DA structured in such a way that it could reliably address potential conflicts of interest involving Buytaert's company, Acquia? What's the history?

Community members have also raised questions about transparency in the Drupal Association.

In the absence of reliable information, speculation has been rampant.

These questions come as the Drupal Association has announced plans to facilitate a process of community consultation around governance of the Drupal project. For these discussions, it's especially important that community members have access to frank information and perspectives about the DA.

In this piece I hope to help address the knowledge gap by filling in some of that missing background. I have years of experience in the two incarnations of the Drupal Association--the Belgian-based VZW (the first Drupal Association, which I'll here call DA-VZW) and the US-based Drupalcon Inc (the current Drupal Association, which I'll here call the DA). This experience includes:

That said, comments here are my own and in no way reflect the views of either DA-VZW (which, in any case, is now defunct) or the DA.

A bland backgrounder I compiled in 2012 may be useful by way of intro, but in what follows here I promise way more of the gritty detail!

256: Drupal 8 Certification Crash Course at Texas Camp 2017!

Posted by Acquia Developer Center Blog - 4 May 2017 at 17:09 UTC
Texas Camp 2017

At DrupalCon Baltimore, I got the chance to chat with David Porter and David Stinemetze from Rackspace. Listen to this conversation to learn a little more about the Daves, Drupal at Rackspace, and the value of Acquia's certification program to individuals and organisations. If you can make it, don't miss your chance to get a 10% discount on taking an Acquia certification exam by taking the Drupal 8 certification crash course at Texas Camp 2017!

The Texas Camp 2017 Drupal 8 Certification Crash Course: a full day of Drupal 8 learning goodness on June 2nd!

"We're hoping to get as many people certified as possible" - Dave Porter

Crash Course Origin Story

I asked Dave Stinemetze what he was looking for coming to DrupalCon Baltimore: "At Rackspace, we're currently on Drupal 7; we're looking to move to Drupal 8. One of the things our team wanted to do was increase our competency with Drupal 8, which included going to sessions, seeing lessons learned from companies who have already made this migration ... you know, starting to get a game plan together."

Both Daves recently got Acquia Drupal 8 certification. I asked about their motivation for doing that. Dave Stinemetze explains, "I've spent so much time in Drupal 7 and Drupal 8 ... it's an idea. It wasn't something I'd had hands on experience with. For me, doing the certification was actually my introduction to transitioning from D7 to D8. I just went head down into the study guides, into the manuals, everything I could find. I started aggregating all these data, taking notes ... [on] all these things that have changed. I placed all my notes up on Guthub, so they're available for anyone."

Why Certification?

Dave Porter adds, "Originally, when I got the D7 certification, I was the only one in San Antonio ... and until Monday, I was still the only one. That was a nice credential to have for myself and for Rackspace. It's important to know that Acquia did the right thing, forcing the fact that there needed to be certification. There needed to be something to give people some kind of credential to validate that they know what they're doing. Because Drupal gives all of us a job. And for us to work in the technology and profession we like, to be who we are, to wear what we want, to go where we want to go and be a part of this community. That certification only solidifies that even more."

"It's important to know that Acquia did the right thing, forcing the fact that there needed to be certification. There needed to be something to give people some kind of credential to validate that they know what they're doing."

"If you go to any of the big agencies and you've got that credential, it's going to separate you from the rest of the people (unless you're one of the big names). But other than that, it's a path for a lot of the people that are coming into Drupal. Drupal is growing; it's appealing to more developers, especially more PHP developers. So giving them a path, a way into the community that really verifies their knowledge and competence, I think it's invaluable."

Dave Stinemetze rounds out the picture, pointing out that being a verified expert also helps internally at Rackspace (and I' sure this goes elsewhere, too), "We're selling ourselves to our stakeholders and we're creating that perception of expertise within our own business. That has value in and of itself."

Conversation Video

Links, References
Podcast series: Drupal 8Skill Level: BeginnerIntermediateAdvanced

Does using drush uli in D8 and getting http://default drive you mad?

Posted by Aten Design Group - 4 May 2017 at 15:27 UTC

In Drupal 8, setting your sites domain in settings.php is no longer possible. In Drupal 7, you could set the base_url in settings.php like:

$base_url = 'http://domain.com';

Have you noticed in Drupal 8 that when you use drush uli it returns a url that starts with http://default! If you are tired of copying and pasting what comes after http://default/ or adding the --uri=http://domain.com flag along with drush uli I have a solution for you!

Meet the drushrc.php file. I prefer to put this one level higher than my Drupal root. So…

  • Project repo
    • webroot (public_html, web, docroot, etc)
    • drush/drushrc.php

Lots can go in the drushrc.php file, but if you simply want to fix the drush uli default issue, it can just have:

<?php
 
$options['url'] = 'http://domain.com';

If you are using GIT to manage your code base, you could consider a strategy of a drushrc.php file per environment. Example:

Create drush/drushrc.local.php

That file can contain:

<?php
 
$options['url'] = 'http://domain.dev';

Your main drushrc.php now looks like:

<?php
 
/**
 * If there is a local drushrc file, then include it.
 */
 
$local_drushrc = __DIR__ . "/drushrc.local.php";
if (file_exists($local_drushrc)) {
  include $local_drushrc;
}

Now you can place drush/drushrc.local.php in your .gitignore file.

If you are using a PaaS like Pantheon, you can take this strategy:

Since Pantheon automatically handles setting the $options[‘url’] for you, you can simply say...if NOT Pantheon, use my local dev domain.

With the Pantheon approach, your drushrc.php file can look like:

<?php
 
if (!isset($_SERVER['PANTHEON_ENVIRONMENT'])) {
  $options['url'] = 'http://domain.dev';
}

I believe setting the $options[‘url’] has always been possible if using drush aliases, so continue on if you’ve always done that.

Now enjoy the infinite bliss when typing drush uli and having the correct domain returned.

Girls Day 2017 at erdfisch

Posted by erdfisch - 4 May 2017 at 15:26 UTC
Girls Day 2017 at erdfisch 04.05.2017 Michael Lenahan Body:  Girls Day 2017 at erdfisch

Every year here in Germany we have Girls' Day. This is a day in which girls can see what it is like working in male-dominated industries (there is an equivalent Boys' Day as well).

We at erdfisch have been taking part in Girls' Day since 2015, so this was our third year. We had the privilege of welcoming Anna, Bianca and Franzi into our office in Heidelberg.

Why do this?

Why is it worth our time taking part in something like this?

Well, if you need a reminder of what a privilege it is to do your job, spend a day explaining the miracle that is open source web development to some teenagers.

I'm very proud of the fact that we are more than just a bunch of developers - in our work, we interact with other developers from other countries and other companies every day.

We meet at international events like the incredible Drupalcamp that took place in Iceland earlier this year.

We are participants in an extremely open way of working.

When explaining to teenagers how Drupal gets developed, you start to realise what an incredible privilege it is to have such a career.

It is, in itself, so much fun to explain why people around the world share their their time and talent for free, and how the economics of open source actually works.

It's more than just a job. It's a career or "calling" (in German, the word "Beruf" for career and "Berufung" for calling are very close).

And there is no reason why this privilege should only be available to men and not women.

Learning open source through Drupal site building

For me and my colleague Peter, Girls Day was a day in which we took time out from our work to explain how Drupal works, and to provide a full day's site building training.

This is a great benefit to us because it helps us to appreciate what it's like to be a beginner again, and to be a site builder.

It makes you find good examples of contributed modules that you can use to introduce the idea of Drupal's incredible extensibility.

We got the girls set up on https://pantheon.io/ - Pantheon is a great platform for trainings like this.

We introduced extensibility by swapping out the default Bartik theme with a modern alternative https://www.drupal.org/project/robotic.

Robotic has a nice slideshow function so that the girls could quickly personalize their sites with colors and slides.

Next, we got to working with content types and fields. We introduced the concept of adding a new type of field through the contributed geolocation module, which allows you to create a field with a location on a Google map.

From there, it was about adding our content, and then displaying content with views. We used calendar module to show how it was possible to build sophisticated views.

It didn't take long before the girls were working on their own concepts.

Anna built a showcase for her mother's store: http://dev-anna-felix.pantheonsite.io/

Bianca build a site which allows her schoolmates to log in and cast votes and choose destination for their school outing: http://dev-klassenfahrt.pantheonsite.io/

Franzi built a site for her music school orchestra: http://dev-musikschulorchester-wiesloch.pantheonsite.io/

Drupal 8 is getting to where we want it to be

It's been interesting running this event over the past three years, because we've been able to take a snapshot each year of how Drupal 8 is progressing in real life.

We're now at the point where Drupal 8 finally feels stable and fun to work with.

It's where we want it to be - a system which you can spend a day learning and really achieve something worth while. And understand how far you can go with it.

And how rewarding it is to be a part of this incredible thing. Don't let sexism, racism, snobbishness or any other thing exclude you from it.

Schlagworte/Tags:  planet drupal-planet Ihr Name Kommentar/Comment Kommentar hinzufügen/Add comment Leave this field blank

Pipelines Beta UI is Now Available!

Posted by Acquia Developer Center Blog - 4 May 2017 at 13:52 UTC
cloud

We’re happy to announce that the web user interface for the Acquia Pipelines beta is now available to all those beta participants with subscriptions on Acquia Cloud! In addition to the CLI, we've now provided a great UI to enhance reporting and usage inside of the Cloud UI.

Tags: acquia drupal planet

Why Drupal is an ideal solution for your dropshipping site

Posted by InternetDevels - 4 May 2017 at 13:14 UTC
Why Drupal is an ideal solution for your dropshipping site

Commerce is rapidly shifting to the Internet nowadays, because it is a vast territory that 
allows you to find sellers and buyers worldwide and make orders at any time. Maybe
you even have already created your own e-commerce site on Drupal.

Read more

Pages

Subscribe with RSS Subscribe to Drupal.org aggregator - Planet Drupal