Reply to comment
- Not Just a Contact Database
-
These optional components give you more power to connect and engage your supporters.

civiCASE
Case management for clients and constituents.

civiCONTRIBUTE
Online fundraising and donor management.

civiEVENT
Online event registration and participant tracking.

civiMEMBER
Online signup and membership management.

civiMAIL
Personalized email blasts and newsletters.

civiREPORT
Report generation and template management.



Re: My comments
Thanks for feedback - a few comments:
Ad 1. Applied. :-)
Ad 2. Buttons are tab specific, so we need to keep them contained within. When you switch to another tab, the set of actions will change.
Ad 3. True, the screen is packed. :-) However, I'm thinking about introducing more space by increasing fields padding, not by releasing margins. What do you think?
Ad 4. If we introduce icons for actions, this needs to be introduced system-wide, so it's a decision coming out of contact view screen and I would rather postpone it for now. I'm planning to introduce informative icons for Bulk email and perhaps for primary objects (email, address, etc). I would rather avoid introducing icons as labels.
Ad 5. It's a mockup. ;-) Made note of it, will introduce it when implementation starts.
Ad 6. Good idea, I will definitely think about something here.
Ad 8. It's a mockup, again. ;-) However, the idea is to have one surrounding div (like #crm-container), than each table with specific data group (phones + IMs, emails + website, addresses, etc) in separate div, so you can lay out the screen in one or two columns with CSS stylesheet.