The problem: Updates in Drupal require FTP / SSH and a bit of know-how
When the average Drupal site owner without ssh, cvs and other geek gadgets wants to update modules on or themes on their Drupal site, they currently have to do the following:
- Go update status and see the mod is out of date
- Take the site offline
- Make a backup (if they can)
- Know where to find the module on d.o., download the tarball
- Unzip the tarball
- Remove the current directory
- Use FTP to upload the new directory
- Run update.php
We’re trying to provide a way that users can get the same user friendliness of a package manager like Synaptic. Where updates and new installs are just a few clicks, no geek gadget belt.
I’ve entered the D7 ux fray, specifically focusing my generous amount of Acquia community time on getting a project called the Plugin Manager spruced up and into core.
For more background on the effort, see: Plugin Manager in Core (part 1).
The solution: make Drupal update like everything else.
Here is the issue:
Plugin Manager Part 2 : The update status UI
I've been working out some wireframes of how the process might look, and I wanted to share them with the planet to see what people thought of them. So without further ado: