Development News

Amazee Labs: Multilingual Drupal - Part 2: Translation Management

Main Drupal Feed - Tue, 06/23/2020 - 08:45
<img src="https://www.amazeelabs.com/sites/default/files/styles/leading_image/public/images/current-affairs/AL%20Translation%20Management%20Blog.png?h=bf5f3dd0&amp;itok=UoMiMPPp" width="1120" height="630" alt="Multilingual Drupal - Part 2: Translation Management" title="Multilingual Drupal - Part 2: Translation Management" class="image-style-leading-image" /> With a simplified translation flow with a balanced use of both human and machine translation, you can reduce your costs and reach even more markets.

WPTavern: Packagist, GitLab, and GitHubUpdater Plugin Work to Improve Support for Alternative Default Branch Names

Wordpress Planet - Mon, 06/22/2020 - 23:19

In response to recent events, where American police officers have been charged with murder for the deaths of George Floyd and Rayshard Brooks, along with the protests led by the Black Lives Matter movement, many repository owners are rejecting the use of the term ‘master’ for the default branch as oppressive terminology. As Git-based repository hosting platforms are moving to make it easier for users to select alternative default branch names, Packagist is working to better support Composer package owners during this transition.

Packagist.org co-founder Jordi Boggiano explained how Composer 1.x has decent support for other default branch names. It allows users to define a branch-alias to rename the default branch to anything, while ensuring that everything still works. Composer 2.x doesn’t assign specialized meaning to master/trunk/default branch names but rather normalizes to named versions. Boggiano also highlighted a few other ways Packagist is improving the transition for people who are renaming their default branches:

In the last couple of days we further improved the experience for alternative default branch names by keeping track of the default name configured in the VCS repository. If you change your default branch to main for example, then master will not have any meaning on your repository. The default branch will receive an alias internally to 9999999-dev unless you configure a branch-alias to a different version yourself.

These changes allowed us to fix a few related issues on packagist.org. The default branch is now always shown on top in the version list. There is no more special treatment for master as a branch name, everything should work no matter what you decide to call your default branch.

While it may not be very difficult for repository owners to change the ‘master’ branch to another name, there may be more required changes to established workflows, integrations, and pipelines that reference the default branch.

The GitHubUpdater plugin is one popular plugin that may be impacted by developers renaming their default branches. Andy Fragen is currently exploring a solution that would offer developers better support for having a principal branch named something other than ‘master:’ 

It is my intention to support whatever naming scheme the developer/user of this plugin desires to use. I am currently testing a branch locally to allow for a Release Branch header to accomplish this. This would require a header in your repository with Release Branch: trunk or Release Branch: main if your move from the previous default of master.

Over the weekend, the discussion around this issue heated up on our post about renaming the ‘Master’ branch of WordPress-owned Git repositories, as well as on the original proposal. Opponents contend that these types of changes in terminology are performative and do nothing to solve real problems like the lack of diversity in tech. Proponents argue that language is powerful and even small changes like this can help new contributors feel more welcome.

GitHub is also getting pushback on its initiative to discontinue using ‘master’ for the default branch. A reddit thread has more than 2,600 comments on the issue. The consensus seems to be that GitHub’s move is merely a gesture at best, and at worst a distraction from real issues and a waste of time and resources. Many see GitHub’s move as giving “the illusion of positive change” in the place of real effort on important issues, at the expense of broken scripts and integrations.

When Nat Friedman said GitHub is already working on renaming ‘master’ to ‘main,’ some users threatened to move to GitLab over it. However, GitLab is working on a similar initiative that would let users choose their own default branch name.

“GitLab is currently fairly opinionated about the default branch name, despite this diversity of preferences – in most situations, it will create a new project with a master branch, or configured for the first new branch to be master, without any user input, and without providing any choice to the user,” GitLab engineer Nick Thomas said. His proposal aims to give users a choice when creating new projects.

Gitlab still has the problem of deciding on what to set for a default branch name when one isn’t specified. Discussion on this issue is heated as well, although more GitLab users seem to be positively disposed towards the general idea proposed in the ticket. Thomas noted that whether master is an appropriate term in this context or not is “probably best taken up at the git-project-level.”

In response to Nat Friedman’s tweet about GitHub renaming the ‘master’ branch, Petr Baudis, the person who originally chose the default names for “master” and “origin,” said he regrets using these terms.

“I picked the names ‘master (and ‘origin’) in the early Git tooling back in 2005,” Baudis said. “This probably means you shouldn’t give much weight to my name preferences. I have wished many times I would have named them ‘main’ (and ‘upstream’) instead. Glad it’s happening.”

Jacob Rockowitz: Webform Cards... To infinity and beyond!!!

Main Drupal Feed - Mon, 06/22/2020 - 21:10

Our expectations of the Webform module are directly tied to Drupal’s Form API, a robust and secure framework for building, validating, and submitting forms. Still, Drupal’s current Form API implementation is about ten years old. It is starting to show its age. When Drupal’s Form API was built 16 years ago, form rendering and validation were always executed server-side; Ajax was a new kid on the block. Now, with modern frontend frameworks, like React and VueJS, form rendering and validation happen clientside, in the web browser. This approach results in a faster, more flexible ‘modern’ user experience.

Modernizing Drupal and Webform User Experience

The Drupal community is working on modernizing Drupal’s user interface and experience. In the meantime, Drupal and the Webform module should provide the best user experience possible. Any request to the server (aka the Drupal backend) is, by definition, slower than changes and behaviors happening in the client (aka web browser). The first step to improving Drupal and the Webform module’s user experience and performance to move most data validation to the client’s web browser using clientside validation.

Clientside validation

Even though modern browser’s support HTML 5 Clientside validation, the implementation is inconsistent and there are known accessibility issues. The Clientside Validation module , which uses the jQuery Validation plugin, solves some of these accessibility issues and offers the most consistent user experience. Installing the Clientside Validation module will immediately improve...Read More

Jacob Rockowitz: Webform Cards... To infinity and beyond!!!

Main Drupal Feed - Mon, 06/22/2020 - 21:10

Our expectations of the Webform module are directly tied to Drupal’s Form API, a robust and secure framework for building, validating, and submitting forms. Still, Drupal’s current Form API implementation is about ten years old. It is starting to show its age. When Drupal’s Form API was built 16 years ago, form rendering and validation were always executed server-side; Ajax was a new kid on the block. Now, with modern frontend frameworks, like React and VueJS, form rendering and validation happen clientside, in the web browser. This approach results in a faster, more flexible ‘modern’ user experience.

Modernizing Drupal and Webform User Experience

The Drupal community is working on modernizing Drupal’s user interface and experience. In the meantime, Drupal and the Webform module should provide the best user experience possible. Any request to the server (aka the Drupal backend) is, by definition, slower than changes and behaviors happening in the client (aka web browser). The first step to improving Drupal and the Webform module’s user experience and performance to move most data validation to the client’s web browser using clientside validation.

Clientside validation

Even though modern browser’s support HTML 5 Clientside validation, the implementation is inconsistent and there are known accessibility issues. The Clientside Validation module , which uses the jQuery Validation plugin, solves some of these accessibility issues and offers the most consistent user experience. Installing the Clientside Validation module will immediately improve...Read More

Jacob Rockowitz: Webform Cards... To infinity and beyond!!!

Main Drupal Feed - Mon, 06/22/2020 - 21:10

Our expectations of the Webform module are directly tied to Drupal’s Form API, a robust and secure framework for building, validating, and submitting forms. Still, Drupal’s current Form API implementation is about ten years old. It is starting to show its age. When Drupal’s Form API was built 16 years ago, form rendering and validation were always executed server-side; Ajax was a new kid on the block. Now, with modern frontend frameworks, like React and VueJS, form rendering and validation happen clientside, in the web browser. This approach results in a faster, more flexible ‘modern’ user experience.

Modernizing Drupal and Webform User Experience

The Drupal community is working on modernizing Drupal’s user interface and experience. In the meantime, Drupal and the Webform module should provide the best user experience possible. Any request to the server (aka the Drupal backend) is, by definition, slower than changes and behaviors happening in the client (aka web browser). The first step to improving Drupal and the Webform module’s user experience and performance to move most data validation to the client’s web browser using clientside validation.

Clientside validation

Even though modern browser’s support HTML 5 Clientside validation, the implementation is inconsistent and there are known accessibility issues. The Clientside Validation module , which uses the jQuery Validation plugin, solves some of these accessibility issues and offers the most consistent user experience. Installing the Clientside Validation module will immediately improve...Read More

Jacob Rockowitz: Webform Cards... To infinity and beyond!!!

Main Drupal Feed - Mon, 06/22/2020 - 21:10

Our expectations of the Webform module are directly tied to Drupal’s Form API, a robust and secure framework for building, validating, and submitting forms. Still, Drupal’s current Form API implementation is about ten years old. It is starting to show its age. When Drupal’s Form API was built 16 years ago, form rendering and validation were always executed server-side; Ajax was a new kid on the block. Now, with modern frontend frameworks, like React and VueJS, form rendering and validation happen clientside, in the web browser. This approach results in a faster, more flexible ‘modern’ user experience.

Modernizing Drupal and Webform User Experience

The Drupal community is working on modernizing Drupal’s user interface and experience. In the meantime, Drupal and the Webform module should provide the best user experience possible. Any request to the server (aka the Drupal backend) is, by definition, slower than changes and behaviors happening in the client (aka web browser). The first step to improving Drupal and the Webform module’s user experience and performance to move most data validation to the client’s web browser using clientside validation.

Clientside validation

Even though modern browser’s support HTML 5 Clientside validation, the implementation is inconsistent and there are known accessibility issues. The Clientside Validation module , which uses the jQuery Validation plugin, solves some of these accessibility issues and offers the most consistent user experience. Installing the Clientside Validation module will immediately improve...Read More

Jacob Rockowitz: Webform Cards... To infinity and beyond!!!

Main Drupal Feed - Mon, 06/22/2020 - 21:10

Our expectations of the Webform module are directly tied to Drupal’s Form API, a robust and secure framework for building, validating, and submitting forms. Still, Drupal’s current Form API implementation is about ten years old. It is starting to show its age. When Drupal’s Form API was built 16 years ago, form rendering and validation were always executed server-side; Ajax was a new kid on the block. Now, with modern frontend frameworks, like React and VueJS, form rendering and validation happen clientside, in the web browser. This approach results in a faster, more flexible ‘modern’ user experience.

Modernizing Drupal and Webform User Experience

The Drupal community is working on modernizing Drupal’s user interface and experience. In the meantime, Drupal and the Webform module should provide the best user experience possible. Any request to the server (aka the Drupal backend) is, by definition, slower than changes and behaviors happening in the client (aka web browser). The first step to improving Drupal and the Webform module’s user experience and performance to move most data validation to the client’s web browser using clientside validation.

Clientside validation

Even though modern browser’s support HTML 5 Clientside validation, the implementation is inconsistent and there are known accessibility issues. The Clientside Validation module , which uses the jQuery Validation plugin, solves some of these accessibility issues and offers the most consistent user experience. Installing the Clientside Validation module will immediately improve...Read More

WPTavern: Gutenberg Times to Hold Live Q&A on Block-Based Themes and Full-Site Editing

Wordpress Planet - Mon, 06/22/2020 - 20:19

On Friday, June 26, Gutenberg Times will be holding a live Q&A on block-based themes and full-site editing. The Zoom webinar will begin at 18:00 UTC and last for around one hour, depending on how many questions are asked by viewers.

The target audience of the event will be theme developers or anyone interested in designing using the upcoming system that relies on blocks to build the entire front end. To attend, viewers should register via Zoom. By registering, Zoom will send viewers reminders about the event and allow them to ask questions to the panel. The session will also be streamed live via the Gutenberg Times YouTube Channel.

Birgit Pauli-Haack, the owner of Gutenberg Times, is hosting the event. The following developers from the WordPress theming community will join her on the panel:

  • Eileen Violini – Design Engineer at Sidetrack Studio and Customer Success Engineer at CastosHQ.
  • Carolina Nymark – WordPress Themes Team representative and creator of the Full Site Editing Course.
  • Kjell Reigstad – Designer at Automattic who works on the Gutenberg project.

“I find the four-people-Brady-Bunch-on-screen format the most appealing and gives people the opportunity to get their questions answered,” said Pauli-Haack.

Friday’s event will begin with a five-minute demo from Reigstad. The goal is to show how theme authors can create a page header and footer by taking those concepts and applying them to a block-based theme. It is an introduction point that theme authors can use in their existing themes without starting from scratch.

The second part of the event will center on answering questions that Nymark often gets from other developers, such as how to put block code within template files. Reigstad will be showcasing demos based on those questions.

“After that, it’s all about the audience questions that I will read and the panel answers,” said Pauli-Haack. “The discussion and demo are all conversation starters. In other Q&As, after introductions, I had my own questions, and then made it all about the audience questions.”

Potential viewers can watch past Q&A events from the Gutenberg Times archive to get a feel for the format.

There is no set direction for the event beyond showing the initial demos. Pauli-Haack wants to put the audience in the driver’s seat and allow the discussion to go wherever it needs to go. The panel is open to exploring all aspects of building themes with blocks, and it is a good opportunity for theme authors to communicate with developers who are at the forefront of the transition into full-site editing.

“I have the feeling it will be more about how to transition from the old way to the new way and how all the pieces fit together,” she said. “Beyond the demos, there probably won’t be many code examples. We will discuss the resources out there and how to approach them.”

Gutenberg Times is in its third year of sharing information about the Gutenberg project. Pauli-Haack describes it as her passion project. “The goal has been to collect all the fragmented information while Gutenberg was in beta before the release in Dec 2018,” she said. However, the site has continued going beyond its initial phase. Pauli-Haack has been holding live Q&As since 2018 on the site.

DrupalCon News: Drupal9 at DrupalCon Global

Main Drupal Feed - Mon, 06/22/2020 - 17:15

The Drupal community has accomplished amazing things with the release of Drupal 9. It’s the easiest major version upgrade in a decade, extending the pattern of continuous innovation from Drupal 8, with dramatically easier tools for end-users. 

DrupalCon Global is a great opportunity to learn more about Drupal 9 and the Drupal project overall. No matter your role or where you are in your Drupal journey, there are sessions that will give you the content you need. 

 

Sooper Drupal Themes: Sooperthemes is now DXPR. Meet DXPR Builder 1.0.0: The Drupal Layout Builder For Marketers

Main Drupal Feed - Mon, 06/22/2020 - 14:21
A Drupal Authoring Experience For Marketers

We are excited to announce that as of June 22nd, 2020, we have a new name and brand identity:

Sooperthemes is now called DXPRWhy we are rebranding

Starting 10 years ago we have worked to make Drupal easier to use for everyone. In the past 10 years, much has changed for all of you who interact with Drupal in some way.

With the introduction of Drupal 8, a new era of scalable, more reliable development practices were introduced. With Drupal 9, an affirmation of Drupal's intent for long-term stability and easier updates has calmed everyone's hearts (at least here at DXPR).

Drupal authors and digital marketers have replaced themers and site builders as our primary audience. 5 years ago our focus started shifting from developing our low-code Drupal theming framework towards developing a visual authoring experience that lets authors create media-rich, mobile-friendly pages without coding. 

Jurriaan Roelofs, Founder at DXPRTry live demoIntroducing DXPR Builder 1.0.0

Inspired by you — our customers and supporters — we introduce DXPR Builder: the layout builder that showcases the result of our 5 years of listening, developing, and improving the Drupal experience for Drupal's most important audience: The Authors.

Authors, especially digital marketers, have been frustrated by the lack of a visual layout builder for Drupal. With the inability to create mobile-friendly layouts, digital marketers relied on IT support to create landing pages, or even anything more complicated than a Word document.

With DXPR Builder, you can upgrade any Drupal 7, 8, or 9 websites with the following awesome no-code capabilities:

  • Immediate inline editing
  • Mobile-friendly layouts up to 12 columns
  • Access your local media or DAM
  • Add marketing elements including icons, countdown timers, and more
  • Supports Drupal views, blocks, translations, revisions, workflows, and other Drupal technologies.
Giving back to the open-source community: DXPR Theme on d.o.

Because our source driver of new business is now our Drupal layout builder module we have decided to open-source the DXPR Theme.

DXPR Theme, the successor of Glazed Theme, was previously our most successful product. This low-code Drupal design framework is a Bootstrap based theme plugin for Drupal 7, 8, and 9.

With over 200 easy-to-use theme settings, DXPR Theme will save your IT team many hours and improve the time-to-market for global changes to the design of your website.

DXPR is more than just a new brand

With our new pay as you grow pricing model, we will be able to help developers implement and customize our product better than ever.

Customer service and tech support are areas that DXPR will focus on improving. I have been the customer service manager at Sooperthemes over the past 10 months; we grew our support team by employing more tech support engineers and enhanced our workflow automation to improve promptness and efficiency. 

As part of the DXPR team I am excited to say that our support and customer success teams are now ready to handle enterprise-class clients, and are ready to serve the Drupal community. 

Nour Eldin, Customer Service Manager at DXPRCurious what your Drupal experience looks like with DXPR?Try Live Demo

Sooper Drupal Themes: Sooperthemes is now DXPR. Meet DXPR Builder 1.0.0: The Drupal Layout Builder For Marketers

Main Drupal Feed - Mon, 06/22/2020 - 14:21
A Drupal Authoring Experience For Marketers

We are excited to announce that as of June 22nd, 2020, we have a new name and brand identity:

Sooperthemes is now called DXPRWhy we are rebranding

Starting 10 years ago we have worked to make Drupal easier to use for everyone. In the past 10 years, much has changed for all of you who interact with Drupal in some way.

With the introduction of Drupal 8, a new era of scalable, more reliable development practices were introduced. With Drupal 9, an affirmation of Drupal's intent for long-term stability and easier updates has calmed everyone's hearts (at least here at DXPR).

Drupal authors and digital marketers have replaced themers and site builders as our primary audience. 5 years ago our focus started shifting from developing our low-code Drupal theming framework towards developing a visual authoring experience that lets authors create media-rich, mobile-friendly pages without coding. 

Jurriaan Roelofs, Founder at DXPRTry live demoIntroducing DXPR Builder 1.0.0

Inspired by you — our customers and supporters — we introduce DXPR Builder: the layout builder that showcases the result of our 5 years of listening, developing, and improving the Drupal experience for Drupal's most important audience: The Authors.

Authors, especially digital marketers, have been frustrated by the lack of a visual layout builder for Drupal. With the inability to create mobile-friendly layouts, digital marketers relied on IT support to create landing pages, or even anything more complicated than a Word document.

With DXPR Builder, you can upgrade any Drupal 7, 8, or 9 websites with the following awesome no-code capabilities:

  • Immediate inline editing
  • Mobile-friendly layouts up to 12 columns
  • Access your local media or DAM
  • Add marketing elements including icons, countdown timers, and more
  • Supports Drupal views, blocks, translations, revisions, workflows, and other Drupal technologies.
Giving back to the open-source community: DXPR Theme on d.o.

Because our source driver of new business is now our Drupal layout builder module we have decided to open-source the DXPR Theme.

DXPR Theme, the successor of Glazed Theme, was previously our most successful product. This low-code Drupal design framework is a Bootstrap based theme plugin for Drupal 7, 8, and 9.

With over 200 easy-to-use theme settings, DXPR Theme will save your IT team many hours and improve the time-to-market for global changes to the design of your website.

DXPR is more than just a new brand

With our new pay as you grow pricing model, we will be able to help developers implement and customize our product better than ever.

Customer service and tech support are areas that DXPR will focus on improving. I have been the customer service manager at Sooperthemes over the past 10 months; we grew our support team by employing more tech support engineers and enhanced our workflow automation to improve promptness and efficiency. 

As part of the DXPR team I am excited to say that our support and customer success teams are now ready to handle enterprise-class clients, and are ready to serve the Drupal community. 

Nour Eldin, Customer Service Manager at DXPRCurious what your Drupal experience looks like with DXPR?Try Live Demo

Sooper Drupal Themes: Sooperthemes is now DXPR. Meet DXPR Builder 1.0.0: The Drupal Layout Builder For Marketers

Main Drupal Feed - Mon, 06/22/2020 - 14:21
A Drupal Authoring Experience For Marketers

We are excited to announce that as of June 22nd, 2020, we have a new name and brand identity:

Sooperthemes is now called DXPRWhy we are rebranding

Starting 10 years ago we have worked to make Drupal easier to use for everyone. In the past 10 years, much has changed for all of you who interact with Drupal in some way.

With the introduction of Drupal 8, a new era of scalable, more reliable development practices were introduced. With Drupal 9, an affirmation of Drupal's intent for long-term stability and easier updates has calmed everyone's hearts (at least here at DXPR).

Drupal authors and digital marketers have replaced themers and site builders as our primary audience. 5 years ago our focus started shifting from developing our low-code Drupal theming framework towards developing a visual authoring experience that lets authors create media-rich, mobile-friendly pages without coding. 

Jurriaan Roelofs, Founder at DXPRTry live demoIntroducing DXPR Builder 1.0.0

Inspired by you — our customers and supporters — we introduce DXPR Builder: the layout builder that showcases the result of our 5 years of listening, developing, and improving the Drupal experience for Drupal's most important audience: The Authors.

Authors, especially digital marketers, have been frustrated by the lack of a visual layout builder for Drupal. With the inability to create mobile-friendly layouts, digital marketers relied on IT support to create landing pages, or even anything more complicated than a Word document.

With DXPR Builder, you can upgrade any Drupal 7, 8, or 9 websites with the following awesome no-code capabilities:

  • Immediate inline editing
  • Mobile-friendly layouts up to 12 columns
  • Access your local media or DAM
  • Add marketing elements including icons, countdown timers, and more
  • Supports Drupal views, blocks, translations, revisions, workflows, and other Drupal technologies.
Giving back to the open-source community: DXPR Theme on d.o.

Because our source driver of new business is now our Drupal layout builder module we have decided to open-source the DXPR Theme.

DXPR Theme, the successor of Glazed Theme, was previously our most successful product. This low-code Drupal design framework is a Bootstrap based theme plugin for Drupal 7, 8, and 9.

With over 200 easy-to-use theme settings, DXPR Theme will save your IT team many hours and improve the time-to-market for global changes to the design of your website.

DXPR is more than just a new brand

With our new pay as you grow pricing model, we will be able to help developers implement and customize our product better than ever.

Customer service and tech support are areas that DXPR will focus on improving. I have been the customer service manager at Sooperthemes over the past 10 months; we grew our support team by employing more tech support engineers and enhanced our workflow automation to improve promptness and efficiency. 

As part of the DXPR team I am excited to say that our support and customer success teams are now ready to handle enterprise-class clients, and are ready to serve the Drupal community. 

Nour Eldin, Customer Service Manager at DXPRCurious what your Drupal experience looks like with DXPR?Try Live Demo

Sooper Drupal Themes: Sooperthemes is now DXPR. Meet DXPR Builder 1.0.0: The Drupal Layout Builder For Marketers

Main Drupal Feed - Mon, 06/22/2020 - 14:21
A Drupal Authoring Experience For Marketers

We are excited to announce that as of June 22nd, 2020, we have a new name and brand identity:

Sooperthemes is now called DXPRWhy we are rebranding

Starting 10 years ago we have worked to make Drupal easier to use for everyone. In the past 10 years, much has changed for all of you who interact with Drupal in some way.

With the introduction of Drupal 8, a new era of scalable, more reliable development practices were introduced. With Drupal 9, an affirmation of Drupal's intent for long-term stability and easier updates has calmed everyone's hearts (at least here at DXPR).

Drupal authors and digital marketers have replaced themers and site builders as our primary audience. 5 years ago our focus started shifting from developing our low-code Drupal theming framework towards developing a visual authoring experience that lets authors create media-rich, mobile-friendly pages without coding. 

Jurriaan Roelofs, Founder at DXPRTry live demoIntroducing DXPR Builder 1.0.0

Inspired by you — our customers and supporters — we introduce DXPR Builder: the layout builder that showcases the result of our 5 years of listening, developing, and improving the Drupal experience for Drupal's most important audience: The Authors.

Authors, especially digital marketers, have been frustrated by the lack of a visual layout builder for Drupal. With the inability to create mobile-friendly layouts, digital marketers relied on IT support to create landing pages, or even anything more complicated than a Word document.

With DXPR Builder, you can upgrade any Drupal 7, 8, or 9 websites with the following awesome no-code capabilities:

  • Immediate inline editing
  • Mobile-friendly layouts up to 12 columns
  • Access your local media or DAM
  • Add marketing elements including icons, countdown timers, and more
  • Supports Drupal views, blocks, translations, revisions, workflows, and other Drupal technologies.
Giving back to the open-source community: DXPR Theme on d.o.

Because our source driver of new business is now our Drupal layout builder module we have decided to open-source the DXPR Theme.

DXPR Theme, the successor of Glazed Theme, was previously our most successful product. This low-code Drupal design framework is a Bootstrap based theme plugin for Drupal 7, 8, and 9.

With over 200 easy-to-use theme settings, DXPR Theme will save your IT team many hours and improve the time-to-market for global changes to the design of your website.

DXPR is more than just a new brand

With our new pay as you grow pricing model, we will be able to help developers implement and customize our product better than ever.

Customer service and tech support are areas that DXPR will focus on improving. I have been the customer service manager at Sooperthemes over the past 10 months; we grew our support team by employing more tech support engineers and enhanced our workflow automation to improve promptness and efficiency. 

As part of the DXPR team I am excited to say that our support and customer success teams are now ready to handle enterprise-class clients, and are ready to serve the Drupal community. 

Nour Eldin, Customer Service Manager at DXPRCurious what your Drupal experience looks like with DXPR?Try Live Demo

Sooper Drupal Themes: Sooperthemes is now DXPR. Meet DXPR Builder 1.0.0: The Drupal Layout Builder For Marketers

Main Drupal Feed - Mon, 06/22/2020 - 14:21
A Drupal Authoring Experience For Marketers

We are excited to announce that as of June 22nd, 2020, we have a new name and brand identity:

Sooperthemes is now called DXPRWhy we are rebranding

Starting 10 years ago we have worked to make Drupal easier to use for everyone. In the past 10 years, much has changed for all of you who interact with Drupal in some way.

With the introduction of Drupal 8, a new era of scalable, more reliable development practices were introduced. With Drupal 9, an affirmation of Drupal's intent for long-term stability and easier updates has calmed everyone's hearts (at least here at DXPR).

Drupal authors and digital marketers have replaced themers and site builders as our primary audience. 5 years ago our focus started shifting from developing our low-code Drupal theming framework towards developing a visual authoring experience that lets authors create media-rich, mobile-friendly pages without coding. 

Jurriaan Roelofs, Founder at DXPRTry live demoIntroducing DXPR Builder 1.0.0

Inspired by you — our customers and supporters — we introduce DXPR Builder: the layout builder that showcases the result of our 5 years of listening, developing, and improving the Drupal experience for Drupal's most important audience: The Authors.

Authors, especially digital marketers, have been frustrated by the lack of a visual layout builder for Drupal. With the inability to create mobile-friendly layouts, digital marketers relied on IT support to create landing pages, or even anything more complicated than a Word document.

With DXPR Builder, you can upgrade any Drupal 7, 8, or 9 websites with the following awesome no-code capabilities:

  • Immediate inline editing
  • Mobile-friendly layouts up to 12 columns
  • Access your local media or DAM
  • Add marketing elements including icons, countdown timers, and more
  • Supports Drupal views, blocks, translations, revisions, workflows, and other Drupal technologies.
Giving back to the open-source community: DXPR Theme on d.o.

Because our source driver of new business is now our Drupal layout builder module we have decided to open-source the DXPR Theme.

DXPR Theme, the successor of Glazed Theme, was previously our most successful product. This low-code Drupal design framework is a Bootstrap based theme plugin for Drupal 7, 8, and 9.

With over 200 easy-to-use theme settings, DXPR Theme will save your IT team many hours and improve the time-to-market for global changes to the design of your website.

DXPR is more than just a new brand

With our new pay as you grow pricing model, we will be able to help developers implement and customize our product better than ever.

Customer service and tech support are areas that DXPR will focus on improving. I have been the customer service manager at Sooperthemes over the past 10 months; we grew our support team by employing more tech support engineers and enhanced our workflow automation to improve promptness and efficiency. 

As part of the DXPR team I am excited to say that our support and customer success teams are now ready to handle enterprise-class clients, and are ready to serve the Drupal community. 

Nour Eldin, Customer Service Manager at DXPRCurious what your Drupal experience looks like with DXPR?Try Live Demo

Evolving Web: What's Next for Drupal 9?

Main Drupal Feed - Mon, 06/22/2020 - 14:01

Drupal 9.0 was launched earlier this month as a continuation of Drupal 8. This time around, the core update was more about updating the technology underlying Drupal's codebase and eliminating dependencies than introducing brand-new features, but fear not: we'll be getting some of those soon enough.

Drupal releases features on a semi-annual basis, and version 9.1 is expected to be rolled out around December this year. Due to the decentralized nature of Drupal's development, the roadmap for 9.1 isn't necessarily set in stone; that said, the strategic initiatives and core objectives are well-documented, so we know what we can expect in the foreseeable future. Most importantly, gone are the days when Drupal was developer-first, editor-second: it's all about usability and accessibility for everyone moving forward.

Let's take a closer look at what that might entail. On the menu: a new front-end theme, automatic updates, and community-driven improvements collected from the 2020 Drupal Product Survey.

Olivero Front-End Theme

When I built my first-ever Drupal site during an Evolving Web training session, I remember thinking two things: "Wow, this is really flexible and fun to use once you get the hang of it", and "Wow, the default theme looks a bit dated". I'm a fan of Drupal, but the Bartik theme and its decade-old design just don't quite do it justice for first-time users.

Drupal has made it a major priority to completely overhaul its user experience and be friendlier for everyone, not just developers. Now that Claro, a new, accessible admin theme, is available in Drupal 9, contributors are focusing on Olivero, a modern front-end theme designed to showcase the CMS in its best light out of the box. Like Claro, Olivero follows a new-and-improved design system that prioritizes user experience and accessibility.

Screenshot of the Olivero front-end theme for Drupal sites

It'll be a good few months before we can officially say bye-bye to Bartik, so here's what we know about Olivero so far to tide you over in the meantime:

  • It looks really good. Olivero's sharp colour palette, modern typography, and judicious use of white space gives Drupal sites a polished, state-of-the art look straight out of the box.
  • It'll be WCAG AA-compliant from the ground up. Accessibility is a major focus in Olivero, which is slated to include a high-contrast mode among myriad other accessibility-first features and functionality.
  • It supports all the most recent features added to Drupal, including embedded media and the drag-and-drop layout builder.

To read more about Olivero's development (and see the prototype high-contrast mode in action), check out this blog post by Lullabot, one of the teams involved in building the theme. According to the post's author, a launch within 9.1 is the most likely release scenario, so stay tuned this December.

Automatic Updates

As it stands, updating a Drupal site isn't the most straightforward process. That's set to change in the foreseeable future, however, as automatic updates have been one of Drupal's main strategic initiatives for some time now.

Major features of the existing Automatic Updates module, which is planned to eventually become part of Drupal core, include:

  • Major update announcements to notify admins when a core update is on its way, what it entails, and how to prepare
  • Update readiness checks to automate the process of ensuring sites are compatible with the latest update
  • One-click updating to allow admins to trigger the database update directly via the Automatic Updates service

These features are currently being tested and refined by the community, and we can expect a core release as soon as they're ready. Get all the details about the Automatic Updates project in the Drupal docs.

The 2020 Drupal Product Survey

Drupal's project lead Dries Buytaert recently started collecting responses to the annual Drupal Product Survey (here's the related post on Dries' blog). The survey's goal is to prioritize upcoming initiatives according to the community's needs. The results will be unveiled this July during the global virtual DrupalCon.

Looking at the survey's contents can give us some clues as to what might be coming to Drupal in the mid- to long-term (but we'll have to wait till the results are out to get a clear picture of how the Survey will influence Drupal's strategic direction).

Target Audiences

When you take the survey, the first questions are about how you use Drupal. The rest of the survey is then tailored according to your response. Here's a glimpse of the different demographics you can choose from to give you an idea of who the questionnaire is intended for (short answer: anyone who has anything to do with Drupal in any capacity!).

The first question on the Drupal Product Survey shows the scope of its audience

Content Editor Experience

The content editing experience in Drupal has seen constant improvements over the last several releases, but how will it evolve in 9.1 and beyond? The survey's questions for content creators include a list of potential Drupal enhancements, which respondents are asked to prioritize. A few highlights:

  • More refined draft/publishing control. This has already been addressed in recent updates; Drupal 9 includes enhanced content moderation workflows that are well-suited to actual editorial processes. It'll be interesting to see how this will be improved upon even further.)
  • Improved accessibility testing and control. Drupal core aims to adhere to stringent accessibility requirements out of the box (note leigh link here to that one page), but it could definitely offer even more testing features for creators directly via the admin UI
  • Improved contextual help and overall "how-to" guidance and Redesigned information architecture/simplified terminology for admin pages. A lot has been done in recent updates to make Drupal more user-friendly and approachable, so this survey question should be a good indicator of how successful those efforts have been--and what still needs to be done to further democratize the CMS.

Other noteworthy points relating to content creation workflows include:

  • Making more pre-built templates available
  • Autosaving
  • Real-time previewing of content being edited
  • Improvements to structured data and metadata management
Developer Experience

Site builders, theme builders, designers, and front- and back-end developers answering the survey also get questions about usability and accessibility, but those obviously look a bit different than the ones targeting content authors.

Discussion points aimed at developers and designers include these potential Drupal enhancements:

  • Improved configuration management
  • Additional front-end development tools, like NPM support and SDKs for common JavaScript frameworks
  • Drush-style out-of-the-box command-line tools integrated into Drupal Core (if you're currently looking for Drush commands to use during deployment, consider getting the Drush module, which adds several admin functionalities)
  • Improved data modeling tools
  • Better support for atomic content (i.e. reusable, channel-agnostic assets), in addition to a component-based theme system with reusable interactive theme elements like responsive tables
  • More modules added to Drupal Core, such as Feeds (to provide a migration UI), Rules (to provide a business logic UI), Admin toolbar, and Pathauto (for generating URL path aliases)
  • Privacy management support, such as user-managed identity access for GDPR
Help Shape Future Versions of Drupal

Of course, this is just the tip of the iceberg when it comes to future plans for Drupal. If you have an opinion on anything we just covered (or on Drupal in general), make sure to take the 2020 product survey (direct survey link) to have your voice heard. Drupal is, and always has been, a community effort, so by taking the time to fill out the questionnaire you'll be directly contributing to the future of a powerful open-source CMS that powers millions of experiences across the web.

Meanwhile, if you want the facts about the latest current edition of Drupal, sign up for our upcoming webinar What You Need to Know About Drupal 9.

+ more awesome articles by Evolving Web

Pages