Differences between revisions 3 and 4
Revision 3 as of 2007-07-07 22:33:52
Size: 1111
Editor: CameronLaird
Comment:
Revision 4 as of 2007-07-18 14:37:16
Size: 1356
Editor: houston
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
piece for people with '''big''' sites. piece for people with '''big''' sites. Notice that, among other
advantages, this facilitates separation of servers, so that
content delivery can be managed with an eye to security,
scalability, and availability,
while content management focuses on flexibility and functionality.

This is a tough one: while Entransit already has at least a couple of what look like home pages (see below), it deserves an explanation better suited to the context of the Python Wiki. Its ecological niche is a challenge to explain, though ...

Entransit is open-source software (exclusively? predominantly? This answer might change in 2007-2008). It was originally created to effect "content delivery" as a front end for ["Plone"] as a back-end "["content management system"]". This is a WebFrameworks piece for people with big sites. Notice that, among other advantages, this facilitates separation of servers, so that content delivery can be managed with an eye to security, scalability, and availability, while content management focuses on flexibility and functionality.

Entransit incorporates search technologies, or at least "hooks", and explicitly invites front-end development with Java, .NET, and PHP.

The [http://plone.org/products/entransit Plone site summarizes], "The Entransit Content Delivery System allows a hybrid approach to content management that creates an open source alternative to expensive mid-tier content management systems. . . ."

["Enfold Systems"] hosts [http://www.enfoldsystems.com/Products/Entransit the authoritative home page for Entransit] as one of its product offerings.

Entransit (last edited 2008-11-15 13:59:57 by localhost)

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