•  powerful and versatile: from CMS for small websites to large community-platforms and EAI-applications - Corinis is your solution of choice

•  sophisticated: Corinis focuses not only on functionality but also on being easy to understand and implement. Every member of the project (designer, programmer, user,...) is able to focus on his task without having to think much about the other members or the solution itself. For example Corinis uses standard-technology only and doesn't introduce any new script-languages etc. one would have to learn.
  

• easy to use: The administration is easy to understand and use making it possible also for non-expierenced users to manage content, users, modules,.. in very little time.
  
  
• easy to install: Corinis comes also in packages which makes the installation very easy. But also without packages Corinis could be set up within a few minutes.
  
  
• open source: Corinis is published under the GPL license making it free software and giving you the oppurtunity to improve it.
  
  
• java based: Corinis is based on java/xml making it possible to integrate it into high-end backend-solutions and make it attractive also for large companies which are interested in using professional standard technology.
  
  
• xml based: Communication between the layers (presentation-application-data), between modules and the interfaces are xml-based giving you the possibility to easily integrate external functions/data/modules and to build interfaces very quickly.
  
  
• multilingual: Corinis follows a multilingual concept and therefore is based on specific language files. If your language isn't available yet, you can easily  create a language file for your language.
  
  
• extensible: Corinis is module-based - an easy-to-understand API makes it possible to write and integrate own modules.
  
  
• platform-independent: Since Corinis is Java-based it runs on nearly any hardware and system.
  
  
• database-independent: Corinis comes with MySql recommended, but every other database for which a JDBC-connector exists is possible. You can also choose  XML-files as your data-storage-system of choice.
  

Corinis has a real abstraction between functionality and layout:

• a module has no predefined layout, only in the administration. When implementing it you are using XSL to create your own layout
  
• functionality is not "omnipresent" - if you need a function/module, you call it, you dont have a bloated/possibly buggy file you include, you just call the function (thanks to java/oop)
• there is no "predefined" way of using a module/function. You can use the guestbook as a comment on pages, or a forum. The functionality is there, how you use it is up to you!
• Easily extendible: You can override/interface to available classes to create your own special modules - while keeping the ability to upgrade the backend without destroying your custom created functionality
• When implementing corinis, you dont have to worry to change everything on each update. Since the interface functions and their response stays the same the output will always work.

Corinis is not an all-in-one package:

• The functionality is easily availabe, but not with a design. That's the part of the one who implements it.
• You can specify the functions that are accessible -> this improves security and makes your code more readable, plus it allows you do implement much faster than with most other products since you dont have to strip away functions you dont need, but add functions you need (normally, when creating the html from a webdesign you normally start from scratch with a few copy/paste snippets and not by finding a similar design and remove everything you dont need...)
• The only thing that is available out of the box is the administration - the rest is availablr through howtos or template packages

For people which are used to Content Management Systems and/or frameworks, doing the first steps with corinis might become a little hard, because of the turn around way of working with it. But once you get the hang it allows you to create webpages/complex portals or communities with much less time.

If you think this is not true, or want more information feel free to use the forum.