- 🇦🇺Australia pameeela
I think that between Project Browser and Automatic Updates, this is largely solved?
Thinking of how configuration synchronization is both UI friendly (mostly) as well as Drush friendly, I am wondering if there would be any way in D9 to integrate some form of composer_ui module that could run composer in the "background" through Drupal's core UI? (I'm somewhat aware of ludwig, but i know a lot has changed since then. )
I myself have had really good experience with Composer, and see the great benefit of it. it is actually the first CLI tool i have used. I have noticed however there are a lot of site builders who are completely overwhelmed with the thought of Composer. I have an e-commerce site, and plan on migrating it from 7 through 8 in sandbox to 9 live, so I am up for the challenge :).
I also however manage a squarespace site for my church and would love to move it to Drupal, but i have quite a bit of hesitation seeing as i might need to hand the keys over to someone who is uncomfortable with the CLI. Is anyone else seeing the difficulty this will continue to produce for Drupal as a platform? I could see loosing a lot more community support over this.
I realize it would be extremely difficult to get the precision and flexibility out of the UI that you would get using the Composer CLI, but to have a way for simple site builds to be easily maintained with basic composer dependency management would probably be appealing to a great number of site builders who love Drupal, as well as potential new developers that might be a blessing to the community.
What better place to discuss ambitious digital experience dreams?
Love me some Drupal!
Thanks for hearing me out.
:)
Postponed: needs info
11.0 🔥
composer
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think that between Project Browser and Automatic Updates, this is largely solved?