This is a follow-on to our article, How Symfony components power Drupal’s drive to new frontiers. It looks at the nuts and bolts of four of the Symfony components/libraries Drupal uses, plus the Twig templating engine.
"There is no website being small enough, not to be perfectly suitable to be done with Drupal."
In other words: #Drupal is suitable also for small (and simple) sites. This is even more true with Drupal 10. And with Drupal as your underlying framework, your site easily grows with your requirements - and if they didn't grow, that's fine too!
My thesis in the blog post: "...not having a budget for a Drupal 7 to 10 update makes me wonder where the budget for the continued use of either outdated, or in the case of switching the platform, less capable technology should come from"
My prediction is, that a #Drupal 10 upgrade will pay back in the long run. But I'm not pushing anyone, it's more like providing a perspective which may help people see a bigger picture.
Exactly, Tim. Like many developers this article fails to understand the kind of organizations that are using #Drupal 7. It's not just a matter of the cost of rebuilding the entire site. People who spent years developing the skills to manage D7 now have to learn multiple entirely new and sometimes more complicated tools and languages. That's just not going to happen at many grassroots & nonprofit organizations.
And this really bums me out because it's just these kinds of users and site builders that adopted and evangelized Drupal from about 2005 to 2016. When Dries started taking about "ambitious" sites, we knew he wasn't taking about us.
@ruby@stpaultim@ultimike I take your point, still the reflection is worth having. There are so many professions that had decades of knowledge and experience, which eventually became less usefull - and they all have to progress. The same happens in the "web industry", just at a much much higher pace.
This is where my argument comes from: the longer you don't learn the new tricks, the more expensive it becomes.
Welcome to this week's Symfony Station Communiqué. It's your review of the essential news in the Symfony and PHP development communities focusing on protecting democracy. We also cover the cybersecurity world and the Fediverse.
New to Drupal 10.1 (coming this June) is a group of settings that will make Drupal front-enders' lives a lot easier (especially newbies). We can now control Twig caching (and disable render, and page caches) from the UI!
Unser Crew-Mitglied Peter auf dem DrupalCamp Ruhr 2023 mit seinem Thema zu "responsive images". So ganz perfekt ist die Lösung in Drupal noch nicht. Er stellt unterschiedliche Herangehensweisen vor und tritt mit dem Publikum in den Austausch.
Vielleicht kommt am Ende etwas heraus, was besser funktioniert. #dcruhr23#drupal#ResponsiveImages
The history of working to implement automated accessibility checks for Core goes back to 2017, shortly after a few open source accessibility tools were released. Deque’s axe-core had been released two years earlier, and it was starting to get embedded in a variety of other systems.
How four Symfony Components + Twig help simplify Drupal Core | Symfony Station (www.symfonystation.com)
This is a follow-on to our article, How Symfony components power Drupal’s drive to new frontiers. It looks at the nuts and bolts of four of the Symfony components/libraries Drupal uses, plus the Twig templating engine.
Symfony Station Communiqué - 12 May 2023 via Symfony Station (www.symfonystation.com)
Welcome to this week's Symfony Station Communiqué. It's your review of the essential news in the Symfony and PHP development communities focusing on protecting democracy. We also cover the cybersecurity world and the Fediverse.
Disabling Twig Caching Just Got A Helluva Lotta Easier (in 10.1)! Via Herchel.com (herchel.com)
New to Drupal 10.1 (coming this June) is a group of settings that will make Drupal front-enders' lives a lot easier (especially newbies). We can now control Twig caching (and disable render, and page caches) from the UI!
How Drupal Improves Accessibility (www.thedroptimes.com)
The history of working to implement automated accessibility checks for Core goes back to 2017, shortly after a few open source accessibility tools were released. Deque’s axe-core had been released two years earlier, and it was starting to get embedded in a variety of other systems.