Document Actions
Introduction
What is the aim of this tutorial?
This tutorial is devoted to content management with Kupu. It introduces the Kupu interface and explains how to insert images, how to create FAQ pages, and why to use ResolveUID. This tutorial is aimed to help a content manager to get acquainted with WYSIWYG editors in Plone.This tutorial is a part of Plone Book for Content Managers - a tutorial digest on the most recent issues. As this book is constantly expanding, you can monitor the renewals made to it subscribing to my blog.
In case any question concerning editing with Kupu arises during your work, something is not clear for you in any article of this tutorial, you have noticed any drawbacks or have suggestions about how to improve it, you are welcomed to contact Olha Pelishok.
If your questions and suggestions concern Kupu in general, contact the Plone General mailing list. Duncan Booth usually settles such issues. He has also done a tremendous amount of very high quality work about Kupu. Duncan Booth took over after Philipp von Weitershausen had done the initial Plone integration.
Getting back to the Kupu content editor, let's start with its general description.
What is Kupu?
Kupu is an open source client-side editor for Firefox, Netscape and Internet Explorer. Inspired by Maik Jablonski's Epoz editor, it was written by Paul Everitt, Guido Wesdorp and Philipp von Weitershausen to improve the JavaScript code and architecture, standards support, support for webservers other than Zope (which was the original target platform for Epoz), customization, and other issues.
Kupu's features:
- Kupu is easy to integrate into a variety of CMS.
- Kupu can be easily customized and extended.
- High-tech and up-to-date Kupu uses CSS in favor of HTML for layout and presentation.
