|
In FocusSince 1994, Quoin has built sophisticated applications for media, publishing, retail, finance, life sciences, and other industries. Read more ... |
Jahia Features
|
ID |
Function |
Feature |
Jahia |
|
1 |
Architecture and Standards |
Ability to easily move content from test to production systems |
Jahia can easily replicate content through its remote server publishing and import/export features. |
|
2 |
Architecture and Standards |
Cross browser support |
Jahia supports Internet Explorer and Firefox for content managers. The system can support any browser for content delivery to visitors. |
|
3 |
Architecture and Standards |
CSS-based layout |
There are no graphical limitations to content style and format when using CSS within Jahia. |
|
4 |
Architecture and Standards |
JSR 168/JSR 286 compliant |
Jahia supports the industry standard for portlet communication within a portal application. Jahia is built on top of the JSR168-compliant with both JSR-168 and JSR-286 standards. It integrates Pluto and Jetspeed-2 as a portlet execution environment. Communication between the portal and its portlets is standard and personalization can be set at the portlet level if necessary. |
|
5 |
Architecture and Standards |
JSR 170 compliant |
Jahia is based on JSR170 for all XML and Content Repository data interchange. Features such import/export or distant publishing use this standard. |
|
6 |
Architecture and Standards |
O/S independent |
Jahia is OS agnostic, both for the server side and the client side. If enterprise class architecture is already in place, it is recommended to remain with the existing environment. On the client side, only a web browser is necessary for browsing, authoring or administrating of the system. |
|
7 |
Architecture and Standards |
Ability to support clustering of multiple web servers for high traffic load. |
Clustering allows multiple servers to serve the web site; this allows more servers to be added as site traffic increases. In addition, a clustered environment can survive one of the servers crashing without taking down the site. Jahia supports clustering based on JBoss Cache. Configuration is easy, as clustering capability is native. Communication over TCP as well as UDP is available. |
|
8 |
Architecture and Standards |
CMS supports multiple databases (e.g. MySQL, Oracle) |
Jahia uses Hibernate as the persistence layer, thus it is database agnostic, supporting MySQL, Oracle, PostgreSQL, SQLServer. etc. |
|
9 |
Authentication, User Management and Rights, Security |
Ability to add new roles and rights |
Jahia provides the ability to add a new role with unique access rights/restrictions. Not only does Jahia offer the ability to add unlimited groups, roles and users, but also the access rights within Jahia can bet set to a site, section of the site, page, container, or even at a field level. Naturally, inheritance can be broken to set new roles for a part or an entire site. |
|
10 |
Authentication, User Management and Rights, Security |
An administrative portlet to manage roles and privileges |
Jahia provides administrators with an ergonomic and easy to use administrative module that allows, among other functionalities, to easily set users, groups, roles and profiles, in a wide range of combinations. The following is a small sampling of the roles and features available within Jahia: Reader: access to content for read only Author: contributor Area administrator: configure and manage a specific space Validator/ access rights management |
|
11 |
Authentication, User Management and Rights, Security |
Captcha |
External captcha solutions can be added at the form validation level and are easily integrated within a Jahia template, allowing a security feature that can reduce spam and automated registration or sign ups. |
|
12 |
Authentication, User Management and Rights, Security |
Integration and real-time authentication against an existing identity management system or enterprise directory (AD/LDAP) |
Jahia offers a native connection to an LDAP directory or Active Directory as
well as a full set of embedded user group management features. |
|
13 |
Authentication, User Management and Rights, Security |
Single Sign-On to manage authentication across multiple applications. |
When applications are deployed through JSR168 portlets, Jahia presents a list of roles pre-defined within the application installed in the Jahia content zone. The author can then define the proper mapping between these roles and groups / users defined in Jahia. Access to the application is then fully transparent: the user will not be required to identify again when connecting to an application through Jahia (Single Sign On). Authentication can also be external to Jahia: Jahia supports JAAS, CAS and NTLM standards, as well as cookie authentication. A user authentication through a third party application can be automatically transferred to the Jahia platform. This can be extended to non-standard authentication protocols by implementing a specific authentication valve for a custom user repository. |
|
14 |
Authoring |
Browser-based WYSIWYG editing that allows non-technical users to author and maintain their own content |
Content is dynamically edited with Jahia. Through the in-site editing interface, an author can easily preview and compare changes in real time. Jahia integrates the WYSIWYG FCK editor that delivers rich content management including: Page setup (title, paragraph) Font management (typography, colors, size, etc) Picture and media file insertion General file and link insertion Ability to cut/paste from text editors Ability to select among predefined style sheets |
|
15 |
Authoring |
DreamWeaver Integration |
DWT can integrate JSPs, allowing for direct integration with Jahia. |
|
16 |
Authoring |
Editable Help Subsystem |
This feature can be easily integrated and customized to user specific needs. |
|
17 |
Authoring |
Implicit metadata assignment. |
Jahia allows for implicit metadata assignment; specific content type can be automatically assigned with a predefined set of metadata. |
|
18 |
Authoring |
MS Word Integration |
The FCK editor can clean up Word-specific tags, allowing for easy import of content from sources outside the browser. |
|
19 |
Authoring |
Must support metadata entry as part of the authoring process |
Jahia supports metadata entry as part of the authoring process. In addition, all metadata is compatible with the Dublin Core standard. Existing metadata compatible with the Dublin Core standard are supported within Jahia. It is also possible, within Jahia, to define a specific list of metadata via an easy-to-use user interface. Access to metadata can also be restricted according to user and group membership. |
|
20 |
Authoring |
Spell check. |
Jahia integrates the FCK editor that delivers rich content management
features, including Automated Spelling correction. |
|
21 |
Authoring |
WebDAV support |
Jahia integrates a fully functioning file server built on the WebDAV standard. Each user or group owns public or private folders, allowing for collaboration through secured authentication. Files can be copied and pasted for the user’s computer or saved from MS Office. The Jahia web project checks for the integrity of rights between these files and containing web pages. |
|
22 |
Collaborative Tools |
Blogs |
Jahia provides users with a powerful blog template that can be customized for specific needs. |
|
23 |
Collaborative tools |
Group Collaboration - discussion groups |
Jahia bundles several forum/discussion templates, including the “Jahia Blog” template and the integrated “j Forums” portlet |
|
24 |
Collaborative tools |
Group Collaboration - project areas |
Jahia integrates a fully functioning file server that works under the WebDav
standard. Each user or group gets a public or private directory in order to
allow for collaborative and authentication-based work. Files can be uploaded or
downloaded by a simple copy/paste from a desktop or save from a Microsoft®
Office program (for example) to a Jahia server. |
|
25 |
Collaborative tools |
Group Collaboration - wikis |
Jahia is built as a wiki (through its in-site editing presentation), and allows for any type of wiki customization through template customization. |
|
26 |
Collaborative tools |
Inbound RSS syndication |
Jahia natively supports imported XML content, including RSS feeds. Portlets that allow subscribing to RSS feeds are also provided. |
|
27 |
Collaborative tools |
Outbound RSS syndication |
Jahia supports multiple template types for content, including generating RSS feeds. |
|
28 |
Content Management |
Ability to publish effective date content automatically |
Automated publishing is achieved through the Jahia time based publishing feature. When content is created, the author specifies when it will start to be visible to authorized users and when it will expire. Advanced preview mode allows the authors to view the state of the page at a given date or time of their choice.(The author can view the content at anytime). |
|
29 |
Content Management |
Ability to stage content |
Content preview is available natively in Jahia; it is one of the principles of “In-site Editing”. Jahia also supports server staging (replication of the live site) through its XML import/export module, which allows for easy publication and content replication between Jahia instances. |
|
30 |
Content Management |
Content validation |
Content definition is separated from content presentation. The validator can be set at the content form entry level. Validation is also an obvious step for the publication workflow. |
|
31 |
Content Management |
Facilitate content life cycle management |
Jahia allows for validation of content created according to N-Step configurable differential workflows (with an inheritance mechanism): this includes notification, global or specific validation. Content being validated is locked in order to maintain its integrity, and workflow can be made language specific. Notifications are sent to process stakeholders and validation can be performed globally or specifically thanks to a dedicated workflow dashboard. The in-site editing view provides an immediate status (with a traffic light) of all zones where a specific workflow applies. |
|
32 |
Content Management |
Facility to reuse content |
Jahia allows users to publish content by pushing structured data (content categories and metadata). The content is authored once and published in several locations and formats. A good example of nested content is the RSS 2.0 feed built in Jahia blogs templates. Content is generated and the JSP leverages an XSLT RSS 2.0 style sheet to parse the XML flow on the fly. Content can also be gathered from another Jahia site through the content picker module. When the source is modified, target destinations are also modified. |
|
33 |
Content Management |
Hierarchical taxonomy support |
The taxonomy is hierarchical, allowing for a simple list of terms or a much more complex tree of terms. There is no limit to the depth of hierarchy. |
|
34 |
Content Management |
Metadata management and taxonomy support |
It is possible, within Jahia, to define a specific list of metadata via an easy-to-use user interface. Access to metadata can also be restricted according to user and group membership (see prior answers). |
|
35 |
Content Management |
Must support content at the chunk/paragraph level |
Jahia delivers a full content personalization engine. Administrators can define access rights for an identified user or a group, for an entire site, a section, a page and/or a content zone (even for a field) in a page. This offers a maximum level of granularity. Administrators and/or users can define or specify personalization through a simple graphical interface and specific CSS. The content personalization may also be done using a “user properties system” linked to a profile. The content personalization can be changed either manually by the user or according to automated parameters (i.e. specific criteria). |
|
36 |
Content Management |
Staging not just content, also templates, JavaScript etc |
Jahia supports replication of a complete site to a testing/staging server through its XML import/export module, which allows for easy publication and content replication between Jahia instances. |
|
37 |
Data Repository |
Ability to easily add fields to documents/ content records - extensible metadata |
Content can be managed through categories and each category can have its metadata extended. |
|
38 |
Data Repository |
Methods to manage structured versus unstructured data |
Content can be managed through categories and rules can be assigned based on these categories. |
|
39 |
Integration & Development Tools |
Ability to integrate with existing applications. |
Jahia relies on different mechanisms to integrate existing application. Based on the technical and functional characteristics of each application, one of these mechanisms will be used: Out-of the box integration of JSR-168 and JSR-286 compliant portlets Webclipping is also available, andJahia offers HTML or SQL web clipping features generating portlets to present information from third party systems. This web clipping mechanism allows for encapsulation in a site of any application: the integration of applications residing, or not, on the same standards, is complete and includes navigation (without iframes). Custom Web Services integration can also be implemented in the JSP templates
to fetch data from a business app. This solution usually involves significantly
more integration work that the two previous solutions, but can be useful in
cases where standard complicant portlet and webclipping do not match technical
constraints. |
|
40 |
Integration & Development Tools |
Automatic import/migration from legacy sites. |
Jahia's XML import/export module enables content from a legacy Jahia to be imported seamlessly. Content from a legacy non-Jahia site can be imported with one or possibly a series of simple XSL transformations. |
|
41 |
Integration & Development Tools |
IDE support (Integrated Development Environment) |
Jahia development can be performed through any Java/J2EE IDE. |
|
42 |
Integration & Development Tools |
Current Web Development Languages |
Jahia is a full java J2EE application, and offers taglibs/API to ease JSP integration |
|
43 |
Integration & Development Tools |
XSLT (Extensible Stylesheet Language Transformation) or open source frameworks for templating |
Content is structured through JSP templates where integrators can define a
variety of additional logic (SOAP calls, Struts framework usage, etc.). There
isn’t any proprietary language to be used within Jahia: it comes with a full
library for JSP integration. |
|
44 |
Integration & Development Tools |
Integrating remote data sources (e.g. XML). |
Jahia’s Import/Export of content is done through XML standards. The Jahia module is compatible with the JSR 170 DTD standard. Content structured through this standard can easily be imported and deployed in Jahia. Jahia can also allow content from an external web service or application to be integrated through its web clipping or Portal management feature. |
|
45 |
Integration & Development Tools |
Relates database information to documents |
Within Jahia, documents can be associated with a user or administrator-defined set of metadata. |
|
46 |
Integration & Development Tools |
Extensible and customizable (APIs and Web Services). |
Jahia not only allows for templates to be customized and extended, but its portal management and web clipping features also allow for easy integration of third party functionalities. Jahia features can also be extended through collaborative development. |
|
47 |
Integration & Development Tools |
Binary file support such as spreadsheets and media assets. |
Jahia offers Digital Assets Management capabilities, seamlessly integrated into the application. Binary files are indexed and can be tagged specifically for faster access. |
|
48 |
Personalization |
Ability for users to subscribe or unsubscribe to content and services. |
Jahia provides the ability for users to subscribe to newsletters, RSS feeds, discussion forum, etc… |
|
49 |
Personalization |
Configure alerts and notification services and direct to roles or users. |
Jahia allows for alerts and notifications. For instance, administrative users will receive alerts/notices for administration tasks such as workflow tasks validation or publication, as well as server issues. |
|
50 |
Personalization |
Offer ability to set themes. |
Jahia offers the ability to define and use different stylesheets or themes. |
|
51 |
Personalization |
Personalize at the role or individual level to set the look and feel. |
After login, the user can have access to personalized content.
Personalization can be pushed to its limits: personal home page, personal site,
etc. The fine granularity of access right management also allows sharing all
corporate needs (stylesheet, look and feel, control of available template for
use, etc…). |
|
52 |
Personalization |
Personalize at the role or individual level to set the service provisions provided |
Jahia offers the ability to apply different stylesheets or themes based on the role of the end-user. |
|
53 |
Personalization |
Provide the ability for individuals to configure layout and utilities. |
Jahia provides the ability for end users to configure layout and utilities, via WYSIWYG tools. A provided template also demonstrates Jahia’s ability to feature drag and drop of content items by the end users, in a way similar to iGoogle or My Yahoo.This functionality will be pushed even further within Jahia’s next release(drag and drop of content). |
|
54 |
Reports & Analytics |
Ability to create custom reports |
Jahia is out-of the box compliant with Google Analytics, but any other similar mark-up based tool can be integrated in the templates.Jahia has its own statistics system from which data can be exported to reporting tools. |
|
55 |
Reports & Analytics |
WebTrends or integration with other web log processing tool |
Integration with WebTrends or Google Analytics can be done easily, from a simple integration of Jahia logs. |
|
56 |
Search |
Ability to search in other languages |
Apache Lucene can support different character sets required for multi-language indexing and search. |
|
57 |
Search |
Support current search |
See below. |
|
58 |
Search |
Full text searching |
Jahia supports full text searching using Apache Lucene. Other search engines can easily be integrated as part of a Jahia system. |
|
59 |
Search |
Support of key-word search and taxonomies. |
Jahia includes a powerful open source search engine (Apache Lucene) that indexes all metadata as well as PDF and Microsoft Office files. A search API is also available to retrieve content as a function of its categorization and/or metadata. Search results are displayed according to the user’s access rights. Keywords are highlighted in the results and users are able to save their searches for a faster access to targeted information updates. Jahia also offers advanced search capabilities, and the search results pages can be fully configured through customized templates. |
|
60 |
Site Management |
Ability to automatically archive content |
Jahia offers several means to archive content: A piece of content can have a publication end date: therefore even if it isn’t accessible online, it will always be available to the author. A piece of content can be deleted: but it will always be available in the versioning system, and authors can roll back previous content versions when necessary. A piece of content can be moved from an archive zone to an online zone ruled by different access rights. Finally, any content, from a single element to an entire site, can be exported as an XML archive, allowing for a full backup at any time. |
|
61 |
Site Management |
Automated code validation |
Jahia embeds the FCK editor that bundles standard validation. This tool supports validation using the XHTML transitional DTD. |
|
62 |
Site Management |
Automated Link checking |
URL integrity for document and internal links are checked in a file/url typed field as well as in bigtext typed field. All page deletions and moves are instantly propagated throughout all navigation bars pointing to the content. |
|
63 |
Site Management |
Support for multiple language usernames |
Jahia supports multiple languages and unlimited users creation. |
|
64 |
Site Management |
Support for multiple languages |
Jahia supports all languages compatible with the UTF-8 standard. Jahia allows for content versioning and management as a function of language. Languages can be mandatory (no publication possible without the required language), or optional. If an element isn’t translated, language can be specified as uniform (a single language) or multiform (more than one language). New languages can be added easily through the user interface at any time. |
|
65 |
Site Management |
Traffic analysis package or service |
Jahia is pre-configured for use with Google Analytics (a form in the
administration module allows entering Google Analytics credentials, and the
system takes care of all the tag integration). The concept of content viewing /
creation is integrated into Jahia in the form of an administration module. This
module is designed to complement specific tools like WebTrends and any other log
analysis tool. This module is for administration use only –but access can be
opened to other profiles- and its logs can be exported using XML / XLS / CSV.
|
|
66 |
Site Management |
Versioning - compare any two revisions |
Versioning is automated in Jahia: any published content is archived and can be found easily, even restored to replace more recent content. The version can be previewed in the versioning module before being recalled in the editing module. This type of modification is published only after workflow validation, like any other modification. |
|
67 |
Site Management |
Versioning - roll back to any revision |
It is possible to display and publish any previous version of content (with the maximum level of granularity). |
|
68 |
Site Management |
Versioning and version control - all revisions kept |
Versioning is automated in Jahia: any published content is archived and can be found easily, even restored to replace more recent content. The version can be previewed in the versioning module before being recalled in the editing module. This type of modification is published only after workflow validation, like any other modification. |
|
69 |
Site Management |
Web accessibility - Section 508 compliant. |
Jahia allows for generation of WAI (Web Accessibility Initiative, compatible with section 508) compliant content. Jahia does not automatically correct HTML content to make it WAI compatible. Generation WAI compliant content is a complex project that implies specific templates definition. Jahia provides with two tools to allow authors to create compliant content: The template developer can create rules that apply to his template: for this purpose, Jahia integrates the Apache Struts Common Validator framework. It creates rules on form fields, for example, or makes the ALT tag mandatory for images. The HTML editor analyses content and will send errors pointing to the W3C
website error description. |
|
70 |
Site Management |
Short, meaningful URLs that can be bookmarked. |
Jahia offers a tool that allows for URLs to be customized, ensuring the URLs have good search engine optimization characteristics. |
|
71 |
Workflow |
Ability to assign content to a user |
Jahia access rights and user management features allow for administrators to assign any content to any user. |
|
72 |
Workflow |
Ability to customize workflows |
Jahia provides users with a multiple step differential validation workflow, allowing for content approval. Notifications are sent to process stakeholders and validation can be performed globally or specifically. The workflow process also differentiates validation per language and content is locked during the validation process. The in-site editing view provides an immediate status of all zones where a specific workflow applies. |
|
73 |
Workflow |
Ability to define the set of status's that a piece of content can have |
Multiple workflows can be defined for the same site. In Jahia, the workflow is inherited by default from the parent but the inheritance can be broken to set different workflows. Workflow can be set at the site, section, page, list and content level. |
|
74 |
Workflow |
Ability to set the status for a piece of content |
Jahia workflow can be set at the site, section, page, list and content level. |
|
75 |
Workflow |
Support task as well as content based workflow |
Jahia workflow is mainly content based, but Jahia offers a BPM module that allows for task-based workflow. |
|
76 |
Workflow |
Workflow generated alerts and audits |
The Jahia workflow notifies content stakeholders during the publishing process. |
|
77 |
Workflow |
Workflow branching or looping |
The workflow mechanism is sequential in Jahia. Any group of users can access the same tasks. |
|
78 |
Workflow |
‘view all’ of pending approval (an overview, not just in an individual version of a single page) |
Jahia provides users with a multiple step differential validation workflow, allowing for content approval. Notifications are sent to process stakeholders and validation can be performed globally or specifically. The workflow process also differentiates validation per language and content is locked during the validation process. The in-site editing view provides an immediate status of all zones where a specific workflow applies. |
|
79 |
Workflow |
Visual workflow editor |
Jahia comes with a WYSIWYG workflow control panel. |
Table 4: Jahia Features