JBoss.orgCommunity Documentation
eXo Content is the singular name for the technologies used to capture, manage, store, preserve, and deliver content and documents. It especially concerns content imported into or generated from within an organization in the course of its operation, and includes the control of access to this content from outside the organization's processes.
The eXo Content users can manage both structured and unstructured content, so that an organization, such as a business or a governmental agency, can more effectively meet business goals (increasing the profits or improving the organizational process with efficient use of budgets), serve its customers (as a competitive advantage, or to improve responsiveness), and protect itself (against non-compliance, law-suits, uncoordinated departments or turnover within the organization).
eXo Content improves your operational productivity and efficiency. It enables you to transform unstructured content into structured content through the process of capturing, storing, managing, preserving, publishing and backing up while securely distributing it. The eXo Content portlet gives you a portal solution that can help you achieve these processes and leverage your business content across all formats for competitive gain. It also provides an environment for employees to share and collaborate on digital content and delivering a comprehensive unified solution with rich functionalities. Every component of your website can be organized, or easily reconstructed, which helps you keep your website under control.
eXo Content consists of three parts:
An extension of eXo Content is used to store, manage and track electronic documents and electronic images and allows documents to be modified and managed easily and conveniently by managing versions, properties, and more.
A way of looking at and controlling the processes presented in an organization such as service provision or information processing, etc. It is an effective tool to use make certain that the processes are effective with the purpose of better and more cost efficient organization.
Which helps in maintaining, controlling, changing and reassembling the content on a web-page. It also helps webmasters who handle all tasks needed to run a website, including development, design, content publication and monitoring.
While creating a site is a quick process, deciding what content to put into it and how to organize that content can take some time. Therefore, to make managing a site as easy and effective as possible, a site created with eXo Content will always adhere to a specific structure:

The Site Content is stored in collaborative workspaces of the underlying Java Content Repository (JCR).
Details:
Files in this folder are used to define the presentation of your entire site, such as font, color, size and more.
All the documents which are used in the site will be stored in this folder.
This folder contains programming scripts used on the site. Resources in this folder help make a web page's graphics and navigation more animated and dynamic.
This folder stores all the links used in the site.
This folder contains three sub-folders:
All sound files used in a site are stored here.
Pictures and other images used in a site are stored here.
All video files used in a site are stored here.
This folder is used to store the documents which present the main site content (text, images, hyperlinks, audios and videos) of the site.
The Web Content is the visual or aural content that is encountered as part of the user experience on a website. It include any or all of the following elements; text, images, sounds, videos and animations.
Much like the website as a whole, ensuring Web Content adheres to a specific structure makes creating and managing the content more effective and dynamic.
This is the key content, the text, images, links, tables, and other elements that make up the bulk of the web content.
This folder contains an image that is used as an illustration for the content. A summary also can be added to this image.
This folder contains CSS data which is used to present the web content. CSS controls the layout, font, color, and more.
This folder contains JS data which is used to make web content more dynamic.
A repository is a location where data is stored and maintained. The content repository stores web content and related digital data and is accessible to users locally, without requiring content to be transferred across a network.
A content repository is composed of a number of workspaces. Workspace is a term used by several software vendors for applications that allow users to exchange and organize files over a network (the Internet, for example).
In this case, the content repository consists of more than one workspace. The repository repository contains multiple workspaces, including: system, backup and collaboration workspaces.
This workspace is used to reserve system folders.
The backup process depends on the timestamps of published content; each published document has a defined period for which it can be published and, when it exceeds that time frame, it will be automatically archived to the backup database.
This workspace is mostly used when utilizing the Workflow based content publication life-cycle.
This workspace allows users to validate and manage documents. This is the central place to store and edit contents and media.
A drive can be understood as a shortcut within the content repository. It enables administrators to limit the visibility of each workspace to groups of users. It also offers a visual simplification of complex content storage arrangements by only showing the structure that is appropriate for users to interact with.
More specifically, a drive consists of:
A configured path where the user will start when browsing the drive.
A set of allowed views that could, for example, limit the actions available to users (such as editing or creation of content within the drive).
A set of permissions to limit the access to, and view of, the drive to a defined number of users.
A set of options to describe the behavior of the drive when users browse it.
A node is an abstract basic unit used to build linked data structures, such as linked lists and trees and computer-based representation of graphs. Nodes contain data and/or links to other nodes. Links between nodes are often implemented by pointers or references.
A node can be defined as a logical placeholder for data. It is a memory block which contains some data units, and optionally a reference to some other data (which may in turn be another node that contains other data). By linking one node with other interlinked nodes, very large and complex data structures can be formed.
Versioning means that, at any given time, the node's state can be saved for possible future recovery. The action of saving is called 'checking in'.
A workspace may contain both versionable and non-versionable nodes. A node is versionable if it has been assigned a mixin type mixin: versionable; otherwise, it is a non-versionable node.
A version exists as a part of a version history graph that describes the predecessor/successor relations among versions of a particular versionable nodes.

Software versioning is the process of assigning either unique names or version numbers to unique states of the software. Within a given version number category (major or minor, for example), these numbers are generally assigned by increasing order and correspond to new developments in the software.
At a fine-grained level, revision control is often used for keeping track of incrementally different versions of electronic information, whether or not this information is actually computer software.
WebDAV stands for Web-based Distributed Authoring and Versioning. It is a set of extensions to the Hypertext Transfer Protocol (HTTP) which allows users to collaboratively edit and manage files on remote servers.
The protocol was developed to make the Web a readable and writable medium. It provides functionality to create, change and move documents on a remote server (typically a web server or "web share"). This is useful for authoring the documents which a web server serves, among other things, but can also be used for general web-based file storage that can be accessed from anywhere.
A podcast is an audio file that you can download and listen to on your computer or a portable MP3 player such as an iPod™. The word itself comes from the combination of the words: iPod and broadcast.
The file plan is the primary records management planning document. Although file plans can differ across organizations, their typical functions are to:
Describe the kinds of items the organization acknowledges to be records.
Describe what broader category of records that the items belong to.
Indicate where records are stored.
Describe retention periods for records.
Delineate who is responsible for managing the various types of records.