Drupal maintenance support plans 8.6 Release and The Road Ahead
Akshita
Thu, 09/06/2020 – 19:05
The Drupal maintenance support plans community is relentlessly working towards achieving the goal of easy usability with each version.
Not only has Drupal maintenance support plans granted its users the ability to integrate futuristic technologies but also provided the marketers with compelling digital solutions.
On September 5, 2020, Drupal maintenance support plans 8.6 was released. And started the wave of enthusiasm and whispers among the stakeholders.
Here’s how much it has succeeded in living up to the expectations and what is to be expected from Drupal maintenance support plans 8.7 release due in January 2021.
Drupal maintenance support plans 8.6 is released. And this what you should be excited about!
The Drupal maintenance support plans core team releases new (minor) versions every six months. These contain bug fixes, security patches, or both.
Drupal maintenance support plans Installation is Boring. Not Anymore.
That’s true. My first experience was as blank as the fresh installed Drupal maintenance support plans 8.3. “What am I supposed to do with this?”, I thought.
WordPress, on the other hand, had something to fiddle with, at least.
Version 8.6 brings with it Umami.
A demo food magazine website to demonstrate features of Drupal maintenance support plans core, Umami gives you dummy content to explore the CMS. Although released with 8.5, Umami is now part of the core under the out-of-the-box initiative.
The goal is to add sample content presented in a well-designed theme, displayed as a food magazine.
Using recipes and feature articles this will make Drupal maintenance support plans look much better right from the start and help evaluators explore core Drupal maintenance support plans concepts like content types, fields, blocks, views, taxonomy, quite easily.
Upgrade to Drupal maintenance support plans 8 with Complete Migration Guide
“This minor release provides new improvements and functionality without breaking backward compatibility (BC) for public APIs.”
Migrate With Ease
While not all Migration challenges are covered. Here are two of the important migration challenges addressed.
Backward compatibility
ID Conflict with Node translation
You can read more about Drupal maintenance support plans 8 migration challenges.
When launched, Drupal maintenance support plans 8 didn’t provide any sort of backward compatibility in modules and hence they were to be rebuilt in Drupal maintenance support plans 8.
However, this is solved with version 8.6. In fact, this is the first release of Drupal maintenance support plans 8 to offer a fully supported migration path from Drupal maintenance support plans 7. Several changes were needed to Migrate APIs to make this possible.
The most important migration module – Migrate – is not only, stable but adds up the ability to re-run migrations to pick up new content that was not available previously.
Another conflict with the multilingual website related to conflicting Node ids. Translations in Drupal maintenance support plans 8 are stored in a completely different way than in Drupal maintenance support plans 7 and Drupal maintenance support plans 6.
When migrating node data from Drupal maintenance support plans 6/7 to Drupal maintenance support plans 8, a lot of data would point to things that no longer existed.
The Drupal maintenance support plans Release Cycle
Starting with Drupal maintenance support plans 8.0.0, Drupal maintenance support plans core releases moved to a new release cycle schedule, and begin using the semantic versioning numbering system.
A release Window is decided for the site administrators (in advance) to look up for the days for a possible bug fix, security release, and minor feature releases.
For any change in release date, a public service announcement is issued before the release.
First Wednesday of every month is fixed for Bugfix release window for Drupal maintenance support plans 8.5.x and 7.x
Drupal Update Wednesday of every month is fixed for security release window for Drupal maintenance support plans 8.5.x and 7.x
Improved Editorial UI with Media Library
As an editor, you always want a seamless experience when editing. Be it with browsing blogs, or media that has been uploaded to the website.
The Media Library provides a views-based browser for previously uploaded media.
With the new version, you can add media to content via a media field, either by selecting from existing media or by uploading new media (including basic bulk upload support).
Building a Custom Layout is a No-Brainer Anymore
Choosing a custom layout no more requires you to write down long lists of codes. But this is not the only thing that makes layout interesting. The layout feature applies to much more than just content types.
Which implies that it can be used for media, contact forms, taxonomy, users, and more.
Layouts allow you to build one of the individual fieldable entities which are completely customizable.
As a marketer, it won’t take much time for you to implement new ideas into a landing page. No more do you require adding contrib modules like Display Suits or Stacks for the job.
The Layout helps to create one or more page sections and to choose from predefined options within them.
Seeing all the different issues and contributors in the release notes is a good reminder that many small contributions add up to big results.
-Dries
Drupal maintenance support plans 8.7 – The Roadmap
Streamlined bulk-upload form – An improved media bulk upload experience which exposes all fields on a single form.
Media Metadata improvements – A simple and intuitive tool to configure the metadata-to-drupal-fields mappings on media entities.
Faster Upload – Drupal maintenance support plans 8 will officially support PHP 7 and drop support for PHP 5.5 and 5.6 with 8.7 release. PHP 7 is much lighter and faster than its previous versions, which means your site becomes quicker to load.
Bring migrate_source_csv to the core – The imported content remains in the CSV files and there is a code to read it and create the relevant entries. Having migrate_source_csv in core would allow the developers to remove that code and use migrate instead. This is important because the contenta CMS uses this for migrations.
WYSIWYG integration – Ability to embed media into the content from the WYSIWYG editor. This will allow content creators to select from media library or create one by uploading an image without requiring any new APIs.
Editorial workflow config moving from content_moderation into a standard profile. This would help in smoother content staging.
Drupal maintenance support plans 8 to Drupal maintenance support plans 9 Upgrade. What to Expect?
Over time, maintenance of backward compatibility would become more intricate. Thus, the point will be reached when too much of deprecated code is there in Drupal maintenance support plans 8. At that time, deprecated systems will be removed and released as Drupal maintenance support plans 9.
So, Drupal maintenance support plans 9.0 should be almost similar to the last release of Drupal maintenance support plans 8 excluding the deprecated code. Upgrading from Drupal maintenance support plans’s latest version to Drupal maintenance support plans 9.0.0 should be as streamlined as the upgrading of minor versions of Drupal maintenance support plans 8 (eg. Drupal maintenance support plans 8.5 to Drupal maintenance support plans 8.6). Therefore, Drupal maintenance support plans 9 offers a clean slate to innovate more swiftly.
Here’s What Content Editors Want…
Let me be a little selfish here. Yes, Drupal maintenance support plans 8.6 looks really good to me and I look forward to working around that editor soon (because that is what concerns me, directly).
As a content editor, I have numerous times faced issues which leave me frustrated.
Improved media bulk upload, smart alt texts for code snippets, and meta information is something I actually look forward to.
Uploading video (non-youtube content) can sometimes be a headache.
There is still scope for major improvements to Drupal maintenance support plans’s content workflow, preview and staging capabilities. It will be done by improving aspects of the Entity API in the core.
Future Important Dates
8.7.0 Feature Freeze: January 2021
8.7.0 Release: March 19, 2021
With all the mentioned features, I believe, the community is successful in making Drupal maintenance support plans more intuitive and easy to use. We provide upgrade assistance, connect with us, drop a mail at hello@opensenselabs.com for a faster upgrade.
blog banner
blog image
Drupal maintenance support plans 8
Drupal maintenance support plans theme
Drupal maintenance support plans Umami
Content Editing
Drupal maintenance support plans Layout
Drupal maintenance support plans Migrate
Drupal maintenance support plans Upgrade
Drupal maintenance support plans Multilingual
Blog Type
Articles
Is it a good read ?
On
Source: New feed
