Blog posts

    Please! No more praising the life-changing, the groundbreaking Paragraphs module! No more new content about what a "bundle of convenience" it is, about its easy to use interface or about its great Drupal developer-targeting features (for instance we, developers, get to reuse code in Paragraphs, remember?). I've done my part “praising” it already here, on this blog! Instead, today I'll d my best to help you solve one of your “empowering the end user” dilemmas: how can you make paragraphs in Drupal easy to use for your clients? More precisely for your actual end-users: your clients' content editors themselves!
    Keep calm and... update to the latest versions of Drupal 7 and Drupal 8, respectively to Drupal 7.56 and Drupal 8.3.4! The 2 Drupal security updates, released into the wild on the 21st of June, come to address certain (3, to be more specific) security vulnerabilities in Drupal core. So, it would be a reckless thing to do to just ignore all the work the security team has done and to leave your website (or your clients') “exposed” to brutal attacks, right? Now let's have a close look at both the “detected” vulnerabilities and their 2 patches:
    Really large teams of Drupal developers, even larger QA teams, a heavily weighting "overload" of custom code, a whole "ecosystem" of repositories... these are just some of the particularities of an enterprise site building process. A process which, if not ideally structured and on backed up by a "healthy" Drupal development routine, with a few basic rules, is prone to error and to "surprise" events right before launch day. Therefore, let me try and make a sort of "draft" list of 7 best practices to stick to when you're Drupal 8 enterprise site building:
    Drupal Commerce 2.x for Drupal 8's here, have no fear! “Fear” that the new version of the module may lack groundbreaking changes or that its developers may have failed to fully leverage Drupal 8's innovative functionalities. No such thing! Expect even more cool out-of-the-box features that will help you set up and customize your future online stores, tailor multiple buyer experiences and... more! Even though we're still talking about a “pre-release version” of Drupal Commerce 2.x, all the blog posts that this topic generated and the module's developers' own session, at DrupalCon Baltimore 2017, already weighted heavily on early adopters' decision making process.
    It's one of the handiest "tricks" for boosting your Drupal site's performance! As you move your JavaScript and CSS files to the footer, you'll instantly lift some of the “pressure” off your web pages, which otherwise would strive to simultaneously render both the HTML and the JavaScript (and the CSS, of course). In other words: you'll then be better organizing the whole page rendering process, ensuring that the “bulk” content gets served to your users first and, immediately after, the loads of JavaScript and CSS files. Now allow me to point out the options available to you for making this move:
    How do you strike a balance between an “unbeatable”, yet cumbersome password policy and user convenience on your Drupal website? Moreover: how do you implement aCUSTOM password policy in Drupal? One that should meet your (or your client's) website's particular needs of security or its specific needs of user-friendliness? Well, you put together Drupal's security-oriented pre-built features and those specific Drupal modules that best fit your site's needs and you tailor your own password policy! And speaking of these modules let me share with your my top 7 favorites ones!
    It's no longer a piece of news: Angular 4's out (since the 23rd of March)! The release followed the team's announcement that they would start implementing Semantic Versioning. Have you tried it yet? If not, then let me “do the honors” for you: let me stir up your curiosity with a “teaser” before you take it for a test drive! A “teaser” that will glide you through all its highlights, new performance improvements, under the hood changes and a focus on those features that will make migrating to this new version of Angular so very smooth.  The very first “change” is that... there is no breaking change!
    Your make a change on your Drupal 8 theme and...Voila! The update's already live on the desktop, the tablet and the mobile phone that you've been simultaneously testing it on! “Pure utopia”, right? Well, not exactly! “Browsersync” it's the right name for it, actually! This tool is the answer to all your prayers! The ones you made during all your discouraging, time-consuming cross-browsing testing marathons. Let's find out how precisely using Browsersync in Drupal 8 can dramatically speed up your changes syncing up:
    “Only for testing” or not entirely true? Are the experimental modules in Drupal 8 some great “tools” to submit new improvements for testing to the large community of Drupal users or are they more than that? Or are they, instead, some “packages” full of cool new features that you should seize the chance and “unwrap” right now? It's certain that this new type of Drupal 8 modules have gone beyond the testing phase. But it's also true that they're not yet fully supported and that you still get “Use them at your own risk” warning messages each time you try to install a “tempting” one.
    How easily do manage to keep your balance “surfing” on the huge wave of content personalization these days? The wave of delivering only user experiences personalized in the slightest details which, on many competitive websites, has even turned into hyper-personalization? Do you find it easy to play the role of a private eye “spying” on your website's visitors? Creating user personas based on their top interests, anticipated needs, preferences, demographics and... on a whole lot of other critical data that help you tailor your Drupal site's content?