Blog posts

    September 20, 2017! For most of us it was just an ordinary Wednesday, yet for the Drupal community and for everyone owing (or planning to own) a Drupal e-shop it was a major release day marked in their calendars: the stable version of Drupal Commerce 2.0 for Drupal 8 was launched into the wild (following no less than 6 beta "teasers") at that date! And along with it, 2 key promises were put forward: the whole Drupal commerce experience will be redefined and development teams will get more productive (since this new version of Drupal Commerce performs remarkably at scale)...
    What makes Node.js work so well in a serverless environment? Is it its lightness? Or its “plays well with all OS's” feature maybe? Or is it its high accessibility translating into a wide pool of developers for you, as a service technology(s) vendor, to select from? Is it the accessibility (again) which, empowers you, the developer this time, to break the skill level restriction and the back-end vs front-end strict delimitation? Why should you build out your serverless app with Node.js? As the headline clearly states, I'll start this post already presuming that...
    Let's play a little empathy game! One which will help you realize why you do need to bother making your Drupal admin UI content editor-friendly: Step into the shoes of a first time Drupal user, of an inexperienced content editor accessing your Drupal site's admin interface for the first time. What do you think? Is that intricate network of forms loaded with “alien” terminology and the “specific” clutter of defaults in the Drupal 8 admin user interface…“ welcoming” enough for you? So, what's your opinion, from your standpoint as a Drupal...
    It's got modular codebase, a whole new architecture, it comes “packed” with lots of new advanced solutions for rich text editing and (well, what do you know!) real-time collaborative editing. In short: in CKEditor 5's case we're talking about a totally new product when compared to its predecessor, Cheditor 4, that we've been using in Drupal 8. Looking forward to seeing the real-time collaborative editing features (in particular) brought to Drupal 8. And to be honest I look forward to an in-browser editor with an equally user-friendly interface, the same approach to...
    And this is a years-old discussion. The good, the bad, and the ugly aspects of implementing such a functionality have been exposed and debated and... debated some more. Yet, since Dries Buytaert's keynote presentation, at Drupalcon Vienna 2017, the issue of automatic updates in Drupal core has turned from a never-ending discussion into a firm... call to action. If WordPress is already offering an automatic update facility to its users, so can Drupal right? What's the “mission statement” behind this initiative? Which are the strategic objectives of those Drupal...
    The headline says it all: I'm not going to tackle this comparison from an online store owner's perspective (unless, of course, we consider those cases when a store owner is its own store's developer, as well). Instead, I'm going to refer strictly to those particular features which would make a web developer, like me, prefer one of the 2 e-commerce platforms over the other. In short: I'll be analyzing the pros and cons of Shopify vs Magento from a developer's perspective only. So, keep on reading if you're interested in finding out:
    Long gone are the days of “page-centric” design! “What will you put on the “Services” page?”, “How will the Portfolio page look like?”, “How many pages will the website have in the end?” etc. etc. It's time you got off this (over) beaten path of “waterfall design” and adopted a more agile way of and carrying out challenging, complex web projects. It's time you leveraged the component-based approach to UI design, breaking it down into small, easily identifiable, clear purpose-carrying puzzle pieces/components instead of key pages!
    Collect, analyze and leverage your data and you shall... stand out in the digital arena! But how can you streamline these 3 data handling process? How can you automate them, “infuse” them with time efficiency and keep all data analyses safe from any type of subjectivity? You go for a big data platform, no doubt about it! And now the question that arises is: to Hadoop or not to Hadoop? Weight the top pros and cons of using Hadoop and find out whether it's the perfect fit for your own use case, for your specific data environment:
    “… easily customizable, content-rich, maintainable forms” I should have added as well, right? For building “just” forms and surveys in Drupal 8 is not the real challenge (you always have the Contact module “up your sleeve” for that). Building robust, “tweak-able” web forms and, moreover, forms that even editors and themers can tweak and that site builders can create right in the UI, now that's the true dare! The test that we'll be putting the Drupal 8 Webform module to in this tutorial here: Webform is the rewritten version of the YAML Form for Drupal 8...
    Isn't it frustrating when 2 equally "tempting" web technologies compete for your preference, if you're a developer, and for your resources if you represent a company? Take these 2 highly popular technologies which have divided the web community into 2 groups: each one of them comes with its own heavy load of advantages, balanced by their sets of drawbacks, too! In conclusion: in the Node.js vs Ruby on Rails debate there's no such thing as “THE technology that fits all use cases and scenarios”. There's only “THE one that makes the best fit for... you”: for...