As a developer why do you want to use EPiX? 

EPiX can be used on each project as your framework.  Instead of creating a user and navigation management/cms system for each client start with a code base which you can extend depending on what you may need.  We have used the EMDK in many projects to speed up development and have a project coding standard which a large group of developers, from a number of different countries, can work against.

 Using the EMDK you can create new document templates to change the look of how documents are presented to the end user.  A skin can either be customised in the gui or a completely new one created.  Or create a new module, we have created

• a donations module to keep track of monies donated to a charity via Worldpay.  A report can be generated to see who can gift aid the donation to claim this back.
• an online travel insurance site that hooks up to a uk bank
• a status manager to view jobs/errors in queues
• a matching engine for comparing trades and their settlements
• and many many more...

EPiX is a portal suite product.  Using EPiX you can build an internet/intranet/extranet site which can be customised for any site.  It has some inbuilt functionality/modules for you to use:

• CMS
• Navigation
• User Management
• Templates
• Web Dav
• Library
• Gallery
• To Do
• Annoucements
• Skins (which you can customise in a gui)
• JSR 168 compliance.  So you can deploy your own jsr 168 portlet and register it with EPiX.
  

But you are not limited to these set of modules.  Using the EMDK you can create your own module, all you need is Java experience.  You can download it here.  To read about setting up a development environment read here.

If you run into any problems/issues remember to  subscribe to our user group email.