Since its inception as an open-source Content Management System (CMS) in 2001, Drupal has grown into a technology that is trusted by many major corporations and governments around the world. The platform is constantly updated with the latest digital technologies by a community of more than 124k contributors. Drupal is not just a platform; it's a community made up of individuals who are passionate about open-source development. With Drupal Development Services, businesses can leverage the capabilities of this platform to develop custom solutions to fulfill specific requirements. This dedication has led to alternative solutions such as Learning Management Systems that are built on Drupal's backbone. We will examine the features of Drupal LMS for edtech businesses in this article.

My site runs on Drupal 9.5. I started preparing to upgrade to Drupal 10 right after 10.0.0 was released, but then I got hit with CKEditor 4 to CKEditor 5 blockers. The Linkit, CodeSnippet, and Entity Embed modules supported Drupal 10 but didn't support CKEditor 5. I could have updated to Drupal 10 and leveraged the CKEditor 4 contributed module, but I wanted to wait.

I will say, though. As we approach Drupal 10.1.0, more users will find a much easier upgrade path to Drupal 10 and CKEditor 5.

Drupal core is moving towards using a main branch. As an interim step, a new 11.x branch has been opened, since Drupal.org infrastructure cannot fully support a Drupal core branch named main currently. This will bring Drupal in line with many other projects.

Before: Moving development branch

Drupal core previously opened a new minor branch (like 10.2.x) each time the previous minor released its first alpha (like 10.1.0-alpha1). This ensured that developers could immediately work on the next minor development version, but it made the most recent branch a moving target that changed every six months.

From 10.1 onwards, we will change our branch naming strategy, for the following reasons:

• Make it easier for developers to choose the correct branch for issues.
• Remove noise on issues from the automated comments created when a branch is opened.
• Remove the overhead from issue bulk updates for branch changes.
• Reduce merge conflicts and merge request permission problems caused by target branch changes.

After: Introducing the 11.x branch

This new 11.x branch will be used as the main development trunk until Drupal.org supports the main branch name. Future feature and API additions will be targeted against the 11.x branch. All outstanding issues filed against 10.1.x will be automatically migrated to 11.x.

The 10.2.x branch will be opened from 11.x prior to 10.2.0.

Comparing the old and new branching model. View a bigger version.
 

From now on, all patches and merge requests should be submitted to 11.x. Changes will be cherry-picked or backported from 11.x to minor branches as required. Backport versions of patches and merge requests can still be posted against specific branches.

Despite the branch name, Drupal 11 development is not yet open. The 11.x branch will still accept only minor-version allowed changes until Drupal 11 development begins.. When Drupal 11 development begins, we will branch the next Drupal 10 minor branch prior to the Drupal 11 alpha development phase, and only then will 11.x will allow Drupal-11-specific changes.

There is currently a 'stub' 11.0.x branch for holding 11.x-only issues that can't be worked on yet. These issues will also be moved to the 11.x branch, and we will use an [11.x] title prefix and 'Major version only' issue tag to distinguish them. 11.0.x will then be opened properly when we're ready to tag an alpha release.

We will rename the 11.x branch to main when possible.

Why DrupalCon?

DrupalCon is the premier 3-4 day conference for the Drupal community. It brings together developers, content creators, site builders, and business leaders from around the world to learn and share their Drupal knowledge. You will have the chance to attend sessions, workshops, and keynotes led by some of the most innovative and successful Drupal leaders. The best part of DrupalCon (in my opinion) is participating in community events, networking opportunities, and social events with the vibrant community of Drupal enthusiasts. Check out this video below from the Drupal Association to learn more.

The internet has brought a paradigm shift in the world of education. Distance learning caused quite a stir during the mid-19th century when its first echoes were heard by people worldwide. Over the years, it continued to progress slowly, but the pandemic made it witness exponential growth and pushed it to a whole new dimension. Overnight, all educational institutions and business organizations transitioned to online learning to educate students and train remote employees. Within days, every school, university, coaching center, and business organization had its learning management system (LMS) like Drupal to cater to the educational needs of their pupils and employees. Drupal development for LMS integration is one of the best possible choices in the content management system (CMS) market for creating and managing an effective LMS. No doubt, we are no longer confined by lockdowns today, but the changes induced by the pandemic have been irreversible.

People of this generation expect websites to provide personalized digital experiences that speak to their individual needs and preferences. To back this up, Salesforce did a study and found that 66% of customers expect brands to understand their needs and expectations. As a Custom Software Development Services provider we are aware of the fact that personalized website content can keep users engaged, boost conversions, and foster long-term loyalty. It's now a breeze to achieve this by using content groups to organize your website's content based on shared traits or user interests.

In the article, you will learn how to slither into the world of leveraging content groups for a personalized Drupal experience. Brace yourself for the next level of personalization on your website - it's unarguably the best choice to make!

Behind every Drupal website are the modules and configuration settings that define the website's content model, authoring experience, presentation, and integrations. This post will explain and explore how the Schema.org Blueprints module handles configuration compared to a Drupal distribution and a Drupal recipe.

A Drupal distribution provides a predefined list of modules and configuration that define an entire website solution. For example, distributions offer a starting point for building a commerce, government, or intranet website. The Drupal community has acknowledged that distributions can be too opinionated and can become challenging to maintain.

There is now a Recipes initiative whose goal is to provide a modernized approach for distributions. A 'recipe' is a composable piece of site functionality and features bundled together. For example, a 'recipe' would provide an event registration system with an Event content type, a calendar view, and an online registration webform.

After installing a distribution or recipe, developers and site builders must alter and reconfigure what is installed to meet their organization's unique requirements. The 'Recipe' initiative and the Schema.org Blueprint module share the goal of providing a better starting point for building out a website's features and functionality. The big difference between these two solutions is the Schema.org Blueprints module does not ship with a predefined content model and configuration. Instead,...Read More