The library in the Zend Framework can be very useful by itself in applications. And frequently we do use it, or portions of it, in applications that do not use the Zend Framework. However, this is not the case with the ZendMail component. We have found the PHP IMAP functions to be substantially more robust than ZendMail for providing email functionality within applications. Because of this, even when we do write a site using ZendFramework, we will use the PHP IMAP functions and not ZendMail.
A domain name should be as descriptive and un-mystical as possible. It need not necessarily be prosaic, but it should definitely be straightforward. Long domain names are easier to remember than paraphrased or partially abbreviated ones. Catchy is sometimes nice if it is catchy enough, and the catchiness is readily identified with your business or organization. Catchy can be harmful if it leads to your competition or some other site. It is better to be long winded and explicit than brief cryptic.
Relying on an MVC framework to provide consistency can end up disappointing if it is implemented or maintained badly. A site that is designed well and coded well will be more comprehensible to subsequent programmers than a badly implemented or maintained framework. A developer working on your site who circumvents the framework can leave a mess for subsequent maintenance.
There are a good number of frameworks that implement the MVC paradigm and which conform to standards for good coding. The ZendFramework is the one that we will use if you as a client request an off-the-shelf framework.
All of our site products use an MVC implementation that provides a minimum of structure and a maximum of flexibility.