[Checkins] SVN: zope-story-website/trunk/src/ Integrated changes from branches/what_who_why_zope; had some trouble merging so some history lost
Brad Allen
brad at allendev.com
Sun Apr 5 00:38:27 EDT 2009
Log message for revision 98865:
Integrated changes from branches/what_who_why_zope; had some trouble merging so some history lost
Changed:
A zope-story-website/trunk/src/_static/basic.css
U zope-story-website/trunk/src/conf.py
U zope-story-website/trunk/src/index.rst
A zope-story-website/trunk/src/who_is_zope.rst
A zope-story-website/trunk/src/why_use_zope.rst
U zope-story-website/trunk/src/zope_history.rst
-=-
Added: zope-story-website/trunk/src/_static/basic.css
===================================================================
--- zope-story-website/trunk/src/_static/basic.css (rev 0)
+++ zope-story-website/trunk/src/_static/basic.css 2009-04-05 04:38:27 UTC (rev 98865)
@@ -0,0 +1,529 @@
+/**
+ * Sphinx stylesheet -- basic theme
+ * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ */
+
+/* -- main layout ----------------------------------------------------------- */
+
+div.documentwrapper {
+ float: left;
+ width: 100%;
+}
+
+div.bodywrapper {
+ margin: 0 0 0 0 /*230px*/;
+}
+
+div.clearer {
+ clear: both;
+}
+
+/* -- relbar ---------------------------------------------------------------- */
+
+div.related {
+ width: 100%;
+ font-size: 90%;
+}
+
+div.related h3 {
+ display: none;
+}
+
+div.related ul {
+ margin: 0;
+ padding: 0 0 0 10px;
+ list-style: none;
+}
+
+div.related li {
+ display: inline;
+}
+
+div.related li.right {
+ float: right;
+ margin-right: 5px;
+}
+
+/* -- sidebar --------------------------------------------------------------- */
+
+div.sphinxsidebarwrapper {
+ padding: 10px 5px 0 10px;
+}
+
+div.sphinxsidebar {
+ float: left;
+ width: 230px;
+ margin-left: -100%;
+ font-size: 90%;
+}
+
+div.sphinxsidebar ul {
+ list-style: none;
+}
+
+div.sphinxsidebar ul ul,
+div.sphinxsidebar ul.want-points {
+ margin-left: 20px;
+ list-style: square;
+}
+
+div.sphinxsidebar ul ul {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+
+div.sphinxsidebar form {
+ margin-top: 10px;
+}
+
+div.sphinxsidebar input {
+ border: 1px solid #98dbcc;
+ font-family: sans-serif;
+ font-size: 1em;
+}
+
+img {
+ border: 0;
+}
+
+/* -- search page ----------------------------------------------------------- */
+
+ul.search {
+ margin: 10px 0 0 20px;
+ padding: 0;
+}
+
+ul.search li {
+ padding: 5px 0 5px 20px;
+ background-image: url(file.png);
+ background-repeat: no-repeat;
+ background-position: 0 7px;
+}
+
+ul.search li a {
+ font-weight: bold;
+}
+
+ul.search li div.context {
+ color: #888;
+ margin: 2px 0 0 30px;
+ text-align: left;
+}
+
+ul.keywordmatches li.goodmatch a {
+ font-weight: bold;
+}
+
+/* -- index page ------------------------------------------------------------ */
+
+table.contentstable {
+ width: 90%;
+}
+
+table.contentstable p.biglink {
+ line-height: 150%;
+}
+
+a.biglink {
+ font-size: 1.3em;
+}
+
+span.linkdescr {
+ font-style: italic;
+ padding-top: 5px;
+ font-size: 90%;
+}
+
+/* -- general index --------------------------------------------------------- */
+
+table.indextable td {
+ text-align: left;
+ vertical-align: top;
+}
+
+table.indextable dl, table.indextable dd {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+
+table.indextable tr.pcap {
+ height: 10px;
+}
+
+table.indextable tr.cap {
+ margin-top: 10px;
+ background-color: #f2f2f2;
+}
+
+img.toggler {
+ margin-right: 3px;
+ margin-top: 3px;
+ cursor: pointer;
+}
+
+/* -- general body styles --------------------------------------------------- */
+
+a.headerlink {
+ visibility: hidden;
+}
+
+h1:hover > a.headerlink,
+h2:hover > a.headerlink,
+h3:hover > a.headerlink,
+h4:hover > a.headerlink,
+h5:hover > a.headerlink,
+h6:hover > a.headerlink,
+dt:hover > a.headerlink {
+ visibility: visible;
+}
+
+div.body p.caption {
+ text-align: inherit;
+}
+
+div.body td {
+ text-align: left;
+}
+
+.field-list ul {
+ padding-left: 1em;
+}
+
+.first {
+ margin-top: 0 !important;
+}
+
+p.rubric {
+ margin-top: 30px;
+ font-weight: bold;
+}
+
+/* -- sidebars -------------------------------------------------------------- */
+
+div.sidebar {
+ margin: 0 0 0.5em 1em;
+ border: 1px solid #ddb;
+ padding: 7px 7px 0 7px;
+ background-color: #ffe;
+ width: 40%;
+ float: right;
+}
+
+p.sidebar-title {
+ font-weight: bold;
+}
+
+/* -- topics ---------------------------------------------------------------- */
+
+div.topic {
+ border: 1px solid #ccc;
+ padding: 7px 7px 0 7px;
+ margin: 10px 0 10px 0;
+}
+
+p.topic-title {
+ font-size: 1.1em;
+ font-weight: bold;
+ margin-top: 10px;
+}
+
+/* -- admonitions ----------------------------------------------------------- */
+
+div.admonition {
+ margin-top: 10px;
+ margin-bottom: 10px;
+ padding: 7px;
+}
+
+div.admonition dt {
+ font-weight: bold;
+}
+
+div.admonition dl {
+ margin-bottom: 0;
+}
+
+p.admonition-title {
+ margin: 0px 10px 5px 0px;
+ font-weight: bold;
+}
+
+div.body p.centered {
+ text-align: center;
+ margin-top: 25px;
+}
+
+/* -- tables ---------------------------------------------------------------- */
+
+table.docutils {
+ border: 0;
+ border-collapse: collapse;
+}
+
+table.docutils td, table.docutils th {
+ padding: 1px 8px 1px 0;
+ border-top: 0;
+ border-left: 0;
+ border-right: 0;
+ border-bottom: 1px solid #aaa;
+}
+
+table.field-list td, table.field-list th {
+ border: 0 !important;
+}
+
+table.footnote td, table.footnote th {
+ border: 0 !important;
+}
+
+th {
+ text-align: left;
+ padding-right: 5px;
+}
+
+/* -- other body styles ----------------------------------------------------- */
+
+dl {
+ margin-bottom: 15px;
+}
+
+dd p {
+ margin-top: 0px;
+}
+
+dd ul, dd table {
+ margin-bottom: 10px;
+}
+
+dd {
+ margin-top: 3px;
+ margin-bottom: 10px;
+ margin-left: 30px;
+}
+
+dt:target, .highlight {
+ background-color: #fbe54e;
+}
+
+dl.glossary dt {
+ font-weight: bold;
+ font-size: 1.1em;
+}
+
+.field-list ul {
+ margin: 0;
+ padding-left: 1em;
+}
+
+.field-list p {
+ margin: 0;
+}
+
+.refcount {
+ color: #060;
+}
+
+.optional {
+ font-size: 1.3em;
+}
+
+.versionmodified {
+ font-style: italic;
+}
+
+.system-message {
+ background-color: #fda;
+ padding: 5px;
+ border: 3px solid red;
+}
+
+.footnote:target {
+ background-color: #ffa
+}
+
+/* -- code displays --------------------------------------------------------- */
+
+pre {
+ overflow: auto;
+}
+
+td.linenos pre {
+ padding: 5px 0px;
+ border: 0;
+ background-color: transparent;
+ color: #aaa;
+}
+
+table.highlighttable {
+ margin-left: 0.5em;
+}
+
+table.highlighttable td {
+ padding: 0 0.5em 0 0.5em;
+}
+
+tt.descname {
+ background-color: transparent;
+ font-weight: bold;
+ font-size: 1.2em;
+}
+
+tt.descclassname {
+ background-color: transparent;
+}
+
+tt.xref, a tt {
+ background-color: transparent;
+ font-weight: bold;
+}
+
+h1 tt, h2 tt, h3 tt, h4 tt, h5 tt, h6 tt {
+ background-color: transparent;
+}
+
+/* -- math display ---------------------------------------------------------- */
+
+img.math {
+ vertical-align: middle;
+}
+
+div.math p {
+ text-align: center;
+}
+
+span.eqno {
+ float: right;
+}
+
+/* -- printout stylesheet --------------------------------------------------- */
+
+ at media print {
+ div.document,
+ div.documentwrapper,
+ div.bodywrapper {
+ margin: 0;
+ width: 100%;
+ }
+
+ div.sphinxsidebar,
+ div.related,
+ div.footer,
+ #top-link {
+ display: none;
+ }
+}
+
+.leftcol {
+ float: left;
+ width: 48%;
+ background-color: lightgreen;
+ padding: 10px 10px 10px 10px;
+}
+
+.rightcol {
+ float: right;
+ width: 48%;
+ background-color: lightblue;
+ padding: 10px 10px 10px 10px;
+}
+
+.leftcolofthree {
+ position: absolute;
+ top: 40px;
+ left: 1%;
+ width: 30%;
+ background-color: lightgreen;
+ padding: 10px 10px 10px 10px;
+}
+
+.middlecolofthree {
+ position: absolute;
+ top: 40px;
+ left: 34%;
+ width: 30%;
+ background-color: lightblue;
+ padding: 10px 10px 10px 10px;
+}
+
+.rightcolofthree {
+ position: absolute;
+ top: 40px;
+ left: 67%;
+ width: 30%;
+ background-color: lightgrey;
+ padding: 10px 10px 10px 10px;
+}
+
+.header {
+ font-size: 200%;
+}
+
+.zsection {
+ font-size: 150%;
+ color: black;
+ font-weight: bold;
+}
+
+.frameworks {
+ background-color: lightyellow;
+ padding: 4px 20px 4px 20px;
+ margin: 0 0 4px 0;
+
+ -moz-border-radius: 5px;
+ -webkit-border-radius: 5px;
+ border: 2px solid #878DDB;
+}
+
+.framework {
+ border: 4px solid orange;
+ padding: 2px 2px 2px 2px;
+ margin: 2px 2px 2px 2px;
+}
+
+.frameworks img {
+ float: left;
+}
+
+.applications {
+ background-color: lightpurple;
+ padding: 4px 20px 4px 20px;
+ margin: 0 0 4px 0;
+
+ -moz-border-radius: 5px;
+ -webkit-border-radius: 5px;
+ border: 2px solid #878DDB;
+}
+
+.application {
+ border: 4px solid purple;
+ padding: 2px 2px 2px 2px;
+ margin: 2px 2px 2px 2px;
+}
+
+.applications img {
+ float: left;
+}
+
+.composeyourown {
+ background-color: lightpurple;
+ padding: 4px 20px 4px 20px;
+ margin: 0 0 4px 0;
+
+ -moz-border-radius: 5px;
+ -webkit-border-radius: 5px;
+ border: 2px solid #878DDB;
+}
+
+.menuacross {
+ background-color: violet;
+ border: 1px solid black;
+}
+
+.menuacross li {
+ display: inline;
+ list-style-type: none;
+ padding-right: 20px;
+ font-size: 150%;
+ color: black;
+ width: 100%;
+}
Modified: zope-story-website/trunk/src/conf.py
===================================================================
--- zope-story-website/trunk/src/conf.py 2009-04-05 04:29:56 UTC (rev 98864)
+++ zope-story-website/trunk/src/conf.py 2009-04-05 04:38:27 UTC (rev 98865)
@@ -91,7 +91,7 @@
# The theme to use for HTML and HTML Help pages. Major themes that come with
# Sphinx are currently 'default' and 'sphinxdoc'.
-html_theme = 'default'
+html_theme = 'zopestory'
# Theme options are theme-specific and customize the look and feel of a theme
# further. For a list of options available for each theme, see the
@@ -99,7 +99,7 @@
#html_theme_options = {}
# Add any paths that contain custom themes here, relative to this directory.
-#html_theme_path = []
+html_theme_path = ['_themes']
# The name for this set of Sphinx documents. If None, it defaults to
# "<project> v<release> documentation".
@@ -131,7 +131,8 @@
#html_use_smartypants = True
# Custom sidebar templates, maps document names to template names.
-#html_sidebars = {}
+html_sidebars = {
+ 'index': 'nosidebar'}
# Additional templates that should be rendered to pages, maps page names to
# template names.
Modified: zope-story-website/trunk/src/index.rst
===================================================================
--- zope-story-website/trunk/src/index.rst 2009-04-05 04:29:56 UTC (rev 98864)
+++ zope-story-website/trunk/src/index.rst 2009-04-05 04:38:27 UTC (rev 98865)
@@ -1,144 +1,179 @@
-.. \ image:: _static/bg.png
-We are devoted to solutions to the perennial problems encountered when building
-complex, scalable web applications. We offer tools for all, from small
-nonprofits to large enterprise systems and high traffic public web applications.
+.. role:: header
+.. role:: zsection
-Frameworks
-==========
+.. container::
+ :class: menuacross
-The following are notable frameworks which users are adivsed to look at if
-they are looking at entering the world of Zope.
+ + `What is Zope? <index.html>`_
+ + `Who is Zope? <who_is_zope.html>`_
+ + `Why Zope? <why_use_zope.html>`_
-.. raw:: html
+.. container::
+ :class: LeftCol
- <div align="center">
- <table width="80%">
- <tr>
- <td align="center" valign="top">
- <img src="_static/grok_logo.png"
- href="http://grok.zope.org" alt=""
- width="200" height="50" align="center"></img><BR>
- <a href="http://grok.zope.org">Grok</a>
- a Python web framework aimed at making
- the full power of the Zope Framework accessible to any
- Python developer.
- </td>
- <td align="center" valign="top">
- <img src="_static/repoze_logo.gif"
- href="http://repoze.org/" alt=""
- width="152" height="50" align="center"></img><BR>
- <a href="http://repoze.org">Repoze,</a>
- a web framework toolkit integrating WSGI middleware with Zope.
- </td>
- <td align="center" valign="top">
- <img src="_static/zope2_logo.png"
- href="http://repoze.org/" alt=""
- width="129" height="50" align="center"></img><BR>
- <a href="http://zope2.zope.org">Zope 2,</a>
- a mature application server which
- has thrived in enterprise production systems for nearly 10
- years.
- </td>
- </tr>
- </table>
- </div>
+ .. rubric:: Zope is a Community
-Applications
-============
+ Hundreds of companies and thousands of developers devoted to solutions to
+ the perennial problems of building complex, scalable web applications.
+ `More... <who_is_zope.html>`__
-Several applications are built atop the Zope Framework, providing rich user
-experiences.
+ .. rubric:: Zope is Open Source
+ All Zope libraries, frameworks, and applications managed by the `Zope
+ Foundation`_ are licensed under the OSS-Certified `Zope Public License`_.
+ This BSD-style license allows use in both open source projects and closed
+ proprietary product offerings.
-.. raw:: html
+ .. rubric:: Zope is a Broad Software Technology
- <div align="center">
- <table width="80%">
- <tr>
- <td align="center" valign="top">
- <img src="_static/plone_logo.png"
- href="http://www.plone.org" alt=""
- width="193" height="50" align="center"></img><BR>
- <a href="http://www.plone.org">Plone</a>
- A powerful, flexible Content Management solution that is easy to
- install, use and extend.
- </td>
- <td align="center" valign="top">
- <img src="_static/schooltool_logo.png"
- href="http://www.schooltool.org/" alt=""
- width="174" height="50" align="center"></img><BR>
- <a href="http://www.schooltool.org">Schooltool,</a>
- a project to develop a common global school
- administration infrastructure that is freely available under an
- Open Source license.
- </td>
- <td align="center" valign="top">
- <img src="_static/launchpad_logo.png"
- href="http://launchpad.net" alt=""
- width="232" height="50" align="center"></img><BR>
- <a href="http://launchpad.net">Launchpad,</a>
- a web application and web site supporting software development,
- particularly that of free software. Launchpad is developed and maintained by
- Canonical Ltd.
- </td>
- </tr>
- </table>
- </div>
+ The base `Zope Framework`_ powers web development frameworks, web
+ application servers, content management systems, and many other software
+ components.
+ .. rubric:: Zope is Mature
-Compose Your Own
-================
+ Zope's robust technologies are born of 10 years of hard-won real world
+ experience in building production web applications for every level
+ of organization, ranging from small nonprofits to large enterprise systems
+ and high traffic public web applications. `More... <why_use_zope.html>`__
-To compose your own application or framwork from scratch, or see how the
-packages within the Zope Framework can work for you, see more information
-below.
+ .. rubric:: Zope is Python-based
-* `Zope 2 Application Server`_, a mature application server which
- has thrived in enterprise production systems for nearly 10 years.
+ Zope is written in `Python`_, a highly-productive, object-oriented
+ programming language with a strong emphasis on clear, elegant,
+ manageable code.
-* `Zope Framework Wiki`_, a place where more information about the Zope
- framwork can be found.
+ .. rubric:: Zope is Secure
+
+ The Zope Framework offers significant security advantages in the form of a
+ fine-grained and highly manageable infrastructure, including support for
+ pluggable authentication and permission-based security policies for object
+ publishing, down to the level of methods and attributes. `More...
+ <why_use_zope.html>`__
+
-This variety of open source and commercial applications built from
-Zope Framework demonstrates a community with years of expertise solving
-a wide range of problems. A deeper inspection of the technology reveals
-powerful tools for managing complexity by fully leveraging the best
-dynamic features of the Python programming language.
+.. container::
+ :class: RightCol
-Organizational Support
-======================
+ .. container::
+ :class: frameworks
-Any large open source community needs support infrastructure and
-shepherding of intellectual property. For years this was handled by
-Zope Corporation, but now those responsibilities have transitioned to
-the `Zope Foundation`_ (founded in 2006).
+ :zsection:`Web Frameworks Built with Zope`
+
+ .. container::
+ :class: framework
+ |Grok|_
-Python Community Cross-Pollination
-===================================
+ Grok is aimed at making the full power of the Zope Framework accessible
+ to any Python developer.
-Zope software components are also deployed in the wider Python community; for
-example:
+ .. container::
+ :class: framework
-* `Twisted`_, an asynchronous network server written in Python
- utilizes *zope.interface*. Some Zope projects come bundled with
- Twisted to provide Zope with a powerful multi-protocol network layer.
-
-* `TurboGears`_, a Python web framework which utilizes zope.interface
- as well as Zope's transaction library.
-
-* `buildout`_, originally developed at Zope Corporation, has gained traction outside the
- Zope Community as a Python-based build system for creating, assembling and
- deploying applications from multiple components.
+ |Repoze|_
-.. _Zope 2 Application Server: http://zope2.zopyx.de/
-.. _Zope Framework Wiki: http://wiki.zope.org/zope3/Zope3Wiki/
-.. _Plone: http://plone.org
-.. _BFG: http://static.repoze.org/bfgdocs/
-.. _Twisted: http://twistedmatrix.com/trac/
-.. _Grok: http://grok.zope.org
-.. _Zope Foundation: http://foundation.zope.org/about
-.. _Turbogears: http://turbogears.org/
-.. _buildout: http://buildout.org
-.. _Schooltool: http://www.schooltool.org/
-.. _Launchpad: http://launchpad.net
+ Repoze, a toolkit for integrating WSGI middleware with Zope.
+ In addition, a new web framework called Repoz.BFG has spun
+ out of the Repoze project.
+
+ .. container::
+ :class: framework
+
+ |Zope 2|_
+
+ Zope 2 is a mature application server which has thrived in enterprise
+ production systems for nearly 10 years. The "granddaddy of Python
+ web frameworks" is alive and kicking, re-energized by the
+ regular injection of new technologies such as `Zope Framework`_,
+ `Twisted`_, and other `Python`_ community innovations.
+
+
+
+ .. container::
+ :class: applications
+
+ :zsection:`A Few Example Applications Built with Zope`
+
+ .. container::
+ :class: application
+
+ |Plone|_
+
+ Plone is a powerful, flexible Content Management solution that is
+ easy to install, use and extend.
+
+ .. container::
+ :class: application
+
+ |Schooltool|_
+
+ a project to develop a common global school administration
+ infrastructure that is freely available under an Open Source license.
+
+ .. container::
+ :class: application
+
+ |Launchpad|_
+
+ Both an application and a web site supporting software development,
+ particularly that of free software, `Launchpad`_ is developed and
+ maintained by `Cannonical Ltd`_.
+
+
+ .. container::
+ :class: composeyourown
+
+ :zsection:`Compose Your Own`
+
+ To compose your own application or framework from scratch, or see how the
+ packages within the Zope Framework can work for you, see more information
+ below.
+
+ * `Zope 2 Application Server`_, a mature application server which has
+ thrived in enterprise production systems for nearly 10 years.
+
+ * `Zope Framework`_, a place where more information about the Zope
+ framework can be found.
+
+ This variety of open source and commercial applications built from Zope
+ Framework demonstrates a community with years of expertise solving a wide
+ range of problems. A deeper inspection of the technology reveals powerful
+ tools for managing complexity by fully leveraging the best dynamic features
+ of the Python programming language.
+
+.. raw:: html
+
+ <br clear="all" />
+
+
+
+.. |Grok| image:: _static/grok_logo.png
+.. _`Grok`: http://grok.zope.org
+
+.. |Repoze| image:: _static/repoze_logo.gif
+.. _`Repoze`: http://static.repoze.org/bfgdocs/
+
+.. |Zope 2| image:: _static/zope2_logo.png
+.. _`Zope 2`: http://zope2.zopyx.de/
+
+.. |Plone| image:: _static/plone_logo.png
+.. _`Plone`: http://plone.org
+
+.. |Schooltool| image:: _static/schooltool_logo.png
+.. _`Schooltool`: http://www.schooltool.org/
+
+.. |Launchpad| image:: _static/launchpad_logo.png
+.. _`Launchpad`: http://launchpad.net
+
+
+.. _`Zope 2 Application Server`: http://zope2.zopyx.de/
+.. _`Zope Framework`: http://docs.zope.org/zopeframework/
+.. _`BFG`: http://static.repoze.org/bfgdocs/
+.. _`Twisted`: http://twistedmatrix.com/trac/
+.. _`Zope Foundation`: http://foundation.zope.org/about
+.. _`Turbogears`: http://turbogears.org/
+.. _`buildout`: http://buildout.org
+.. _`Zope Public License`: http://www.zope.org/Resources/License/
+.. _`Python`: http://www.python.org/
+.. _`Cannonical Ltd`: http://www.canonical.com/
Added: zope-story-website/trunk/src/who_is_zope.rst
===================================================================
--- zope-story-website/trunk/src/who_is_zope.rst (rev 0)
+++ zope-story-website/trunk/src/who_is_zope.rst 2009-04-05 04:38:27 UTC (rev 98865)
@@ -0,0 +1,121 @@
+.. role:: header
+.. role:: zsection
+
+.. container::
+ :class: menuacross
+
+ + `What is Zope? <index.html>`_
+ + `Who is Zope? <who_is_zope.html>`_
+ + `Why Zope? <why_use_zope.html>`_
+
+
+.. container::
+ :class: LeftColOfThree
+
+ :header:`Community`
+
+ .. rubric:: Zope is an Open Source Community
+
+ Hundreds of companies and thousands of developers participate in the Zope
+ Community. A liberal BSD-style license called ZPL enables the Zope
+ Framework projects to freely intermingle code and ideas.
+
+ .. rubric:: Zope Community Links
+
+ + Zope Framework
+ + `Plone`_
+ + `Grok Community`_
+ + Repoze
+ + Repoze.BFG
+ + Zope 2 community (mailing lists, irc, etc.)
+ + `Planet Zope <http://planet.zope.org/>`_
+ + Central index of `Zope-related mailing lists`
+
+
+ .. rubric:: Zope Community Intersections
+
+ + `Python`_ has a substantial worldwide open source `community
+ <http://www.python.org/>`_
+ + `Twisted`_, an asynchronous network server written in Python
+ utilizes *zope.interface*. Some Zope projects come bundled with
+ Twisted to provide Zope with a powerful multi-protocol network layer.
+ + `TurboGears`_, a Python web framework which utilizes zope.interface
+ as well as Zope's transaction library.
+ + Pylons
+ + `buildout`_, originally developed at Zope Corporation, has gained traction outside the
+ Zope Community as a Python-based build system for creating, assembling and
+ deploying applications from multiple components.
+ + `Launchpad`_ hosts many software projects, including several involving
+ Zope, and is itself built `Zope Framework`_.
+
+
+.. container::
+ :class: MiddleColOfThree
+
+ :header:`Business`
+
+ .. rubric:: Business
+
+ The `Zope Foundation`_ takes care of business, shepherding Zope's
+ intellectual property and providing the server infrastructure needed to
+ support community projects.
+
+ Professional support and training for Zope solutions can be obtained from
+ companies such as `Zope Corporation`_ (the originator of Zope) and other
+ `Zope Solution Providers`_. In addition, the various Zope community sites
+ are good places to check for consultants and potential hires.
+
+.. container::
+ :class: RightColOfThree
+
+ :header:`History`
+
+ .. rubric:: A Brief History of Zope
+
+ The beginning of Zope's story goes something like this, in 1996, Jim
+ Fulton (CTO of Zope Corporation) was drafted to teach a class on common
+ gateway interface (CGI) programming, despite not knowing very much about
+ the subject. CGI programming is a commonly-used web development model
+ that allows developers to construct dynamic websites. On his way to the
+ class, Jim studied all the existing documentation on CGI. On the way back,
+ Jim considered what he didn't like about traditional, CGI-based
+ programming environments. From these initial musings, the core of Zope was
+ written while flying back from the CGI class.
+
+ Zope Corporation (then known as Digital Creations) went on to release
+ three open-source software packages to support web publishing: Bobo,
+ Document Template, and BoboPOS. These packages were written in a language
+ called Python, and provided a web publishing facility, text templating,
+ and an object database, respectively. Digital Creations developed a
+ commercial application server based on their three opensource
+ components. This product was called Principia. In November of 1998,
+ investor Hadar Pedhazur convinced Digital Creations to open source
+ Principia. These packages evolved into what are now the core components of
+ Zope 2.
+
+ In 2001, the Zope community began working on a component architecture for
+ Zope, but after several years they ended up with something much more:
+ Zope 3. While Zope 2 was powerful and popular, Zope 3 was designed to
+ bring web application development to the next level.
+
+ Source: The Zope 3 Book
+
+.. _`Zope Foundation`: http://foundation.zope.org/
+.. _`Zope 2 Application Server`: http://zope2.zopyx.de/
+.. _`Plone`: http://plone.org
+.. _`Grok`: http://grok.zope.org
+.. _`Grok Community`: http://grok.zope.org/community
+.. _`Zope Framework`: http://docs.zope.org/zopeframework/
+.. _`BFG`: http://static.repoze.org/bfgdocs/
+.. _`Twisted`: http://twistedmatrix.com/trac/
+.. _`Turbogears`: http://turbogears.org/
+.. _`buildout`: http://buildout.org
+.. _`Zope Public License`: http://www.zope.org/Resources/License/
+.. _`Python`: http://www.python.org/
+.. _`Launchpad`: http://launchpad.net
+.. _`Zope User Groups`: http://www.zope.org/Resources/UserGroups
+.. _`Zope-related mailing lists`: http://www.zope.org/Resources/MailingLists
+.. _`Zope Solution Providers`: http://www.zope.org/Resources/ZSP/
+.. _`Zope Corporation`: http://www.zope.com/
+.. _`Zope Solution Providers`: http://www.zope.org/Resources/ZSP/
+.. _`Launchpad`: http://launchpad.net
Added: zope-story-website/trunk/src/why_use_zope.rst
===================================================================
--- zope-story-website/trunk/src/why_use_zope.rst (rev 0)
+++ zope-story-website/trunk/src/why_use_zope.rst 2009-04-05 04:38:27 UTC (rev 98865)
@@ -0,0 +1,157 @@
+.. role:: header
+.. role:: zsection
+
+.. container::
+ :class: menuacross
+
+ + `What is Zope? <index.html>`_
+ + `Who is Zope? <who_is_zope.html>`_
+ + `Why Zope? <why_use_zope.html>`_
+
+
+Why Use Zope?
+=============
+
+Zope applications, libraries, and frameworks are suited for different purposes
+and environments; but most share common advantages:
+
+Zope is Mature
+--------------
+
+Zope's robust technologies are born of 10 years of hard-won real world
+experience in building production web applications for every level of
+organization, ranging from small nonprofits to large enterprise systems and
+high traffic public web applications.
+
+Zope's groundbreaking innovations over the years led the way in demonstrating
+the practicality of powerful software patterns, including object databases,
+object publishing, and component architecture.
+
+All the applications built using the Zope Framework benefit from this
+maturity, For example, the older projects, the Zope 2 app server as well as
+Plone, both increasingly make use of the newest Zope library versions while
+still maintaining the feature set that makes it useful in heavy production
+settings.
+
+Meanwhile, younger Zope web frameworks such as Grok and Repoze.BFG, leverage
+the mature Zope Framework libraries to bring new ideas to web development.
+
+Designed for Automated Testing
+------------------------------
+
+All the major Zope frameworks and libraries are built around a culture of
+automated testing.
+
+Scalable Performance
+--------------------
+
+Applications built using the Zope Object Database can benefit from ZEO
+Clustering, which allow multiple applications to share a single object
+database.
+
+Persistence Options
+-------------------
+
+Zope applications traditionally benefit from the use of a mature
+high-performance transactional object database called ZODB, which increases
+developer productivity by avoiding the management overhead of a relational
+database layer. This benefit multiplies when combined with Zope schema classes
+to marry content objects and metadata with web forms.
+
+However, relational databases (RDBMs) are also a popular persistence option
+for Zope applications, and good options exist for using object relational
+mappers such as SQLAlchemy and Storm.
+
+See also:
+ + `ZODB in Python Package Index`_
+ + `ZODB/ZEO Programming Guide`_
+ + `ZODB vs Relational Database: a simple benchmark`_
+ + `SQLAlchemy`_
+ + `Storm`_
+
+Zope Component Architecture (ZCA)
+---------------------------------
+
+One of the lessons learned over the years was the need for a component
+architecture; using object composition instead of object inheritance avoids
+tight coupling between application parts so that components can be swapped
+without causing breakage. The Zope Component Architecture provides and elegant
+solution which helps manage complexity and encourage component reusability.
+
+See also:
+ + `A Comprehensive Guide to Zope Component Architecture`_
+ + `Zope Component Architecture Overview`_
+ + `Grok Explains Zope Component Architecture`_
+
+Security
+-------------------
+
+The `Zope Framework`_ offers significant security advantages in the form of
+a fine-grained and highly manageable infrastructure, including support
+for pluggable authentication and permission-based security policies for object
+publishing, down to the level of methods and attributes.
+
+By default, nothing is published unless an explicit security declaration is
+attached either within application code or within configuration.
+
+For applications needing less security and more simplicity, Zope Framework
+security can be relaxed to allow convenient, free-form web object publishing.
+
+When it comes to security, one size does NOT fit all.
+
+See also:
+ + `Pluggable Authenication for Plone and Zope 2 <http://plone.org/documentation/manual/pas-reference-manual/referencemanual-all-pages>`__
+
+
+MetaData and Dublin Core
+-------------------------
+
+Zope supports attaching metadata for application content objects, adhering
+to the `Dublin Core <http://dublincore.org/>`_ metadata standard.
+
+
+I18n and L10n Support
+-------------------------------------------------------------
+
+`Zope Framework`_ supports a manageable approach to internationalization and
+localization, to make Zope applications easily translatable.
+
+
+Twisted Server Integration
+---------------------------
+
+While Zope does have a robust built-in HTTP server for publishing objects to
+the web, it also comes bundled with the powerful `Twisted`_ server, an
+"event-driven networking engine" designed to support not only HTTP but
+many other network protocols in a concurrently asynchronous fashion.
+
+
+WSGI Integration Options
+---------------------------
+
+Zope plays well with `WSGI`_ HTTP pipelines, enabling layering
+of `WSGI "middleware"`_ applications between the web server and the main
+"endware" application. Zope applications can play the role of either
+WSGI middleware or endware.
+
+See also:
+ + `Repoze: Integrating Zope Into a WSGI World`_
+ + `PasteDeploy`_
+
+
+
+
+.. _`Zope Framework`: http://docs.zope.org/zopeframework/
+.. _`WSGI`: http://wsgi.org/wsgi/
+.. _`WSGI "middleware"`: http://wsgi.org/wsgi/Middleware_and_Utilities
+.. _`Twisted`: http://twistedmatrix.com/trac/wiki
+.. _`PasteDeploy`: http://docs.zope.org/zope3/Code/zope/publisher/paste.txt/index.html
+.. _`Repoze: Integrating Zope Into a WSGI World`: http://repoze.org/about.html
+.. _`ZODB vs Relational Database: a simple benchmark`: http://pyinsci.blogspot.com/2007/09/zodb-vs-relational-database-simple.html
+.. _`ZODB/ZEO Programming Guide`: http://wiki.zope.org/ZODB/guide/index.html
+.. _`ZODB in Python Package Index`: http://pypi.python.org/pypi/ZODB3
+.. _`SQLAlchemy`: http://www.sqlalchemy.org/
+.. _`Storm`: https://storm.canonical.com/
+.. _`A Comprehensive Guide to Zope Component Architecture`: http://muthukadan.net/docs/zca.html
+.. _`Zope Component Architecture Overview`: http://wiki.zope.org/zope3/ComponentArchitectureOverview
+.. _`Grok Explains Zope Component Architecture`: http://grok.zope.org/about/component-architecture
\ No newline at end of file
Modified: zope-story-website/trunk/src/zope_history.rst
===================================================================
--- zope-story-website/trunk/src/zope_history.rst 2009-04-05 04:29:56 UTC (rev 98864)
+++ zope-story-website/trunk/src/zope_history.rst 2009-04-05 04:38:27 UTC (rev 98865)
@@ -1,29 +1,29 @@
-
A Brief History of Zope
=======================
-The beginning of Zope’s story goes something like this, in 1996, Jim Fulton
-(CTO of Zope Corporation) was drafted to teach a class on common gateway
+The beginning of Zope's story goes something like this, in 1996, Jim Fulton
+(CTO of Zope Corporation) was drafted to teach a class on common gateway
interface (CGI) programming, despite not knowing very much about the subject.
-CGI programming is a commonly-used web development model that allows developers
-to construct dynamic websites. On his way to the class, Jim studied all the
-existing documentation on CGI. On the way back, Jim considered what he didn’t
-like about traditional, CGI-based programming environments. From these initial
-musings, the core of Zope was written while flying back from the CGI class.
+CGI programming is a commonly-used web development model that allows
+developers to construct dynamic websites. On his way to the class, Jim studied
+all the existing documentation on CGI. On the way back, Jim considered what he
+didn’t like about traditional, CGI-based programming environments. From these
+initial musings, the core of Zope was written while flying back from the CGI
+class.
Zope Corporation (then known as Digital Creations) went on to release three
open-source software packages to support web publishing: Bobo, Document
-Template, and BoboPOS. These packages were written in a language called Python,
-and provided a web publishing facility, text templating, and an object
+Template, and BoboPOS. These packages were written in a language called
+Python, and provided a web publishing facility, text templating, and an object
database, respectively. Digital Creations developed a commercial application
server based on their three opensource components. This product was called
Principia. In November of 1998, investor Hadar Pedhazur convinced Digital
Creations to open source Principia. These packages evolved into what are now
the core components of Zope 2.
-In 2001, the Zope community began working on a
-component architecture for Zope, but after several years they ended up with
-something much more: Zope 3. While Zope 2 was powerful and popular, Zope 3 was
-designed to bring web application development to the next level.
+In 2001, the Zope community began working on a component architecture for
+Zope, but after several years they ended up with something much more:
+Zope 3. While Zope 2 was powerful and popular, Zope 3 was designed to bring
+web application development to the next level.
Source: The Zope 3 Book
More information about the Checkins
mailing list