The article discusses indepth the following principles:
- minimise the number of options
- be robust and error-proof
- provide task-based interfaces
- hide implementation details
- meet core usability guidelines
- match authors' mental models
- support both frequent and infrequent users
- provide efficient user interfaces
- provide help and instructions
- minimise training required
- support self-sufficiency
eZ Publish while not perfect meets many of the principles at least in some aspect. When I have a bit more time (yeah right) I may evaluate eZ based against these principles in more depth.
Making something as complex as a CMS especially one as feature packed and complex as eZ Publish usable is a huge task but in the end it is a tool that has to be used and usibility is important.
While I'm not sure about where eZ Publish 4.0 is at right now it might be a good time to note whats good about the current admin interface and what areas could be improved.