This is your chance to have your vote counted, your voice heard. Below are requests from our community, things you would like to see fixed, implemented and added to ExpressionEngine. The goal is to get as many votes as possible, so I can have a clear priority rank based on our user feedback. Nothing here is guaranteed to be built or implemented, but it is all stuff that is possible and the more people that want it the better.
If you don't see something you want, please .(JavaScript must be enabled to view this email address)!
Place action buttons for forms in a footer that stays on screen in a sticky action bar.
Remove the dependency on images for the EE CP, move to a fully CSS based design.
Create a consistent and logical naming convention for labeling and naming with the CP
Pop a new window for any link to the front page of the website(s) being managed by EE.
Reduce, and reuse CSS, clean up tighten and unify the CSS of the CP allowing for easier customization and co-branding.
Better HTML structural markup, keeping in mind consistency and extension,
Re-factor, lessen and improve the use of jQuery, javascript and ajax in the CP. Rule of thumb if it doesn’t directly improve UX, leave it out.
A complete style guide and UI language for add on developers to utilize for their add ons, giving them a unified look and feel.
Develop a consistent and easy to use style language to use across the CP.
Have a system that allows us to make changes to all the ticked entries. See Low Variables as an example. There you can tick multiple items and then assign it to another folder, delete it or change the field type. So following that example, perhaps entries can have mass Status changes, Author assignments or even Channel assignment etc?
Allow creation of navigation templates much like you can create toolbar templates on Wygwam. New members get a toolbar based on the member group assignment.
From a users perspective these are no different and should not be labeled and stored in different locations. Consider consolidating all types of addons under a single name and into a single location.
Rebuild comment module from the ground up with better functionality, and greatly improved navigation and moderation of modules
Create a quick link to a filtered entries view for editing quickly.
More clearly mark sites within an MSM install, giving users a glance confirmation of the chosen site.
Allow template groups to be sorted alphabetically with a single click option.
Create a standard for ordering and sorting to be used across all table based views.
Consider changing the default from auto linking to not auto linking.
Allow set up and management of role based top level navigation.
Improve the template creation and editing workflow for developers/designers
Create a workflow for previewing content in context within the publishing and editing workflows
Improve the workflow for creating and managing channels.
Simplify and hone the CP design so that it melts away while you work.
Creating a more contextual and useful overview screen for high level areas.
Design the CP with the ultimate user in mind first and foremost, making the secondary user, the developer/designer
Create a better display and dismissal system for system messages, notifications and warnings.
Solve the display issue where accordions are being used, in order to remove the accordions
Rethink the main, secondary and workflow navigation within the EE CP.
Create a system or standard for multi-language website construction that is supported by the system
Allow snippets and global variables to be files, improving the overall template workflow. Additional information here
Check for add on compatibility with new versions to prevent data loss or broken web sites from critical add ons breaking upon upgrade.
Move Third Party folders outside of ExpressionEngine root, allowing for easier and cleaner updates.
Create a better email notification system for use with Safecracker forms, so that they can be used as advanced contact and data collection forms.
Allow the comment module to interface with twitter directly, without the use of a plugin.
Allow developers to turn off the contextual help button from specific member groups to avoid confusion.
Create a default front end site that provides best practices and good template authoring for new user educational purposes.
Remove the custom fields from the dependency of field groups. Allow one custom field to be applied to multiple channels or channel groups.
Create an easier way to migrate from server to server without a million path changes etc.
Create a class room pricing package for EE licenses to further educate future EE designers and developers.
Create better custom field support for Categories, allowing for more category tied flexible content.
Improve the definitions of global variables and snippets
Create better custom field support for members, potentially move currently standard fields like AIM, MSN etc.. to custom fields so they can be deleted.
Allow users to see analytics about their install on the CP homepage
Allow users to have CP homepage widgets, like accessories but for the main content section.
Allow developers and end users to customize the CP homepage with items important to their workflows.