Provide optional composer integration but don't force users to understand how to use composer

Created on 20 January 2017, over 8 years ago

Updated 1 July 2025, 6 days ago

One of the items mentioned during some of Dries' keynotes is that there's a danger of Drupal leaving beginners and site builder behind. A major step in the current march forward is Composer usage. While Composer is a great tool and should become the standard for building complex projects, it should not be required to build a Drupal site unless a GUI is provided; additionally it should always be possible to download files from d.o, put them in the correct location (after extracting the archive) and have it work.

This should be seen as an opposition to #2477789: Use composer to build sites → becoming a requirement unless a GUI is provided.

📌 Task

Status

Postponed: needs info

Component

Idea

Created by

🇺🇸United States damienmckenna NH, USA

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 6 days ago →
🇦🇺Australia pameeela
Wondering if we can consider this outdated in light of Project Browser / Drupal CMS / Auto Updates? These still leverage Composer, but the user doesn't need to know about it. We are not done yet obviously, but certainly on the right track I think, if a bit late in coming.
Comment 5 days ago →
🇬🇧United Kingdom catch
Yes this happened with package_manager / project_browser / automatic_updates - lots of work still to do on those but the overall concept is implemented now.

Went ahead and credited everyone with more than one comment on this issue.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024