Differences between revisions 1 and 25 (spanning 24 versions)
Revision 1 as of 2002-12-20 19:14:02
Size: 90
Editor: 213
Comment:
Revision 25 as of 2007-07-17 19:19:06
Size: 3768
Editor: ip59934a65
Comment: added: BAOW, Leonardo
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Inserisci una descrizione per ContentManagementSystems = Content Management Systems =
Line 3: Line 3:
dsfs A content management system (CMS) might be simply defined as a system which supports the publishing or sharing, editing or manipulation, searching and indexing, archival or versioning of content, frequently documents, typically using Web technologies. A more extensive definition can be found in the [http://en.wikipedia.org/wiki/Content_management_system Wikipedia topic entry].
Line 5: Line 5:
dsf
sd
fsd
f
dsfsd
In plainer terms, content management systems are the applications used to manage Web sites where the writers, editors and users are able to upload, edit and manage content without needing to know too many of the technical details about how the site actually works.

== Zope-based Solutions ==

The most established Python-based content management systems are those derived from ["Zope"], notably [http://www.plone.org Plone], [http://www.cps-project.org Nuxeo CPS] and [http://www.infrae.com/products/silva Silva]. These solutions have been used in large scale and high profile deployments over a number of years, and a range of organisations provide support and services for those solutions.

== Non-Zope Solutions ==

For those wanting non-Zope CMS solutions, there are a few options which may provide at least some of the features found in the more established solutions mentioned above, and the solutions mentioned below may be targeted more towards developers than individuals or organisations wishing to immediately deploy a complete and working solution.

 * [http://sourceforge.net/projects/peo/ BAOW] is a lightweight content management system based on SQL database (Firebird/InterBase, MySQL, PostgreSQL, SQLite). v1.1 released: 2005-07-07
 * [http://www.djangoproject.com/ Django] offers elementary support for content management (and was initially derived from the lower levels of a commercial content management system).
 * [http://www.ikaaro.org/itools itools] offers content management functionality.
 * [http://leonardo.pyworks.org/ Leonardo] extensible content management system, architected in a REST-like style. Initially focused on providing for personal websites with a password-protected wiki and blog (including Atom feed). It can be run as CGI and uses the filesystem as a database.
 * [http://payago.com/ Payago] is a lightweight website management system based on [http://nevow.com/ Nevow].
 * [http://www.pylucid.org PyLucid] is a lightweight CMS written in Python WSGI. No shell account is needed. To run !PyLucid you need a standard Web server with Python (at least v2.3), CGI and mySQLdb.
 * [http://orangoo.com/skeletonz/ Skeletonz] is simple, powerful, extensible, reliable. Has been in development since October 2005. Ajax based editor with spell checking & UTF-8 support. High performance: best result is around 600 request/sec. Open source, GNU GPL.
 * [http://cvs.sourceforge.net/viewcvs.py/webware-sandbox/Sandbox/fbar/teeny_tiny_cms/ teeny_tiny_cms] runs on ["Webware"] and uses SQLObject, SQLite and Docutils.

=== Wiki Solutions ===

Despite their simple beginnings, many wiki solutions offer many of the capabilities listed above. Numerous wiki projects have been written in Python. The following are the most widely deployed:

 * MoinMoin is the solution used to publish and manage the information on this page!
 * [http://trac.edgewall.org/ Trac] provides a wiki within a larger solution for the management of software projects and project information -- bug tracking, source browsing, and so on.
 * See a more complete list of wiki solutions on the PythonWikiEngines page.

== Editorial Notes ==

The above lists should be arranged in ascending alphabetical order - please respect this when adding new solutions. When specifying release dates please use the format YYYY-MM-DD.

Content Management Systems

A content management system (CMS) might be simply defined as a system which supports the publishing or sharing, editing or manipulation, searching and indexing, archival or versioning of content, frequently documents, typically using Web technologies. A more extensive definition can be found in the [http://en.wikipedia.org/wiki/Content_management_system Wikipedia topic entry].

In plainer terms, content management systems are the applications used to manage Web sites where the writers, editors and users are able to upload, edit and manage content without needing to know too many of the technical details about how the site actually works.

Zope-based Solutions

The most established Python-based content management systems are those derived from ["Zope"], notably [http://www.plone.org Plone], [http://www.cps-project.org Nuxeo CPS] and [http://www.infrae.com/products/silva Silva]. These solutions have been used in large scale and high profile deployments over a number of years, and a range of organisations provide support and services for those solutions.

Non-Zope Solutions

For those wanting non-Zope CMS solutions, there are a few options which may provide at least some of the features found in the more established solutions mentioned above, and the solutions mentioned below may be targeted more towards developers than individuals or organisations wishing to immediately deploy a complete and working solution.

Wiki Solutions

Despite their simple beginnings, many wiki solutions offer many of the capabilities listed above. Numerous wiki projects have been written in Python. The following are the most widely deployed:

  • MoinMoin is the solution used to publish and manage the information on this page!

  • [http://trac.edgewall.org/ Trac] provides a wiki within a larger solution for the management of software projects and project information -- bug tracking, source browsing, and so on.

  • See a more complete list of wiki solutions on the PythonWikiEngines page.

Editorial Notes

The above lists should be arranged in ascending alphabetical order - please respect this when adding new solutions. When specifying release dates please use the format YYYY-MM-DD.

ContentManagementSystems (last edited 2014-05-25 07:47:58 by SteveBreuning)

Unable to edit the page? See the FrontPage for instructions.