• Anonymous
  • Login
  • Register



OpenWebCMS - WebCMS for Domino

Owners Julian Buss Category
Content Management
Contributors - Platform
R 8.5.2
Downloads 2224Download latest release Last Release Feb 14, 2008
Rating
(2 ratings)
 Project Creation Oct 15, 2007
Status Not active Short URL Not defined
Description Full flavoured web content management system - flexible - very fast In Catalog
No


UPDATE August 2011: this project is not longer active and not longer supported by YouAtNotes. You may download and try it to learn about it's java based backend, but I encourage you to not use this project in production anymore. 

OUTDATED description of this project below: 

---

OpenWebCMS is an OpenSource Web Content Management System for Lotus Domino. It's based on the formerly commercial product "YouAtNotes CMS" from YouAtNotes GmbH, Germany. In 10/02 YouAtNotes decided to give this CMS free as OpenSource under the YouAtNotes OpenSource Licence, which is like the GPL.


Documentation can be found here: http://www.youatnotes.de/youatnotes/development/cms/wiki.nsf/pages/Home
Description in german can be found here: http://www.youatnotes.de/cms
Forum can be found here: https://www.youatnotes.de/web/youatnotes/forum.nsf/WebBoardMainActiveCategorized?OpenView&RestrictToCategory=OpenWebCMS


The OpenWebCMS is a complete solution for building dynamic Websites with Domino and to give users the chance to edit the content in simple Notes Richtext. It has loads of features and a sophisticated backend with caching which makes the system very fast.

Features:
General

* Full flavoured Web Content Management system for Lotus Domino. Edit content via Notes client, serve it to the web.
* Extremly flexible mechanism for implementing automatic navigation.
* Very fast due to sophisticated caching.
* Efficient and fast development of layout and functionality for web sites. Easy maintenance.
* Easy to use GUI for users.
* Own logging mechanism if you don't want to use HTTP logs.
* Prepared to custom extensions.

Backend

* Backend is implemented as java servlet and runs on the domino server.
* The backend does all the hard work and caches data (computed HTML stuff), so that the next access to the same kind of data is very fast.
* Backend can serve multiple CMS databases.
* Backend controls the creation of domino backend objects and makes sure that there is no waste of memory.
* Backend writes a log of it's activities and can be set to different log levels.
* Backend can write a log entry for every access to a CMS document from the web. The log entry contains clear text titles and not only cryptic IDs?.
* All logging runs in seperate threads on the server and does not slow down the site.
* Backend does maintenance tasks in a seperate thread.

Web development

* Content is structed in areas (categories). Areas can span multiple levels.
* All kind of automatic navigators can be developed. A navigator can display elements for CMS documents based on their area and level.
* You can display multiple navigators on one page.
* You can define navigators which display only documents of a certain level.
* Automatic expand/collapse functionality in navigators.
* Automatic handling of active/deactive elements in navigators.
* Automatic handling of navigator elements as text or image.
* Navigators can display the result of a full text search to display only documents of specific criterias.
* Template system: a content is assigned to a HTML template. In the HTML you define how fields of the content document should display in the web.
* Content documents are assigend to standard templates, but you can force using another template by an URL parameter.
* In a template you define HTML with embedded domino formulas (named "DML" here). With that you can easily create a very dynamic site.
* You can hold common used HTML/DML fragments as "component", which you can include in several templates.
* Templates for result of a full text search so that you can display search results as you like.
* Support for centrally stored stylesheets.
* Support for centrally stored JavaScript? code.
* Support for centrally stored file resources.
* ... and so much more not coming to my mind at this moment :-)

User GUI

* Users create content based on content types. In a content type you define all neccessary properties for content documents, so that the user does not need to care about that.
* Users create content with NotesRicht? text, but you can also create custom subforms so that the user works with custom fields.
* Optional version management with separation of published and work versions of a content.
* Automatic optimization for search engines - meta tags are create automatically out of the content, you can define standard keywords etc.
* You can define edit rights for each area so that one group of users only can edit content in one area and another group in another area.
* Buttons for write common needed HTML tags into the content field.
* Possibility to store files (images, PDFs?...) in a central place and link to them.
* Usage of central stored text blocks.



Projects can have short and readable URLs, e.g. http://mobilecontrols.openntf.org.

You can request a short URL to your project by sending a mail to support at openntf dot org. Put the word 'OpenNTF' somewhere in the subject.
Owners are the people with maximal rights. For example they can create releases and add more contributors.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter the contributors or owners here who you want to receive notifications and questions by email.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
In addition to the owners additional OpenNTF contributors have to be listed here. Contributors don't have the same access rights as owners, e.g. they cannot create releases.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter a short description of the project here (up to 100 characters).

The short description shows up in the project UI and in some of the views.
In this field you should enter a more detailed description of your project.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.
A Catalog Release is for projects that are production ready and that are end-user "install friendly".

This property describes whether any release of this project has been added to the catalog.

Learn more about the catalog.