- Issue created by @w01f
- 🇩🇪Germany jurgenhaas Gottmadingen
I'd say, that doesn't help much. People who find the Klaro module have already found what they need. It's more like the other modules should point to Klaro with a recommendation to use this instead.
The EU Cookie Compliance module already has that recommendation in bold at the top of their project page.
And the GDPR module makes one assume it does the same, but it has no consent management whatsoever. And the module itself doesn't seem to be much maintained these days.
- 🇺🇸United States w01f
Ahh, I had missed the bold message on the EU Cookie Compliance page (that's the one we use). If that's the case and they all tackle the same problem, so that Klaro is the obvious, de facto best option - then I agree and we can close this.
- 🇩🇪Germany jurgenhaas Gottmadingen
Yeah, it really sounds like the community is comming together behind this Klaro module. That's what I was told all over DrupalCon last week.
Here is also a link to our ADR on how the decision came together that Drupal CMS goes with Klaro: https://git.drupalcode.org/project/drupal_cms/-/wikis/Architecture-Decis...
