General principles of Lutece
Description of Lutece and its components
Lutèce is written in Java and relies on recognized Open Source software (SpringFramework, Lucene, Freemarker, Ehcache, Jakarta-commons, PDFBox, ...).
Lutèce provides a web administration interface. The site administrator has access to a set of advanced features: dynamic definition of content types, workflow and online configurable notification rules, installation of plugins, page preview interface of the site, with possibility to suspend the publication of content blocks, user relationship management tools, line request tracking, RSS feeds and newsletters, newsletter, calendar, appointments ....
The graphic customization meets the standards of the Web HTML5 and CSS3 (current use of the Twitter framework Bootstrap), a graphical interface allows to add online various presentation styles as well as new page templates. An indexing engine (Lucene) allows you to search all the content of the site.
The range of services offered on a site can be easily customized by adding plugins. Lutèce's software architecture is modular. Each function of the site is managed by a plugin.
The main features are:
- Content Management System Content Management (CMS)
- customizable forms
- follow-up and instruction of requests (User Relationship Management)
- appointment management
- public consultation tool
- workflow configurable and extensible by specific modules comments content (pages, articles, ...), social networks, ...
- multimedia library search engine
- display and production of RSS feeds
- mailing lists
- quiz tools, polls, FAQ
Lutèce : a modular portal
Lutèce is developed on a J2EE base consisting of recognized open source libraries (Ehcache, Freemarker, Spring, ...). Its development respects the interoperability standards necessary for reusability, scalability and maintenance, development. The Lutèce framework is a development model in its own right, with standards and rules of design, architecture, and development to respect. Lutèce makes it possible to create Internet, Intranet or Extranet portals / applications. Plugins are grafted on the kernel, they can be added or removed from the project without interference with other components.
These plugins can themselves be supplemented by "modules", which are "plugin plugins" (for example: the mylutece plugin which centralizes the front-office authentication mechanisms is used with one or n modules depending on the type authentication to set up (Ldap, OpenId, OAuth, Persona, Database, ...).