Drupal News

Specbee: Enhancing Drupal front end performance through Pattern Lab

Main Drupal Feed - Tue, 04/27/2021 - 12:34
Enhancing Drupal front end performance through Pattern Lab Vinit Kumar 27 Apr, 2021 Top 10 best practices for designing a perfect UX for your mobile app

Component-driven theming is becoming widely popular today because of various reasons. The most significant being reusability and portability of components. Pattern lab is a front-end framework that uses an atomic design architecture to implement a component-based design. In this article, we will discuss more about Pattern Lab and how you can enhance your Drupal frontend performance with it.

What is Pattern Lab?

Think of Pattern Lab as an application that can help you organize your UI components in a pattern-driven approach. It is basically a static site generator that binds together all the UI components together. Pattern lab uses atomic design to accelerate the process of creating modular designs. It starts out really basic and gets more complex as you move up the ladder.

Credit: Pattern Lab

Let’s breakdown these visual building blocks:

Atoms: They are the most basic building blocks of your design. For example, UI elements like buttons, search fields, form elements, labels.

Molecules: They are groups of atoms that work together to perform a particular action. For example, a search navigation that involves a combination of atoms like a search button, a search field and a label.

Organisms: Organisms are molecules and atoms grouped together to define sections of the application. They’re more complex and have more interactions. For example, a header, a footer or a related blog post section.

Templates: Groups of Organisms form Templates. They are placeholders for organisms. For example, a blog page template, login page template or a shopping cart page template.

Pages: When you combine a template with real content, you get a page.

Credit: Pattern Lab

Why should you use Pattern Lab?

Patten Lab makes frontend developers work an absolute pleasure. This is because it allows rapid design prototyping with demonstrable interface and interactivity.

It allows developers to maintain code consistency, implement and leverage reusable components and allows multiple developers to work at the same time. All of these benefits help in easy maintenance of the code.

In terms of Drupal, frontend developers can start their work independently without the dependency on Drupal development. We can work faster and with more consistency than ever before.

Patten Lab with Drupal

Integrating Pattern Lab with Drupal has many benefits and can improve and fasten frontend development. Thanks to the Drupal community, we now have a contributed theme Emulsify Drupal that comes with inbuilt the Pattern Lab architecture. This reduces the extra development effort of achieving a Pattern Lab integration.

Creating a Heading atom in Pattern Lab

For a better understanding of implementing Pattern Lab in Drupal, let’s take an example of creating a Heading atom and integrating it in Drupal Twig template.

Heading atom directory

In the atom directory we will have 3 required files.

_heading.twig : The heading markup will go in this file
_hading.scss : This is for heading style
heading.yml : This is for static data to be passed in twig

Heading atom Twig

_heading.twig

In Heading twig, we can add the element markup with all the required attributes as variable. We can pass data from yml file or drupal field data with these variables.

Heading.yml / Heading.json

heading.json

This is an example of a json file containing static data for the variable available in the _heading.twig file.

Integrating Heading atom in Drupal template with field values

Here, we will be overriding the page template and integrating it with the heading atom.

Default bartik page-title.html.twig

Pattern Lab Heading atom integrated in page-title.html.twig

Here, in page-title.html.twig, instead of the default H1 element we are importing the heading atom as reusable element and adding Drupal field value to the defined variable in the heading atom - heading_level and heading.

Using the same pattern, we can create engaging Drupal websites using Pattern Lab.

I hope this article encourages you to start using Pattern Lab with Drupal using the Emulsify Drupal theme and play around with atoms, molecules, organisms, templates and pages to create compelling websites. If you need assistance with your Drupal development needs, our Drupal experts are just a call away. Contact us today.

Drupal Drupal Development Drupal Planet Drupal Tutorial Drupal Module Drupal 8 Drupal 9 Shefali ShettyApr 05, 2017 Subscribe For Our Newsletter And Stay Updated Subscribe

Leave us a Comment

  Shefali ShettyApr 05, 2017 Recent Posts Image Enhancing Drupal front end performance through Pattern Lab Image How to Control Access to Restricted Pages with the Rabbit Hole Module in Drupal 8 Image Celebrate with Us! Specbee Sponsors DrupalCon North America 2021 Want to extract the maximum out of Drupal? TALK TO US Featured Success Stories

A Drupal powered multi-site, multi-lingual platform to enable a unified user experience at SEMI.

link

Discover how our technology enabled UX Magazine to cater to their massive audience and launch outreach programs.

link

Discover how a Drupal powered internal portal encouraged the sellers at Flipkart to obtain the latest insights with respect to a particular domain.

link

Specbee: Enhancing Drupal front end performance through Pattern Lab

Main Drupal Feed - Tue, 04/27/2021 - 12:34
Enhancing Drupal front end performance through Pattern Lab Vinit Kumar 27 Apr, 2021 Top 10 best practices for designing a perfect UX for your mobile app

Component-driven theming is becoming widely popular today because of various reasons. The most significant being reusability and portability of components. Pattern lab is a front-end framework that uses an atomic design architecture to implement a component-based design. In this article, we will discuss more about Pattern Lab and how you can enhance your Drupal frontend performance with it.

What is Pattern Lab?

Think of Pattern Lab as an application that can help you organize your UI components in a pattern-driven approach. It is basically a static site generator that binds together all the UI components together. Pattern lab uses atomic design to accelerate the process of creating modular designs. It starts out really basic and gets more complex as you move up the ladder.

Credit: Pattern Lab

Let’s breakdown these visual building blocks:

Atoms: They are the most basic building blocks of your design. For example, UI elements like buttons, search fields, form elements, labels.

Molecules: They are groups of atoms that work together to perform a particular action. For example, a search navigation that involves a combination of atoms like a search button, a search field and a label.

Organisms: Organisms are molecules and atoms grouped together to define sections of the application. They’re more complex and have more interactions. For example, a header, a footer or a related blog post section.

Templates: Groups of Organisms form Templates. They are placeholders for organisms. For example, a blog page template, login page template or a shopping cart page template.

Pages: When you combine a template with real content, you get a page.

Credit: Pattern Lab

Why should you use Pattern Lab?

Patten Lab makes frontend developers work an absolute pleasure. This is because it allows rapid design prototyping with demonstrable interface and interactivity.

It allows developers to maintain code consistency, implement and leverage reusable components and allows multiple developers to work at the same time. All of these benefits help in easy maintenance of the code.

In terms of Drupal, frontend developers can start their work independently without the dependency on Drupal development. We can work faster and with more consistency than ever before.

Patten Lab with Drupal

Integrating Pattern Lab with Drupal has many benefits and can improve and fasten frontend development. Thanks to the Drupal community, we now have a contributed theme Emulsify Drupal that comes with inbuilt the Pattern Lab architecture. This reduces the extra development effort of achieving a Pattern Lab integration.

Creating a Heading atom in Pattern Lab

For a better understanding of implementing Pattern Lab in Drupal, let’s take an example of creating a Heading atom and integrating it in Drupal Twig template.

Heading atom directory

In the atom directory we will have 3 required files.

_heading.twig : The heading markup will go in this file
_hading.scss : This is for heading style
heading.yml : This is for static data to be passed in twig

Heading atom Twig

_heading.twig

In Heading twig, we can add the element markup with all the required attributes as variable. We can pass data from yml file or drupal field data with these variables.

Heading.yml / Heading.json

heading.json

This is an example of a json file containing static data for the variable available in the _heading.twig file.

Integrating Heading atom in Drupal template with field values

Here, we will be overriding the page template and integrating it with the heading atom.

Default bartik page-title.html.twig

Pattern Lab Heading atom integrated in page-title.html.twig

Here, in page-title.html.twig, instead of the default H1 element we are importing the heading atom as reusable element and adding Drupal field value to the defined variable in the heading atom - heading_level and heading.

Using the same pattern, we can create engaging Drupal websites using Pattern Lab.

I hope this article encourages you to start using Pattern Lab with Drupal using the Emulsify Drupal theme and play around with atoms, molecules, organisms, templates and pages to create compelling websites. If you need assistance with your Drupal development needs, our Drupal experts are just a call away. Contact us today.

Drupal Drupal Development Drupal Planet Drupal Tutorial Drupal Module Drupal 8 Drupal 9 Shefali ShettyApr 05, 2017 Subscribe For Our Newsletter And Stay Updated Subscribe

Leave us a Comment

  Shefali ShettyApr 05, 2017 Recent Posts Image Enhancing Drupal front end performance through Pattern Lab Image How to Control Access to Restricted Pages with the Rabbit Hole Module in Drupal 8 Image Celebrate with Us! Specbee Sponsors DrupalCon North America 2021 Want to extract the maximum out of Drupal? TALK TO US Featured Success Stories

A Drupal powered multi-site, multi-lingual platform to enable a unified user experience at SEMI.

link

Discover how our technology enabled UX Magazine to cater to their massive audience and launch outreach programs.

link

Discover how a Drupal powered internal portal encouraged the sellers at Flipkart to obtain the latest insights with respect to a particular domain.

link

Specbee: Enhancing Drupal front end performance through Pattern Lab

Main Drupal Feed - Tue, 04/27/2021 - 12:34
Enhancing Drupal front end performance through Pattern Lab Vinit Kumar 27 Apr, 2021 Top 10 best practices for designing a perfect UX for your mobile app

Component-driven theming is becoming widely popular today because of various reasons. The most significant being reusability and portability of components. Pattern lab is a front-end framework that uses an atomic design architecture to implement a component-based design. In this article, we will discuss more about Pattern Lab and how you can enhance your Drupal frontend performance with it.

What is Pattern Lab?

Think of Pattern Lab as an application that can help you organize your UI components in a pattern-driven approach. It is basically a static site generator that binds together all the UI components together. Pattern lab uses atomic design to accelerate the process of creating modular designs. It starts out really basic and gets more complex as you move up the ladder.

Credit: Pattern Lab

Let’s breakdown these visual building blocks:

Atoms: They are the most basic building blocks of your design. For example, UI elements like buttons, search fields, form elements, labels.

Molecules: They are groups of atoms that work together to perform a particular action. For example, a search navigation that involves a combination of atoms like a search button, a search field and a label.

Organisms: Organisms are molecules and atoms grouped together to define sections of the application. They’re more complex and have more interactions. For example, a header, a footer or a related blog post section.

Templates: Groups of Organisms form Templates. They are placeholders for organisms. For example, a blog page template, login page template or a shopping cart page template.

Pages: When you combine a template with real content, you get a page.

Credit: Pattern Lab

Why should you use Pattern Lab?

Patten Lab makes frontend developers work an absolute pleasure. This is because it allows rapid design prototyping with demonstrable interface and interactivity.

It allows developers to maintain code consistency, implement and leverage reusable components and allows multiple developers to work at the same time. All of these benefits help in easy maintenance of the code.

In terms of Drupal, frontend developers can start their work independently without the dependency on Drupal development. We can work faster and with more consistency than ever before.

Patten Lab with Drupal

Integrating Pattern Lab with Drupal has many benefits and can improve and fasten frontend development. Thanks to the Drupal community, we now have a contributed theme Emulsify Drupal that comes with inbuilt the Pattern Lab architecture. This reduces the extra development effort of achieving a Pattern Lab integration.

Creating a Heading atom in Pattern Lab

For a better understanding of implementing Pattern Lab in Drupal, let’s take an example of creating a Heading atom and integrating it in Drupal Twig template.

Heading atom directory

In the atom directory we will have 3 required files.

_heading.twig : The heading markup will go in this file
_hading.scss : This is for heading style
heading.yml : This is for static data to be passed in twig

Heading atom Twig

_heading.twig

In Heading twig, we can add the element markup with all the required attributes as variable. We can pass data from yml file or drupal field data with these variables.

Heading.yml / Heading.json

heading.json

This is an example of a json file containing static data for the variable available in the _heading.twig file.

Integrating Heading atom in Drupal template with field values

Here, we will be overriding the page template and integrating it with the heading atom.

Default bartik page-title.html.twig

Pattern Lab Heading atom integrated in page-title.html.twig

Here, in page-title.html.twig, instead of the default H1 element we are importing the heading atom as reusable element and adding Drupal field value to the defined variable in the heading atom - heading_level and heading.

Using the same pattern, we can create engaging Drupal websites using Pattern Lab.

I hope this article encourages you to start using Pattern Lab with Drupal using the Emulsify Drupal theme and play around with atoms, molecules, organisms, templates and pages to create compelling websites. If you need assistance with your Drupal development needs, our Drupal experts are just a call away. Contact us today.

Drupal Drupal Development Drupal Planet Drupal Tutorial Drupal Module Drupal 8 Drupal 9 Shefali ShettyApr 05, 2017 Subscribe For Our Newsletter And Stay Updated Subscribe

Leave us a Comment

  Shefali ShettyApr 05, 2017 Recent Posts Image Enhancing Drupal front end performance through Pattern Lab Image How to Control Access to Restricted Pages with the Rabbit Hole Module in Drupal 8 Image Celebrate with Us! Specbee Sponsors DrupalCon North America 2021 Want to extract the maximum out of Drupal? TALK TO US Featured Success Stories

A Drupal powered multi-site, multi-lingual platform to enable a unified user experience at SEMI.

link

Discover how our technology enabled UX Magazine to cater to their massive audience and launch outreach programs.

link

Discover how a Drupal powered internal portal encouraged the sellers at Flipkart to obtain the latest insights with respect to a particular domain.

link

Web Wash: Delete Files Instantly Using Fancy File Delete in Drupal

Main Drupal Feed - Tue, 04/27/2021 - 06:22

Removing files from Drupal is more tricky than you might think. There has been another tutorial about this using the module File Delete.  It requires going through a cycle of minimum 6 hours.  By default, Drupal protects files from removal which are still being used and referenced in other content. Instead of directly deleting a file, the linked usages need to be cleared first, and the files marked as temporary, then finally the system will remove them during cleanup.

This is actually a good policy. However, sometimes it’s annoying to wait for a few hours before these files are being cleaned up. In particular, if we are sure these files are unused or orphaned, there is another module called Fancy File Delete, which solves this problem.

Fancy File Delete allows you to delete files straight away without having to wait.

However, great care must be taken when using this module, because it has a ‘force delete’ option. Use of this module should be restricted to experienced administrators.

hussainweb.me: A Drupal Developer’s Tech Stack

Main Drupal Feed - Tue, 04/27/2021 - 03:41
The title of this post is not really accurate, but I can't think of another way to say it. This post is related to my earlier one on what a Drupal Developer does day-to-day. Here, I will talk about some of the skills required of a Drupal developer. I am not aiming for completeness in this post (that's a goal for another time) but I will try to list all skills required to build a regular Drupal site, deploy it, and keep it running. Some of these skills are foundational whereas others may be only needed for specific requirements. Moreover, not all skills are required at a high expertise level. For some roles, even awareness is enough.

hussainweb.me: A Drupal Developer’s Tech Stack

Main Drupal Feed - Tue, 04/27/2021 - 03:41
The title of this post is not really accurate, but I can't think of another way to say it. This post is related to my earlier one on what a Drupal Developer does day-to-day. Here, I will talk about some of the skills required of a Drupal developer. I am not aiming for completeness in this post (that's a goal for another time) but I will try to list all skills required to build a regular Drupal site, deploy it, and keep it running. Some of these skills are foundational whereas others may be only needed for specific requirements. Moreover, not all skills are required at a high expertise level. For some roles, even awareness is enough.

#! code: Drupal 9: Auto Tweeting From A Drupal Site When Content Is Published

Main Drupal Feed - Mon, 04/26/2021 - 20:04

Normally, when creating Tweets from Drupal 8 I use the Social Post Twitter module. This module is part of the Drupal Social Initiative and has been my go-to module when I've needed to read or send Tweets from a Drupal site. Since the release of Drupal 9, however, these modules have not been receiving the support needed and as of writing this article there is no easy way to install them on a Drupal 9 site. I've looked into the issue queues and can't see why the delay is there.

The Social Post Twitter module does have a lot of features that I didn't need for what I was looking for, which was to send Tweets when items of content are created. I decided to see how difficult it would be to send Tweets from a Drupal site as an item of content is published.

As it happens, creating your own Twitter integration to post status updates to Twitter isn't that difficult. The Social Post Twitter module is build around the abraham/twitteroauth package. Aside from the boilerplate code of setting up services and hooks I only needed a few lines of code to start that package and then send the needed data to Twitter. I decided it would be helpful to go through every step along the way from getting authentication details to writing code and creating a Drupal module.

Before getting into how to get the code working we need to get some authentication details.

Getting Your Access Tokens

In order to send Tweets from your Drupal site you'll need to get some OAuth details. Do find these you need to head over to https://developer.twitter.com/ and apply for developer access. This isn't that easy to figure out how to do this, so I've added some steps here to go through.

Read more.

#! code: Drupal 9: Auto Tweeting From A Drupal Site When Content Is Published

Main Drupal Feed - Mon, 04/26/2021 - 20:04

Normally, when creating Tweets from Drupal 8 I use the Social Post Twitter module. This module is part of the Drupal Social Initiative and has been my go-to module when I've needed to read or send Tweets from a Drupal site. Since the release of Drupal 9, however, these modules have not been receiving the support needed and as of writing this article there is no easy way to install them on a Drupal 9 site. I've looked into the issue queues and can't see why the delay is there.

The Social Post Twitter module does have a lot of features that I didn't need for what I was looking for, which was to send Tweets when items of content are created. I decided to see how difficult it would be to send Tweets from a Drupal site as an item of content is published.

As it happens, creating your own Twitter integration to post status updates to Twitter isn't that difficult. The Social Post Twitter module is build around the abraham/twitteroauth package. Aside from the boilerplate code of setting up services and hooks I only needed a few lines of code to start that package and then send the needed data to Twitter. I decided it would be helpful to go through every step along the way from getting authentication details to writing code and creating a Drupal module.

Before getting into how to get the code working we need to get some authentication details.

Getting Your Access Tokens

In order to send Tweets from your Drupal site you'll need to get some OAuth details. Do find these you need to head over to https://developer.twitter.com/ and apply for developer access. This isn't that easy to figure out how to do this, so I've added some steps here to go through.

Read more.

#! code: Drupal 9: Auto Tweeting From A Drupal Site When Content Is Published

Main Drupal Feed - Mon, 04/26/2021 - 20:04

Normally, when creating Tweets from Drupal 8 I use the Social Post Twitter module. This module is part of the Drupal Social Initiative and has been my go-to module when I've needed to read or send Tweets from a Drupal site. Since the release of Drupal 9, however, these modules have not been receiving the support needed and as of writing this article there is no easy way to install them on a Drupal 9 site. I've looked into the issue queues and can't see why the delay is there.

The Social Post Twitter module does have a lot of features that I didn't need for what I was looking for, which was to send Tweets when items of content are created. I decided to see how difficult it would be to send Tweets from a Drupal site as an item of content is published.

As it happens, creating your own Twitter integration to post status updates to Twitter isn't that difficult. The Social Post Twitter module is build around the abraham/twitteroauth package. Aside from the boilerplate code of setting up services and hooks I only needed a few lines of code to start that package and then send the needed data to Twitter. I decided it would be helpful to go through every step along the way from getting authentication details to writing code and creating a Drupal module.

Before getting into how to get the code working we need to get some authentication details.

Getting Your Access Tokens

In order to send Tweets from your Drupal site you'll need to get some OAuth details. Do find these you need to head over to https://developer.twitter.com/ and apply for developer access. This isn't that easy to figure out how to do this, so I've added some steps here to go through.

Read more.

php[architect]: Community Corner: Interview with Angie Byron, Part Two

Main Drupal Feed - Mon, 04/26/2021 - 17:16

Now on Drupal 9, the community isn’t slowing down. This month, we continue our interview with Angie Byron, a.k.a Webchick, a Drupal Core committer and product manager, Drupal Association Board Member, author, speaker, mentor, and Mom, and so much more. Currently, she works at Aquia for the Drupal acceleration team, where her primary role is to “Make Drupal awesome.” We talk about Drupal, coding, family, and her journey throughout the years.

Get the Full Issue

This article was published in the February 2021 issue of php[architect] magazine. Download the Free Article PDF to see how it looks in the published magazine.

If you'd like more articles like this one, become a subscriber today!. You can get each monthly issue in digital and print options or buy individual issues.

Subscribe

See Part One Here

Let’s dive into Drupal and, more specifically, Drupal 9. When you run into someone who doesn’t know what Drupal is, how do you explain it to them?

I like to say Drupal is three things; it’s a content management system doing the things a typical CMS does for you. It’s also a content management framework that is built off of a very extensible architecture. So if you are a developer and Drupal can’t do something you need it to do, you can extend it very easily through modules and plugins to make it do whatever you want it to do. Finally, it’s a community. I’ve been in the Drupal community since 2005, and we have rewritten it at least three times in that amount of time. The code is completely different from each iteration, but the overall framework is the same, and the people are just amazing. It’s a friendly, welcoming, inviting, diverse community.

My elevator pitch for why to use Drupal is: it’s good for customers who don’t know what they want. You can start it off as just a website, then add a blog. Later, when they need ecommerce, you can add it on, and then when they decide they need a forum with a rating system, there are solutions for that. To build that solution yourself, you would end up with a gargantuan codebase with things stapled together.

How well does Drupal align with the overall PHP Community?

I think, particularly with the advent of Drupal 9, we are much more aligned with the global PHP community. This is where we started adopting some of the PHP-FIG standards for things like coding standards, auto-loading, and HTTP requests. This allowed us to align a lot better with what other PHP developers were doing. We adopted Symfony as our framework of choice underneath the hood so that we could keep Drupal focused on what makes Drupal Drupal, like the Entity system.

We made a deliberate decision back around the 2012-2013 days of Drupal to focus more on embracing the larger PHP ecosystem. We knew it was time to make that change for Drupal to be able to make modifications without breaking everybody’s code all of the time, and that was a lot easier with an object-oriented paradigm.

I think prior to Drupal 8, we were pretty much off on our own little island where we would write every single thing ourselves, such as the routing system, menu handling system, filtering system, and other things. With Drupal 8, we really started to look at what was the best of breed for doing things like HTTP requests or access control and using those solutions.

As a developer, what features in Drupal 9 are exciting to you?

I am most looking forward to the automatic updates, which is a major Drupal 9 initiative. This will allow Drupal sites to stay current and patched with security updates. The other thing I am really excited about is the potential of the easy out-of-the-box initiative. Currently, that initiative is taking some features that are not quite part of the standard out of the box experience and polishing off the rough edges, and getting them in. But I think, if we really took that initiative name to its core and we really did make Drupal easy out of the box, I feel that would be transformative and amazing.

One thing I’ve seen over and over again is that developers seem to love Drupal from a technical perspective. They come in, and they get it. It’s sensible, well documented, and has a beautiful architecture. End-users, however, did not have that same experience at all. When you first install Drupal, until recently, you were presented with an empty homepage that just said, “You have no content,” and it was very hard for them to grasp the power of Drupal. Now with the out of the box profile, we have a demo set up that makes it so much easier to understand what’s going on.

Drupal 9 was the first major release that is backward compatible with its predecessor. Can you tell readers unfamiliar with it more about it and if you think it lives up to the promise of smoother upgrades?

In the past, Drupal had this philosophy of “it’s done when it’s done” and “we break your code and not your data.” What that meant is that we would rewrite all of Drupal between versions five and six and six and seven and seven and eight, and then we do our best to get your data moved over to the new version, but you’re on your own for any custom code, your themes, that kind of stuff.

That’s a lot of work, and people rightly were very annoyed about this trend, especially when seven to eight move from procedural, functional programming to object-oriented programming and Symfony. This was a big, big change, and people were like, “we’re never doing that again.” We were like, “Right, we don’t want you to do that again, either.” So from Drupal 8 forwards, we’ve changed things dramatically. We now release every six months a backward-compatible feature version, such as Drupal 8.1, 8.2, 8.3, and now 9.1, 9.2, 9.3. Every six months, you’re getting bug fixes. You’re also getting new features, but they’re backward-compatible so that they won’t break any of your existing stuff. Then in a major release, so between Drupal eight and nine, which just happened back in June of this year, the only thing we do is we drop the backward-compatibility layer, and that’s it.

We don’t make any other changes. Drupal 8.9, which was the last reason for 8 and 9.0, are exactly the same. The only difference is that 9.0 doesn’t have the backward-compatibility layers. What it means is that in the olden days, in order to move from one version of Drupal to another, you essentially kind of build out a brand new site and move everything over. Sometimes you would need to figure out what the new modules were for the new version. Now you run a tool that has a dashboard, and it scans through your code, and it lets you know “these three modules need to be updated” or “you need to make a one-line code change here.”

So previously, depending on how complicated your site was, a move in major versions of Drupal could be months to upgrade, at very least weeks, but it wasn’t exactly something you could just do over the weekend. Now, in Drupal it’s much more straightforward, and it should be something that can get accomplished over a weekend.

So the move from Drupal 8 to Drupal 9 is more of an upgrade and not this huge migration, which is really positive and is the plan moving forward.

Does this new upgrade path make it easier to contribute modules?

Yeah, because now modules can work in both versions of Drupal as long as you are using the newer APIs and not the old stuff from earlier versions of Drupal.

How does Drupal attract contributors?

This year has been a little tough because we haven’t had traditional conferences. Traditionally we get a lot of mileage out of conferences. We have big events in North America, and Europe called DrupalCon, where developers and users get together in person and talk. They are geared towards the business audience, the contributor audience, and the developer audience. It becomes a weird melting pot of all these different kinds of people.

That is where we get a lot of folks in is through the conference where we educate people who come there to learn something for their job. At the end of the conference, we have what’s called a contribution sprint day, which is kind of split into these two areas. In one room, you have a big football-field-sized ballroom with tables, and each table focuses on what they are working on, like media or testing.

In the other room, you have a bunch of people in bright t-shirts running around, and this is the new contributor room. So they set people up with development environments. As soon as you walk into the door, you are handed a USB stick that has everything you need on it, and you are ready to go. They have already prefabricated a bunch of issues that are kind of novice issues or good first-time issues. They pair people up and hand out issues to work on, and then they are around if you have questions.

So we have a track for people who’ve never contributed before, whereby at the end of the day, they might have their name on a contribution that gets pulled in. The other track is where the developers are more experienced and know exactly what they want to work on; they just need to find the right people to talk to.

It’s a lot of fun.

This year we’ve done virtual sprints, we have issues with novice tags for first-time users. We also have a mentioning channel for people who want to get involved.

Has Drupal benefited from adopting tools from the PHP community like Composer, Symfony, and Twig?

We definitely have benefited. That’s the short answer to that question? Twig is amazing in that it allows people to separate cleanly their logic from their presentation and to do it in a way that’s interoperable with other PHP projects that use Twig. And that’s a skill that you learn once and reuse it a bunch of different times. Adopting a lot of the symphony underlying HTTP framework has been nice because then it’s kind of like outsourcing that bit of the code where we trust that stuff’s working properly and allows us to stay focused on the things that Drupal can do.

Overall just for the health of the PHP ecosystem, I think it’s really good for projects to adopt similar standards and be interoperable with each other because that makes for a bigger community that’s able to move around and do more stuff.

We had hoped that move would have triggered a new round of adoption among PHP developers who did not previously use Drupal. If that has happened, it definitely hasn’t happened on mass. We had done five years’ worth of refactoring to get Drupal onto the new thing. It might be an “it takes time” situation, or maybe people are just happy with whatever technologies they are using. But I do run into those people who say, “I was a symphony developer at my work when they told me now we are using Drupal, and it has been fricking fantastic because now I can combine the two in one,” that feels really good.

What does Drupal have to do to compete and thrive in the open-source CMS market?

Like we discussed, I feel making the end-user experience as solid as the developer experience is key. Kathy Sierra wrote about the “I suck threshold”, and it’s when you use new technology, and at first you’re blundering around. You don’t know what’s, what, and then at some point, you reach the “Oh, I get it” phase, and then you’re awesome with it. Drupal’s length of time to get past the “I suck” threshold is long, and you really have to commit yourself to it. I feel like that’s asking a lot of people, so I’d like to continue efforts like the starter distro and things like that.

I’d like to continue efforts to reduce that amount of time spent thrashing around in “I suck” and more into the “Oh, I get it” and “this is awesome, and I’m gonna use it” phase. That’s kind of going to be my focus for the next while.

What has been your biggest achievement, and what do you feel Drupal’s biggest achievement has been as a platform?

For Drupal, that is tough because there are so many different stories. One I am particularly proud of, and unfortunately, it doesn’t exist any longer, but during the Obama years of the US government, Drupal was running whitehouse.gov. That was a big deal—not only for us but just for open-source in general. That high profile of a target for nasty people who want to do nasty things was running on open-source was huge.

And that was a huge enabler, not just for Drupal, but I feel like all surrounding open-source technologies. One of the things that the Obama administration built with Drupal during that era was something called “We, the people,” and it was a petition website, kind of on the order of change.org. If you got a petition with more than a certain amount of signatures, then that bill would actually go to the floor of the House, and they’d have to discuss it. It was a way of people powering the government to actually care about issues. That made some real actual changes. Making the government more accountable to people and giving people a voice in the government and what types of things that governments should care about. I feel like that was a really neat example of the kinds of things that Drupal can do.

My biggest achievement is being a mom, as cliche as that may sound, but I have a little seven-year-old kid, and she’s amazing and awesome and hilarious. She fills my life with joy every day, so that’s definitely the best thing I ever did.

It’s always such a great reminder that we have these platforms available to us, mostly because of open-source, that are genuinely transformational. Even if we don’t program as professionals but code out of passion, the tools, language, and frameworks are used by fortune 500 companies and governments worldwide. We can all add our little pice to make them better, more robust, and more secure.

That wraps up this interview with Angie Byron, a truly impactful and inspirational person to talk to. If you ever have the opportunity to see Angie speak or, better yet, to talk to Angie, don’t pass it up! If for no other reason but to tell her thanks for everything she has done for Drupal and OpenSource and everything the Drupal community has brought to PHP.

Biography

Eric Van Johnson is the CTO of DiegoDev Group, LLC. A group of passionate and talented frontend, backend, and mobile developers that strive to provide outstanding services. He is also one of the organizers of San Diego PHP (SDPHP), his local user group, and a podcaster. In the early ’80s while Eric’s friends were getting Atari 2600 or Intellivision gaming consoles, his Dad bought him a TRS-80 Coco with BASIC. Eric started teaching himself coding and never looked back. A husband, father, and enjoyer of scotch and baseball. He had to give up playing baseball because he kept spilling his scotch while trying to run the bases. @shocm

The post Community Corner: Interview with Angie Byron, Part Two appeared first on php[architect].

php[architect]: Community Corner: Interview with Angie Byron, Part Two

Main Drupal Feed - Mon, 04/26/2021 - 17:16

Now on Drupal 9, the community isn’t slowing down. This month, we continue our interview with Angie Byron, a.k.a Webchick, a Drupal Core committer and product manager, Drupal Association Board Member, author, speaker, mentor, and Mom, and so much more. Currently, she works at Aquia for the Drupal acceleration team, where her primary role is to “Make Drupal awesome.” We talk about Drupal, coding, family, and her journey throughout the years.

Get the Full Issue

This article was published in the February 2021 issue of php[architect] magazine. Download the Free Article PDF to see how it looks in the published magazine.

If you'd like more articles like this one, become a subscriber today!. You can get each monthly issue in digital and print options or buy individual issues.

Subscribe

See Part One Here

Let’s dive into Drupal and, more specifically, Drupal 9. When you run into someone who doesn’t know what Drupal is, how do you explain it to them?

I like to say Drupal is three things; it’s a content management system doing the things a typical CMS does for you. It’s also a content management framework that is built off of a very extensible architecture. So if you are a developer and Drupal can’t do something you need it to do, you can extend it very easily through modules and plugins to make it do whatever you want it to do. Finally, it’s a community. I’ve been in the Drupal community since 2005, and we have rewritten it at least three times in that amount of time. The code is completely different from each iteration, but the overall framework is the same, and the people are just amazing. It’s a friendly, welcoming, inviting, diverse community.

My elevator pitch for why to use Drupal is: it’s good for customers who don’t know what they want. You can start it off as just a website, then add a blog. Later, when they need ecommerce, you can add it on, and then when they decide they need a forum with a rating system, there are solutions for that. To build that solution yourself, you would end up with a gargantuan codebase with things stapled together.

How well does Drupal align with the overall PHP Community?

I think, particularly with the advent of Drupal 9, we are much more aligned with the global PHP community. This is where we started adopting some of the PHP-FIG standards for things like coding standards, auto-loading, and HTTP requests. This allowed us to align a lot better with what other PHP developers were doing. We adopted Symfony as our framework of choice underneath the hood so that we could keep Drupal focused on what makes Drupal Drupal, like the Entity system.

We made a deliberate decision back around the 2012-2013 days of Drupal to focus more on embracing the larger PHP ecosystem. We knew it was time to make that change for Drupal to be able to make modifications without breaking everybody’s code all of the time, and that was a lot easier with an object-oriented paradigm.

I think prior to Drupal 8, we were pretty much off on our own little island where we would write every single thing ourselves, such as the routing system, menu handling system, filtering system, and other things. With Drupal 8, we really started to look at what was the best of breed for doing things like HTTP requests or access control and using those solutions.

As a developer, what features in Drupal 9 are exciting to you?

I am most looking forward to the automatic updates, which is a major Drupal 9 initiative. This will allow Drupal sites to stay current and patched with security updates. The other thing I am really excited about is the potential of the easy out-of-the-box initiative. Currently, that initiative is taking some features that are not quite part of the standard out of the box experience and polishing off the rough edges, and getting them in. But I think, if we really took that initiative name to its core and we really did make Drupal easy out of the box, I feel that would be transformative and amazing.

One thing I’ve seen over and over again is that developers seem to love Drupal from a technical perspective. They come in, and they get it. It’s sensible, well documented, and has a beautiful architecture. End-users, however, did not have that same experience at all. When you first install Drupal, until recently, you were presented with an empty homepage that just said, “You have no content,” and it was very hard for them to grasp the power of Drupal. Now with the out of the box profile, we have a demo set up that makes it so much easier to understand what’s going on.

Drupal 9 was the first major release that is backward compatible with its predecessor. Can you tell readers unfamiliar with it more about it and if you think it lives up to the promise of smoother upgrades?

In the past, Drupal had this philosophy of “it’s done when it’s done” and “we break your code and not your data.” What that meant is that we would rewrite all of Drupal between versions five and six and six and seven and seven and eight, and then we do our best to get your data moved over to the new version, but you’re on your own for any custom code, your themes, that kind of stuff.

That’s a lot of work, and people rightly were very annoyed about this trend, especially when seven to eight move from procedural, functional programming to object-oriented programming and Symfony. This was a big, big change, and people were like, “we’re never doing that again.” We were like, “Right, we don’t want you to do that again, either.” So from Drupal 8 forwards, we’ve changed things dramatically. We now release every six months a backward-compatible feature version, such as Drupal 8.1, 8.2, 8.3, and now 9.1, 9.2, 9.3. Every six months, you’re getting bug fixes. You’re also getting new features, but they’re backward-compatible so that they won’t break any of your existing stuff. Then in a major release, so between Drupal eight and nine, which just happened back in June of this year, the only thing we do is we drop the backward-compatibility layer, and that’s it.

We don’t make any other changes. Drupal 8.9, which was the last reason for 8 and 9.0, are exactly the same. The only difference is that 9.0 doesn’t have the backward-compatibility layers. What it means is that in the olden days, in order to move from one version of Drupal to another, you essentially kind of build out a brand new site and move everything over. Sometimes you would need to figure out what the new modules were for the new version. Now you run a tool that has a dashboard, and it scans through your code, and it lets you know “these three modules need to be updated” or “you need to make a one-line code change here.”

So previously, depending on how complicated your site was, a move in major versions of Drupal could be months to upgrade, at very least weeks, but it wasn’t exactly something you could just do over the weekend. Now, in Drupal it’s much more straightforward, and it should be something that can get accomplished over a weekend.

So the move from Drupal 8 to Drupal 9 is more of an upgrade and not this huge migration, which is really positive and is the plan moving forward.

Does this new upgrade path make it easier to contribute modules?

Yeah, because now modules can work in both versions of Drupal as long as you are using the newer APIs and not the old stuff from earlier versions of Drupal.

How does Drupal attract contributors?

This year has been a little tough because we haven’t had traditional conferences. Traditionally we get a lot of mileage out of conferences. We have big events in North America, and Europe called DrupalCon, where developers and users get together in person and talk. They are geared towards the business audience, the contributor audience, and the developer audience. It becomes a weird melting pot of all these different kinds of people.

That is where we get a lot of folks in is through the conference where we educate people who come there to learn something for their job. At the end of the conference, we have what’s called a contribution sprint day, which is kind of split into these two areas. In one room, you have a big football-field-sized ballroom with tables, and each table focuses on what they are working on, like media or testing.

In the other room, you have a bunch of people in bright t-shirts running around, and this is the new contributor room. So they set people up with development environments. As soon as you walk into the door, you are handed a USB stick that has everything you need on it, and you are ready to go. They have already prefabricated a bunch of issues that are kind of novice issues or good first-time issues. They pair people up and hand out issues to work on, and then they are around if you have questions.

So we have a track for people who’ve never contributed before, whereby at the end of the day, they might have their name on a contribution that gets pulled in. The other track is where the developers are more experienced and know exactly what they want to work on; they just need to find the right people to talk to.

It’s a lot of fun.

This year we’ve done virtual sprints, we have issues with novice tags for first-time users. We also have a mentioning channel for people who want to get involved.

Has Drupal benefited from adopting tools from the PHP community like Composer, Symfony, and Twig?

We definitely have benefited. That’s the short answer to that question? Twig is amazing in that it allows people to separate cleanly their logic from their presentation and to do it in a way that’s interoperable with other PHP projects that use Twig. And that’s a skill that you learn once and reuse it a bunch of different times. Adopting a lot of the symphony underlying HTTP framework has been nice because then it’s kind of like outsourcing that bit of the code where we trust that stuff’s working properly and allows us to stay focused on the things that Drupal can do.

Overall just for the health of the PHP ecosystem, I think it’s really good for projects to adopt similar standards and be interoperable with each other because that makes for a bigger community that’s able to move around and do more stuff.

We had hoped that move would have triggered a new round of adoption among PHP developers who did not previously use Drupal. If that has happened, it definitely hasn’t happened on mass. We had done five years’ worth of refactoring to get Drupal onto the new thing. It might be an “it takes time” situation, or maybe people are just happy with whatever technologies they are using. But I do run into those people who say, “I was a symphony developer at my work when they told me now we are using Drupal, and it has been fricking fantastic because now I can combine the two in one,” that feels really good.

What does Drupal have to do to compete and thrive in the open-source CMS market?

Like we discussed, I feel making the end-user experience as solid as the developer experience is key. Kathy Sierra wrote about the “I suck threshold”, and it’s when you use new technology, and at first you’re blundering around. You don’t know what’s, what, and then at some point, you reach the “Oh, I get it” phase, and then you’re awesome with it. Drupal’s length of time to get past the “I suck” threshold is long, and you really have to commit yourself to it. I feel like that’s asking a lot of people, so I’d like to continue efforts like the starter distro and things like that.

I’d like to continue efforts to reduce that amount of time spent thrashing around in “I suck” and more into the “Oh, I get it” and “this is awesome, and I’m gonna use it” phase. That’s kind of going to be my focus for the next while.

What has been your biggest achievement, and what do you feel Drupal’s biggest achievement has been as a platform?

For Drupal, that is tough because there are so many different stories. One I am particularly proud of, and unfortunately, it doesn’t exist any longer, but during the Obama years of the US government, Drupal was running whitehouse.gov. That was a big deal—not only for us but just for open-source in general. That high profile of a target for nasty people who want to do nasty things was running on open-source was huge.

And that was a huge enabler, not just for Drupal, but I feel like all surrounding open-source technologies. One of the things that the Obama administration built with Drupal during that era was something called “We, the people,” and it was a petition website, kind of on the order of change.org. If you got a petition with more than a certain amount of signatures, then that bill would actually go to the floor of the House, and they’d have to discuss it. It was a way of people powering the government to actually care about issues. That made some real actual changes. Making the government more accountable to people and giving people a voice in the government and what types of things that governments should care about. I feel like that was a really neat example of the kinds of things that Drupal can do.

My biggest achievement is being a mom, as cliche as that may sound, but I have a little seven-year-old kid, and she’s amazing and awesome and hilarious. She fills my life with joy every day, so that’s definitely the best thing I ever did.

It’s always such a great reminder that we have these platforms available to us, mostly because of open-source, that are genuinely transformational. Even if we don’t program as professionals but code out of passion, the tools, language, and frameworks are used by fortune 500 companies and governments worldwide. We can all add our little pice to make them better, more robust, and more secure.

That wraps up this interview with Angie Byron, a truly impactful and inspirational person to talk to. If you ever have the opportunity to see Angie speak or, better yet, to talk to Angie, don’t pass it up! If for no other reason but to tell her thanks for everything she has done for Drupal and OpenSource and everything the Drupal community has brought to PHP.

Biography

Eric Van Johnson is the CTO of DiegoDev Group, LLC. A group of passionate and talented frontend, backend, and mobile developers that strive to provide outstanding services. He is also one of the organizers of San Diego PHP (SDPHP), his local user group, and a podcaster. In the early ’80s while Eric’s friends were getting Atari 2600 or Intellivision gaming consoles, his Dad bought him a TRS-80 Coco with BASIC. Eric started teaching himself coding and never looked back. A husband, father, and enjoyer of scotch and baseball. He had to give up playing baseball because he kept spilling his scotch while trying to run the bases. @shocm

The post Community Corner: Interview with Angie Byron, Part Two appeared first on php[architect].

php[architect]: Community Corner: Interview with Angie Byron, Part Two

Main Drupal Feed - Mon, 04/26/2021 - 17:16

Now on Drupal 9, the community isn’t slowing down. This month, we continue our interview with Angie Byron, a.k.a Webchick, a Drupal Core committer and product manager, Drupal Association Board Member, author, speaker, mentor, and Mom, and so much more. Currently, she works at Aquia for the Drupal acceleration team, where her primary role is to “Make Drupal awesome.” We talk about Drupal, coding, family, and her journey throughout the years.

Get the Full Issue

This article was published in the February 2021 issue of php[architect] magazine. Download the Free Article PDF to see how it looks in the published magazine.

If you'd like more articles like this one, become a subscriber today!. You can get each monthly issue in digital and print options or buy individual issues.

Subscribe

See Part One Here

Let’s dive into Drupal and, more specifically, Drupal 9. When you run into someone who doesn’t know what Drupal is, how do you explain it to them?

I like to say Drupal is three things; it’s a content management system doing the things a typical CMS does for you. It’s also a content management framework that is built off of a very extensible architecture. So if you are a developer and Drupal can’t do something you need it to do, you can extend it very easily through modules and plugins to make it do whatever you want it to do. Finally, it’s a community. I’ve been in the Drupal community since 2005, and we have rewritten it at least three times in that amount of time. The code is completely different from each iteration, but the overall framework is the same, and the people are just amazing. It’s a friendly, welcoming, inviting, diverse community.

My elevator pitch for why to use Drupal is: it’s good for customers who don’t know what they want. You can start it off as just a website, then add a blog. Later, when they need ecommerce, you can add it on, and then when they decide they need a forum with a rating system, there are solutions for that. To build that solution yourself, you would end up with a gargantuan codebase with things stapled together.

How well does Drupal align with the overall PHP Community?

I think, particularly with the advent of Drupal 9, we are much more aligned with the global PHP community. This is where we started adopting some of the PHP-FIG standards for things like coding standards, auto-loading, and HTTP requests. This allowed us to align a lot better with what other PHP developers were doing. We adopted Symfony as our framework of choice underneath the hood so that we could keep Drupal focused on what makes Drupal Drupal, like the Entity system.

We made a deliberate decision back around the 2012-2013 days of Drupal to focus more on embracing the larger PHP ecosystem. We knew it was time to make that change for Drupal to be able to make modifications without breaking everybody’s code all of the time, and that was a lot easier with an object-oriented paradigm.

I think prior to Drupal 8, we were pretty much off on our own little island where we would write every single thing ourselves, such as the routing system, menu handling system, filtering system, and other things. With Drupal 8, we really started to look at what was the best of breed for doing things like HTTP requests or access control and using those solutions.

As a developer, what features in Drupal 9 are exciting to you?

I am most looking forward to the automatic updates, which is a major Drupal 9 initiative. This will allow Drupal sites to stay current and patched with security updates. The other thing I am really excited about is the potential of the easy out-of-the-box initiative. Currently, that initiative is taking some features that are not quite part of the standard out of the box experience and polishing off the rough edges, and getting them in. But I think, if we really took that initiative name to its core and we really did make Drupal easy out of the box, I feel that would be transformative and amazing.

One thing I’ve seen over and over again is that developers seem to love Drupal from a technical perspective. They come in, and they get it. It’s sensible, well documented, and has a beautiful architecture. End-users, however, did not have that same experience at all. When you first install Drupal, until recently, you were presented with an empty homepage that just said, “You have no content,” and it was very hard for them to grasp the power of Drupal. Now with the out of the box profile, we have a demo set up that makes it so much easier to understand what’s going on.

Drupal 9 was the first major release that is backward compatible with its predecessor. Can you tell readers unfamiliar with it more about it and if you think it lives up to the promise of smoother upgrades?

In the past, Drupal had this philosophy of “it’s done when it’s done” and “we break your code and not your data.” What that meant is that we would rewrite all of Drupal between versions five and six and six and seven and seven and eight, and then we do our best to get your data moved over to the new version, but you’re on your own for any custom code, your themes, that kind of stuff.

That’s a lot of work, and people rightly were very annoyed about this trend, especially when seven to eight move from procedural, functional programming to object-oriented programming and Symfony. This was a big, big change, and people were like, “we’re never doing that again.” We were like, “Right, we don’t want you to do that again, either.” So from Drupal 8 forwards, we’ve changed things dramatically. We now release every six months a backward-compatible feature version, such as Drupal 8.1, 8.2, 8.3, and now 9.1, 9.2, 9.3. Every six months, you’re getting bug fixes. You’re also getting new features, but they’re backward-compatible so that they won’t break any of your existing stuff. Then in a major release, so between Drupal eight and nine, which just happened back in June of this year, the only thing we do is we drop the backward-compatibility layer, and that’s it.

We don’t make any other changes. Drupal 8.9, which was the last reason for 8 and 9.0, are exactly the same. The only difference is that 9.0 doesn’t have the backward-compatibility layers. What it means is that in the olden days, in order to move from one version of Drupal to another, you essentially kind of build out a brand new site and move everything over. Sometimes you would need to figure out what the new modules were for the new version. Now you run a tool that has a dashboard, and it scans through your code, and it lets you know “these three modules need to be updated” or “you need to make a one-line code change here.”

So previously, depending on how complicated your site was, a move in major versions of Drupal could be months to upgrade, at very least weeks, but it wasn’t exactly something you could just do over the weekend. Now, in Drupal it’s much more straightforward, and it should be something that can get accomplished over a weekend.

So the move from Drupal 8 to Drupal 9 is more of an upgrade and not this huge migration, which is really positive and is the plan moving forward.

Does this new upgrade path make it easier to contribute modules?

Yeah, because now modules can work in both versions of Drupal as long as you are using the newer APIs and not the old stuff from earlier versions of Drupal.

How does Drupal attract contributors?

This year has been a little tough because we haven’t had traditional conferences. Traditionally we get a lot of mileage out of conferences. We have big events in North America, and Europe called DrupalCon, where developers and users get together in person and talk. They are geared towards the business audience, the contributor audience, and the developer audience. It becomes a weird melting pot of all these different kinds of people.

That is where we get a lot of folks in is through the conference where we educate people who come there to learn something for their job. At the end of the conference, we have what’s called a contribution sprint day, which is kind of split into these two areas. In one room, you have a big football-field-sized ballroom with tables, and each table focuses on what they are working on, like media or testing.

In the other room, you have a bunch of people in bright t-shirts running around, and this is the new contributor room. So they set people up with development environments. As soon as you walk into the door, you are handed a USB stick that has everything you need on it, and you are ready to go. They have already prefabricated a bunch of issues that are kind of novice issues or good first-time issues. They pair people up and hand out issues to work on, and then they are around if you have questions.

So we have a track for people who’ve never contributed before, whereby at the end of the day, they might have their name on a contribution that gets pulled in. The other track is where the developers are more experienced and know exactly what they want to work on; they just need to find the right people to talk to.

It’s a lot of fun.

This year we’ve done virtual sprints, we have issues with novice tags for first-time users. We also have a mentioning channel for people who want to get involved.

Has Drupal benefited from adopting tools from the PHP community like Composer, Symfony, and Twig?

We definitely have benefited. That’s the short answer to that question? Twig is amazing in that it allows people to separate cleanly their logic from their presentation and to do it in a way that’s interoperable with other PHP projects that use Twig. And that’s a skill that you learn once and reuse it a bunch of different times. Adopting a lot of the symphony underlying HTTP framework has been nice because then it’s kind of like outsourcing that bit of the code where we trust that stuff’s working properly and allows us to stay focused on the things that Drupal can do.

Overall just for the health of the PHP ecosystem, I think it’s really good for projects to adopt similar standards and be interoperable with each other because that makes for a bigger community that’s able to move around and do more stuff.

We had hoped that move would have triggered a new round of adoption among PHP developers who did not previously use Drupal. If that has happened, it definitely hasn’t happened on mass. We had done five years’ worth of refactoring to get Drupal onto the new thing. It might be an “it takes time” situation, or maybe people are just happy with whatever technologies they are using. But I do run into those people who say, “I was a symphony developer at my work when they told me now we are using Drupal, and it has been fricking fantastic because now I can combine the two in one,” that feels really good.

What does Drupal have to do to compete and thrive in the open-source CMS market?

Like we discussed, I feel making the end-user experience as solid as the developer experience is key. Kathy Sierra wrote about the “I suck threshold”, and it’s when you use new technology, and at first you’re blundering around. You don’t know what’s, what, and then at some point, you reach the “Oh, I get it” phase, and then you’re awesome with it. Drupal’s length of time to get past the “I suck” threshold is long, and you really have to commit yourself to it. I feel like that’s asking a lot of people, so I’d like to continue efforts like the starter distro and things like that.

I’d like to continue efforts to reduce that amount of time spent thrashing around in “I suck” and more into the “Oh, I get it” and “this is awesome, and I’m gonna use it” phase. That’s kind of going to be my focus for the next while.

What has been your biggest achievement, and what do you feel Drupal’s biggest achievement has been as a platform?

For Drupal, that is tough because there are so many different stories. One I am particularly proud of, and unfortunately, it doesn’t exist any longer, but during the Obama years of the US government, Drupal was running whitehouse.gov. That was a big deal—not only for us but just for open-source in general. That high profile of a target for nasty people who want to do nasty things was running on open-source was huge.

And that was a huge enabler, not just for Drupal, but I feel like all surrounding open-source technologies. One of the things that the Obama administration built with Drupal during that era was something called “We, the people,” and it was a petition website, kind of on the order of change.org. If you got a petition with more than a certain amount of signatures, then that bill would actually go to the floor of the House, and they’d have to discuss it. It was a way of people powering the government to actually care about issues. That made some real actual changes. Making the government more accountable to people and giving people a voice in the government and what types of things that governments should care about. I feel like that was a really neat example of the kinds of things that Drupal can do.

My biggest achievement is being a mom, as cliche as that may sound, but I have a little seven-year-old kid, and she’s amazing and awesome and hilarious. She fills my life with joy every day, so that’s definitely the best thing I ever did.

It’s always such a great reminder that we have these platforms available to us, mostly because of open-source, that are genuinely transformational. Even if we don’t program as professionals but code out of passion, the tools, language, and frameworks are used by fortune 500 companies and governments worldwide. We can all add our little pice to make them better, more robust, and more secure.

That wraps up this interview with Angie Byron, a truly impactful and inspirational person to talk to. If you ever have the opportunity to see Angie speak or, better yet, to talk to Angie, don’t pass it up! If for no other reason but to tell her thanks for everything she has done for Drupal and OpenSource and everything the Drupal community has brought to PHP.

Biography

Eric Van Johnson is the CTO of DiegoDev Group, LLC. A group of passionate and talented frontend, backend, and mobile developers that strive to provide outstanding services. He is also one of the organizers of San Diego PHP (SDPHP), his local user group, and a podcaster. In the early ’80s while Eric’s friends were getting Atari 2600 or Intellivision gaming consoles, his Dad bought him a TRS-80 Coco with BASIC. Eric started teaching himself coding and never looked back. A husband, father, and enjoyer of scotch and baseball. He had to give up playing baseball because he kept spilling his scotch while trying to run the bases. @shocm

The post Community Corner: Interview with Angie Byron, Part Two appeared first on php[architect].

Bell Towers Theme

Drupal Themes - Mon, 04/26/2021 - 16:02
Template responsive bootstrap 3 based

The customization options are rather expansive, with options for Google Fonts, logo uploads, and more. The full-screen slider works nicely for those who want to show off large images or promotional banners, while the full color control offers the ultimate branding environment.

  • bootstrap v3.3.7
  • jquery 3.5.1 noConflict()
  • googlefont font icon
  • html5shiv for crossbrowser
NO jquery_update module needed

NO CDN dependence for js or css files

DEMO

http://drupalforum.byethost10.com/drupal-free-template/belltowers/index.html

Valid for frontpage not recommended for admin pages

Avaliable section in front page by default, Services, Portfolio, About, Team, Contact, Footer

Fully customizable. Enjoy!

Jacob Rockowitz: To Drupal or not to Drupal… Putting my foot down in the Webform module's issue queue

Main Drupal Feed - Mon, 04/26/2021 - 14:19

I hate the title of this blog post because "putting my foot down" means that I am frustrated and need to make a statement about sustainability in the Webform module's issue queue. The clown feet represent the two emotions that I feel with regard to maintaining the Webform module. I love helping individuals and organizations in the Drupal community, this interaction makes me happy, but I am frustrated that my work is no longer sustainable, and that makes me sad.

The Webform module and Drupal are free to use, but the time and effort we collectively spend triaging issues, answering support requests, fixing bugs, and adding new features, is not free. Everyone needs to contribute something back to the Drupal community if we want our collaboration to succeed. This is especially so if someone wants help and assistance in the Webform module's issue queue. It is time to clearly state this requirement in the Webform module's issue queue to sustain our collaboration.

I recently updated the Webform module's project page to include several ways to get involved, fund development, join the Drupal Association, or hire me for professional support. I can no longer accept that someone can't do one of the above. If someone has limited financial means, they can request a free membership to the Drupal Association. Better yet, that can earn a committed credit by helping with documentation or by reviewing a patch.

Addressing the free-rider problem in Webform module's issue queue

Many blog posts, including a few of my own, discuss the sustainability challenges around open source projects. Right now, I need to solve the free-rider problem in the Webform issue queue.

Free-riders in the Webform issue queue limit my ability to support individuals and organizations who are actively contributing to Drupal and the Webform module. To continue to sustain my work in the...Read More

Jacob Rockowitz: To Drupal or not to Drupal… Putting my foot down in the Webform module's issue queue

Main Drupal Feed - Mon, 04/26/2021 - 14:19

I hate the title of this blog post because "putting my foot down" means that I am frustrated and need to make a statement about sustainability in the Webform module's issue queue. The clown feet represent the two emotions that I feel with regard to maintaining the Webform module. I love helping individuals and organizations in the Drupal community, this interaction makes me happy, but I am frustrated that my work is no longer sustainable, and that makes me sad.

The Webform module and Drupal are free to use, but the time and effort we collectively spend triaging issues, answering support requests, fixing bugs, and adding new features, is not free. Everyone needs to contribute something back to the Drupal community if we want our collaboration to succeed. This is especially so if someone wants help and assistance in the Webform module's issue queue. It is time to clearly state this requirement in the Webform module's issue queue to sustain our collaboration.

I recently updated the Webform module's project page to include several ways to get involved, fund development, join the Drupal Association, or hire me for professional support. I can no longer accept that someone can't do one of the above. If someone has limited financial means, they can request a free membership to the Drupal Association. Better yet, that can earn a committed credit by helping with documentation or by reviewing a patch.

Addressing the free-rider problem in Webform module's issue queue

Many blog posts, including a few of my own, discuss the sustainability challenges around open source projects. Right now, I need to solve the free-rider problem in the Webform issue queue.

Free-riders in the Webform issue queue limit my ability to support individuals and organizations who are actively contributing to Drupal and the Webform module. To continue to sustain my work in the...Read More

Jacob Rockowitz: To Drupal or not to Drupal… Putting my foot down in the Webform module's issue queue

Main Drupal Feed - Mon, 04/26/2021 - 14:19

I hate the title of this blog post because "putting my foot down" means that I am frustrated and need to make a statement about sustainability in the Webform module's issue queue. The clown feet represent the two emotions that I feel with regard to maintaining the Webform module. I love helping individuals and organizations in the Drupal community, this interaction makes me happy, but I am frustrated that my work is no longer sustainable, and that makes me sad.

The Webform module and Drupal are free to use, but the time and effort we collectively spend triaging issues, answering support requests, fixing bugs, and adding new features, is not free. Everyone needs to contribute something back to the Drupal community if we want our collaboration to succeed. This is especially so if someone wants help and assistance in the Webform module's issue queue. It is time to clearly state this requirement in the Webform module's issue queue to sustain our collaboration.

I recently updated the Webform module's project page to include several ways to get involved, fund development, join the Drupal Association, or hire me for professional support. I can no longer accept that someone can't do one of the above. If someone has limited financial means, they can request a free membership to the Drupal Association. Better yet, that can earn a committed credit by helping with documentation or by reviewing a patch.

Addressing the free-rider problem in Webform module's issue queue

Many blog posts, including a few of my own, discuss the sustainability challenges around open source projects. Right now, I need to solve the free-rider problem in the Webform issue queue.

Free-riders in the Webform issue queue limit my ability to support individuals and organizations who are actively contributing to Drupal and the Webform module. To continue to sustain my work in the...Read More

Tag1 Consulting: Automating Infrastructure with EKS and Pulumi: Deploying New Enterprise Web Applications in Minutes - Part 2

Main Drupal Feed - Mon, 04/26/2021 - 12:35

Automated deployment of software - whether it’s new packages, patches, or configuration changes - is a fact of life in modern software development and management. Automated infrastructure, however, is a newer set of tools and processes. With Amazon EKS and Pulumi, Tag1 is tackling these challenges to meet the needs of Fortune 500 customers. In this second part of our series on automating infrastructure, Managing Director Michael Meyers is joined by CIO Jeff Sheltren and Senior Infrastructure Engineer Travis Whitehead. They discuss how Tag1 is using these tools to create and deploy entire websites, ready for use, in just a few minutes. From a standardized distribution, to Docker, to Pulumi, and finally to deployment, you’ll hear about the ins and outs of the workflows Tag1 is creating to be faster and more successful. - Part 1 ### Additional resources - EKS - Pulumi - Docker For a transcript of this video, see Transcript: Deploying New Enterprise Web Applications in Minutes- Part 2. --- Photo by Amir Hanna on Unsplash

Read more lynette@tag1co… Mon, 04/26/2021 - 05:35

Tag1 Consulting: Automating Infrastructure with EKS and Pulumi: Deploying New Enterprise Web Applications in Minutes - Part 2

Main Drupal Feed - Mon, 04/26/2021 - 12:35

Automated deployment of software - whether it’s new packages, patches, or configuration changes - is a fact of life in modern software development and management. Automated infrastructure, however, is a newer set of tools and processes. With Amazon EKS and Pulumi, Tag1 is tackling these challenges to meet the needs of Fortune 500 customers. In this second part of our series on automating infrastructure, Managing Director Michael Meyers is joined by CIO Jeff Sheltren and Senior Infrastructure Engineer Travis Whitehead. They discuss how Tag1 is using these tools to create and deploy entire websites, ready for use, in just a few minutes. From a standardized distribution, to Docker, to Pulumi, and finally to deployment, you’ll hear about the ins and outs of the workflows Tag1 is creating to be faster and more successful. - Part 1 ### Additional resources - EKS - Pulumi - Docker For a transcript of this video, see Transcript: Deploying New Enterprise Web Applications in Minutes- Part 2. --- Photo by Amir Hanna on Unsplash

Read more lynette@tag1co… Mon, 04/26/2021 - 05:35

Tag1 Consulting: Automating Infrastructure with EKS and Pulumi: Deploying New Enterprise Web Applications in Minutes - Part 2

Main Drupal Feed - Mon, 04/26/2021 - 12:35

Automated deployment of software - whether it’s new packages, patches, or configuration changes - is a fact of life in modern software development and management. Automated infrastructure, however, is a newer set of tools and processes. With Amazon EKS and Pulumi, Tag1 is tackling these challenges to meet the needs of Fortune 500 customers. In this second part of our series on automating infrastructure, Managing Director Michael Meyers is joined by CIO Jeff Sheltren and Senior Infrastructure Engineer Travis Whitehead. They discuss how Tag1 is using these tools to create and deploy entire websites, ready for use, in just a few minutes. From a standardized distribution, to Docker, to Pulumi, and finally to deployment, you’ll hear about the ins and outs of the workflows Tag1 is creating to be faster and more successful. - Part 1 ### Additional resources - EKS - Pulumi - Docker For a transcript of this video, see Transcript: Deploying New Enterprise Web Applications in Minutes- Part 2. --- Photo by Amir Hanna on Unsplash

Read more lynette@tag1co… Mon, 04/26/2021 - 05:35

Pages