Archive for the ‘WCM’ Category

• BEdita

  Date: 2010.10.26 | Category: CMS, WCM | Response: 0

  [Translate]

  ---

  BEdita is an open source web development framework that features a Content Management System (CMS) out-of-the-box.

  Current version is 3.0.1, released on 12 January 2010 under Affero General Public License version 3.
  Current preview and “unstable” version is 3.1.beta, released on 9 July 2010 under the same GPL license.

  BEdita is built upon the PHP development framework CakePHP.

  Features

  BEdita is also a complete content management system, since it already comes with a multi-language back office application, able to manage several kinds of data: the CMS presents a number of modules, each related to a type of content. It is able to handle documents, multimedia objects and galleries, events, news, address books, blogs, bibliographies, newsletters and more out of the box.

  All this content is managed in multiple languages, geo-localized and organized through different strategies: hierarchic tree, custom categories and tags.

  Official web sites

  • BEdita official web site
  

• jAPS

  Date: 2010.07.30 | Category: WCM | Response: 1

  [Translate]

  ---

  jAPS 2.0 – java Agile Portal System is an Open Source, professional “Enterprise Accessible Information Platform” that makes easier aggregation, publishing, access, customization and integration of services, information, processes and resources, compatible with international standards like WCAG 2.0, Section 508 and PAS 78. jAPS 2.0 Platform provides performance, reliability and scalability features typical of enterprise software (“Enterprise”), allows users with disabilities to access and manage information and services (“Accessible“), seeks to simplify content management (“Information“) and it can be used as a framework (“Platform”) to build vertical applications based on contents (“Content Enabled Vertical Application”).

  jAPS & Technology

  jAPS 2.0 is entirely based on standard technologies developed on Java EE platform, XML and SOA architecture that provide support for the integration with other systems.

  Is jAPS a Content Management System?

  jAPS is more than a web content management system. It’s a platform that can integrate custom services, modules and other specific applications.

  The web content management system called jACMS (Java Agile CMS) is an integrated module compatble with accessibility requirements of W3C WCAG standards. It allows to manage the life cycle of contents and related resources (documents, images, etc.) and it’s also easy to use for disabled people.

  jAPS Features

  • provides a secure unified access to information, data and applications with single sign on capabilities (Single Point of Entry)
  • allows to share information and collaboration services (Collaboration)
  • allows users to choose contents and services (Personalization)
  • facilitate easy customization to meet specific needs (Flexibility)
  • simplify content management: workflow management, categorization, indexing and information search (Content Management)
  • allows to aggregate features of heterogeneous systems, data from other systems and CMS contents into new web components (showlets/portlets) as dashboard (Aggregation)
  • allows to integrate external services into a single platform (Integration)
  • provides extensible authentication and authorization features to control access to resources, information and functionalities (Permissioning)

  jAPS is available on Sourceforge since November 2005 and there is an active community. Companies, government, software developers, Universities, experts in accessibility are members of jAPS Community.

  

• dotCMS

  Date: 2010.07.26 | Category: CMS, WCM | Response: 0

  [Translate]

  ---

  dotCMS is a free software / open source web content management system (wCMS) for building/managing websites, content and content driven web applications. dotCMS includes features such as support for virtual hosting, WebDav (beta), structured content, clustering and can run on multiple databases PostgreSQL, MySQL, MSSQL and Oracle. It also includes standard wCMS features like page caching, templating, and a API. There are a number of features and modules in dotCMS, including RSS feeds, AJAX calendar, a reporting engine, news listing, blogs, forums, user tracking and tagging, built in search engine and language internationalization to name a few.

  History

  dotCMS was initially developed as a Java alternative to the PHP CMSes on the market, as well as to provide a counterpoint to high cost, enterprise applications. It is the result of over 5 years of development by dotMarketing, Inc, which also developed and released the open source project management tool dotProject, Both dotCMS and dotProject were conceived and originated by William Ezell. In order to achieve compliance with JSR-168 portlet specification dotCMS was built upon the Liferay portal, though has since forked Liferay at version 3.2.2. dotCMS 1.0 was initially open sourced and made available in 2005 under the dotMarketing Public License. In 2006, dotCMS released version 1.2 which included the structured content engine. In 2007 dotCMS released version 1.5, which included a new user interface and permissions. In October, 2007 dotCMS 1.5 was the runner up for Packt Publishing’s “Best New Open Source CMS” award, followed in 2008 by a second place finish for Packt’s “Best Other Open Source CMS (best non PHP CMS)”. dotCMS was runner-up in the 2009 Packt Publishing category, “Best Other Open Source CMS.”

  In April 2009 version 1.7 was released, introducing a plugin architecture, providing a wide range of extension points. A Windows installer to expedite the installation process was released October 2009.

  1.9 Update

  The upcoming 1.9 patch is a significant revision to the code base and will have a number of changes and improvements, including:

  • i18n compliance for the administration interface
  • Complete template redesign for the administration interface
  • Conversion to the Dojo Javascript framework for AJAX functions
  • Binary content fields for structures
  • Additional form structure and new form submission engine
  • Completely refactored permissions system

  Recently dotCMS announced its plan to integrate CMIS (Content Management Interoperability Services) into v1.9–making dotCMS the first WCMS to do so. dotCMS is an Oasis TC Member.

  Technologies

  dotCMS is a standards based CMS written in the Java programming language, and comes bundled with the Apache Tomcat Application Server. It is database agnostic and can run on PostgreSQL, MySQL, MSSQL or Oracle. It is capable of integrating with user’s authentication scheme’s, such as Active Directory or LDAP, and will support operation in a clustered or load balanced environment. It leverages a number of standards based open source projects such as:

  • Apache Struts Web Framework
  • Apache Lucene Search Engine
  • Apache Velocity Templating Language
  • Liferay Portal
  • EXT Javascript Framework
  • Apache Tomcat Application Server
  • OSCache distributed caching system
  • Hibernate Object Relational Mapping

  Structured Content

  The driving concept behind content stored within dotCMS is that it is addressed through a system of structures. Structures are administrated through a back end portlet where fields are assigned to them. Fields are named and given a content type and then ordered. Each structure can then be permissioned and used when creating content, and allows different types of content with consistent components to be referenced for display on the front end. A “web page content” structure could be assigned a title and body, for instance, while “events” have titles, dates, times, locations, descriptions, links, etc. Structures therefore allow the CMS to tailor itself to the content demands of the institution using it, because they can create and define structures that are specific to their needs. Those structures can then be created through relationships, allowing content from one structure to be associated content items in another. There is no limit to the number of structures one can use within dotCMS.

  

• DotNetNuke

  Date: 2010.06.18 | Category: WCM, blog | Response: 0

  [Translate]

  ---

  DotNetNuke is an open source platform for building web sites based on Microsoft .NET technology.

  It is written in VB.NET and distributed under both a Community Edition BSD-style license and a Professional Edition proprietary license. DotNetNuke’s content management system is extensible and customizable through the use of skins, modules, data providers, language packs and templates.

  DotNetNuke Community Edition

  DotNetNuke’s content management system allows non-technical users to create and edit content, and add custom features and personalize the site look and feel. It can be further expanded with addition of third party modules and tailored with custom graphics and layouts in the form of skins.

  The DotNetNuke Corporation provides an open source version of DotNetNuke called the Community Edition. It includes access to the source code of the framework and basic modules, and an MIT license allowing flexible modification and distribution rights. The Community Edition a popular web content management (WCM) system and application development framework for ASP.NET, with over 6,000,000 downloads and 400,000 production web sites as of September 2009.

  A narrative video overview of DotNetNuke called A Short Story has been created by Nik Kalyani and the Chicago DotNetNuke Users Group. It shows DotNetNuke from the perspective of developers, system administrators, business decision makers and end users, and is available on YouTube.

  Modules

  The default functionality of DotNetNuke can be expanded by adding third-party modules, either from an existing library of free and proprietary modules, or through in-house development of custom functionality. The DotNetNuke framework provides basic functionality such as security, user administration and content management, while modules are used to tailor the web site for specific deployment needs.

  A set of primary modules are included with the core DotNetNuke distribution. These modules provide the functionality required to create an e-commerce system, and intranet, a public web site or a custom web application. They are maintained by a volunteer team community on the DotNetNuke Community Forge.

  Further modules can be downloaded from Snowcovered, a marketplace of third-party DotNetNuke modules and skins. As of September 2009, over 6,000 extensions are available, including e-commerce systems, photo galleries, localization modules, blogs, forums, wiki, social networking functionality and others. Modules are available in both free and paid versions from the open source community and proprietary commercial DotNetNuke developers.

  A module can be uploaded and automatically installed on a DotNetNuke installation through the administration pages of DotNetNuke. Once a module is added by the administrator, it can be placed on any of the pages in the web site and custom access permission can be configured for it.

  Skins

  DotNetNuke has a skinning architecture which provides a separation between design and content, enabling a web designer to develop skins without requiring any specialist knowledge of development in ASP.NET: only knowledge of HTML and an understanding of how to prepare and package the skins themselves is required. Skins consist of basic HTML files with placeholders (tokens) for content, menus and other functionality, along with support files such as images, style sheets and JavaScript, packaged in a ZIP file.

  Upon Microsoft’s release of the .NET Framework version 2, Microsoft had included functionality known as master pages. The principal idea behind master pages was to encourage code recycling and consistent design and aesthetics throughout a site by creating a master page with placeholders, which at runtime would be compiled and replaced by content.

  Although this advancement was considered significant, DotNetNuke decided to keep its skinning engine, using the argument that to construct master pages, a web designer needed access to Microsoft’s Visual Studio, which would then put developer code at a risk (as master pages have the ability to contain VB.NET code). Bearing in mind that a significant proportion of web designers choose to use both Windows and Mac OS-based design software, DotNetNuke decided to retain the skinning engine to retain its open-source ideals and availability to the web design community.

  Like modules, compiled (“ZIPped”) skins can be uploaded and automatically installed through the administration pages. If the compiled skin does not contain an ASP.NET user control file, then the DotNetNuke skinning engine builds one based on various tokens included in the HTML file which refer to various sections, placeholders and/or modules of a DotNetNuke-produced page. A number of discussions on the DotNetNuke forums debate the differences between designing skins in “pure” HTML and Cascading Style Sheets, or creating skins in Visual Studio as ASP.NET user controls.

  Since version 4.4, skin developers have been able to specify skin-level DOCTYPEs to allow them to develop skins that follow accessibility and XHTML standards.

  Awards

  DotNetNuke has won awards, including

  • CRN Emerging Vendor – CRN Emerging Vendor 2009
  • asp.netPRO 2009 Reader’s Choice Award – Content Management System runner-up behind Microsoft Sharepoint Server 2007
  • Microsoft Canada Ignite IT Awards 2009 – Top 5 Developer Submissions Finalist
  • Visual Studio Magazine – Editor’s Choice Award 2007