Drupal news is a monthly highlight of useful articles and, of course, news from the Drupal world presented on Lviv Drupal Cafe. Every month, drupalers gather for beer and talk and we’re talking about what’s happening in our world of Everything Drupal - new trends, tricks, and techniques.


Evolution approach of "Continuous innovation" or Core updates that doesn’t kill you, but make you stronger.

Main feature of that “evolution approach” of continuous innovation (God I’m tired of this word) is a conscious support of backward compatibility via deprecated code. Meaning that when new API’s / features added, which equals chances in module’s architecture, it’ll be working “the old way” for a while. And the moment this deprecated code will be removed from the core / modules - that would be Drupal 9. In short, D9 = D8 - deprecated code. Yes, I think that would be a bit of inconvenience for module maintainers to support both things, but if this approach will be followed by core modules at least - we’ll have really continuous evolution of the project.

http://buytaert.net/making-drupal-upgrades-easy-forever


Code deprecation policy.

Speaking of code deprecation. Official announce.

https://groups.drupal.org/node/516318


From App Store to Play Market: not quite.

Some changes in D.org projects: from now on you are able to create full projects (not sandboxes) without D.org’s Team approval. It raises concern about code quality of those “unapproved” projects, but luckily we’ve got tool to separate sheep from the goats or modules which are safe from ones which are not. You might have seen it already on D.org - it’s a shield symbol that means this module has been reviewed by security team and found to be written according to “Drupal Way” standards.

This, however, raised separate discussion that even with old system, some popular modules were badly written. Thing is, that “Feature” approach became popular relatively recently - 4-5 years ago, year or two after Drupal 7 release. And now it’s standard practice that module, in fact, is a “mini-framework” with API and some basic features / settings, upon which we’re building our own full scale features. But back in D5 / D6 and beginning of D7 time, modules often were “feature-o-modules” - that’s why they had such bad architecture / code quality.

https://www.drupal.org/drupalorg/blog/goodbye-project-applications-hello-security-advisory-opt-in


Web-omelette with user preferences and how to store them properly.

https://www.webomelette.com/storing-user-data-such-preferences-drupal-8-using-userdata-service


Let’s talk about 4th industrial revolution for a bit.

To be honest, 4th industrial isn’t what I was looking for in the first place - Drop solid is a company where Drupal’s Nick Veenhof, went to hold a CTO position in order to.. Promote Drupal and better Web in Belgium. Which is a bit funny, since Drupal itself has Belgium passport (Full article here).

But talking about 4th industrial revolution - as I’ve been saying for quite a while now, the only thing that makes you unique in digital century - is “humanessense” or just Being Human.

https://dropsolid.com/en/blog/fourth-industrial-revolution-three-act-play


Paragraphs VS Embed Entities VS Panelizer.

Very handy overview of three available approaches for organizing content work structure.

As it goes with Drupal, you can do the same thing in a few different ways - and that’s good. What’s bad, you need to know those ways and pick the right one for your current goal.

In short, think first then choose best option for your current case.

https://www.mediacurrent.com/blog/editorial-workflow-head-head-paragraphs-vs-entity-embed-vs-panelizer

Bonus: additional comparison of Paragraphs and ECK (https://www.chapterthree.com/blog/paragraphs-vs-eck-drupal-8). Also, fresh Bricks module - a bit better structured alternative for Paragraphs. In my opinion, these are two very similar modules that doing the same thing in slightly different ways. What’s good: support of Entities and revisions. This module worth a look at least.


Call of Duty (crossed out) feedback : Admin Menu

Sort of survey to find most added custom items / menu sections on commercial projects. Let’s make our admin menus better!

https://www.drupal.org/node/2863330


From D7 file entity to D8 media: a migration guide.

Case of custom Migrate class that handles the migration of media files to D8.

https://www.previousnext.com.au/blog/migrating-drupal-7-file-entities-drupal-8-media-entities


Second thoughts on composer or don’t put everything you got on production.

https://www.codeenigma.com/build/blog/do-you-really-need-composer-production


Bugs, those sneaky bastards.

Story of inconsistence that lived through 15 years.

https://www.thirdandgrove.com/accumulation-technical-debt-or-how-recently-opened-critical-core-bug-15-years-old


Future updates: a plan for next 12 months.

Initiative priorities for D8.4/D8.5. Your suggestions are welcome!

https://www.drupal.org/node/2858592


Fresh in Drupal! Short array syntax is in D8.

It’s a bit awkward, but this has been introduced in PHP 5.4 (B.C era in modern worlds.) and finally we have it in the Core! Make sure you adjust your code for that!

https://groups.drupal.org/node/516354


Smart default settings.

It’s worth noting that you can make content editor’s life better with smart default settings.

Remember: what you set up once, people don’t have extra pains of dealing with it every day.

http://savaslabs.com/2017/03/06/five-drupal-8-tips-to-empower-content-authors.html


Default pages.

Same stuff, but for pages.

http://www.vdmi.nl/blog/creating-default-pages-drupal-8


Webform, but not quite THAT webform

Finally we have proper webforms in D8! It’s worth mentioning that this is not D7 webform, but merge with ex Yaml_forms module. Now with UI and all you’ve been so fond of in D7 webforms.

https://dev.acquia.com/blog/drupal-8-module-of-the-week--webform-formerly-known-as-yaml-form/07/03/2017/17741


Fun Algorithm from Adobe & Cornell University

https://github.com/luanfujun/deep-photo-styletransfer

In other news, smart lads from Adobe and Cornell University has developed nice algorithm that enables to copy image look’n’feel from source to destination image. Take a look at examples.