We have an hour to chat so bring your best Drupal topics and let’s do this thing!
Some examples to get your mind firing: how do I recreate [feature] on my Drupal 7 site in Drupal 8? I need to explain [complicated thing] to a non-technical stakeholder — any advice? How can I get Drupal and my CRM to play nicely?
This free call is sponsored by NTEN.org but open to everyone.
Integrating CRM into web technology has come as a turning point in business process automation. Well, enterprises can now easily evaluate and manage their contacts, existing clients, and leads or prospects generated through the marketing campaigns on social media platforms without any nuisance.
Last month I begun my second decade of working with Drupal! How crazy is that? I started at ComputerMinds in 2009. Drupalcon Paris was my first week on the job – I just remember taking so many notes, as if it were a university course! I had a lot to learn then, but now I can look back with a much more experienced head, hopefully wiser, with some sort of perspective.
It’s probably only over the last few years that it became clear that Drupal’s strength is its ability to be turned to just about anything that a website needs to do. That has meant that whilst alternative products have picked up the simpler sites, Drupal has been brilliant for projects with complex requirements. Integrating with CRMs and all sorts of other APIs, handling enormous traffic loads, providing content for apps – this kind of stuff has always been Drupal’s jam. You just have to know how to get it hooked up in all the right places!
Speaking of hooks, it’s been interesting to see Drupal move from its famous magical hooks, towards event-driven architecture. For me, that single shift represented an enormous change in direction for Drupal. I believe the events/subscriber pattern, as a part of a wider effort in Drupal 8 to deliberately use existing well-defined design patterns and solutions, is a sign of a much more mature and professional platform. Most coding problems have been solved well elsewhere, we shouldn’t reinvent the wheel! (Although I know I can be guilty of that!) That’s just one example of how the Drupal ecosystem has become more professional over the last ten years. Formal testing is another example. Many people have felt left behind by this shift, as a need in the enterprise world that Drupal could meet was identified. ‘Enterprise’ gets used as a dirty word sometimes – but to be frank, there’s more money and more suitable opportunity there!
That is something the Drupal community has to be honest about. It is rightly aiming to champion diversity, and be as accessible as possible for as many as possible across the world (I especially love that Drupal is now so good for multilingual projects). It’s not like Drupal is suddenly inappropriate for smaller projects – in fact, I’d still suggest it’s far ahead in many aspects.
But money makes things happen, and gives people their livelihood. I appreciate seeing honesty and innovation about this coming from community leaders. Thankfully those kinds of values are what drive the Drupal project, even if money is often the facilitator. As a community we must always fight to keep those things in the right relation to each other: money has an inevitable influence that we must accept, but it must be led by us and our values, not the other way around. I should add that I am very aware that I am privileged to be a developer in a leading Drupal agency, so my opinion will be shaped by that position!
To end with honesty and innovation myself, I would love to see the following carried into the Drupal project’s next 10 years, which I saw the community espouse over the last decade. I know I need to grow in these things myself!
Maintain excellence, even as the make-up of the community changes.
Deliberately listen to under-represented portions of the community, as an intentional force against the skewing effect of money/power.
Keep watch for what competitors and other relevant products are doing, to incorporate worthwhile things wherever possible.
Reflect on the strengths & weaknesses of Drupal (and its community) with honesty. Let’s make the most of what makes Drupal what it is and not be afraid for it to focus on that; the same goes for us as individuals.
I’m proud to work with Drupal, long may it continue!
In our recent rebrand at Third and Grove, we took on a Drupal headless build with a Gatsby front end. With any project where you are pushing the limits of what technologies are capable of, there were some growing pains.
These growing pains resulted from a few other places too (developers less familiar with React and Gatsby, using new and actively changing tools). We ran into some issues that we thought were really strange with bundle sizes, which turned out to be due to the way we were querying images. We also ran into load time issues with some SVGs that were being handled with a library called svgr. We also had a few fonts to load. Well, 18 (yeah that’s right). As a last resort implementing our own lazy loading helped bring us in a perfect lighthouse score!