[Checkins] SVN: zope-story-website/branches/what_who_why_zope/ Check-in of mockup of 4-page layout, for evaluation by ZeOmega artists.
Jeff Rush
jrush at taupro.com
Wed Apr 1 02:19:03 EDT 2009
Log message for revision 98744:
Check-in of mockup of 4-page layout, for evaluation by ZeOmega artists.
Changed:
_U zope-story-website/branches/what_who_why_zope/
A zope-story-website/branches/what_who_why_zope/src/_static/basic.css
A zope-story-website/branches/what_who_why_zope/src/_themes/
A zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/
A zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/layout.html
A zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/
A zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/basic.css
A zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css
A zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css_t
A zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/theme.conf
U zope-story-website/branches/what_who_why_zope/src/conf.py
U zope-story-website/branches/what_who_why_zope/src/index.rst
U zope-story-website/branches/what_who_why_zope/src/who_is_zope.rst
U zope-story-website/branches/what_who_why_zope/src/why_use_zope.rst
U zope-story-website/branches/what_who_why_zope/src/zope_history.rst
-=-
Property changes on: zope-story-website/branches/what_who_why_zope
___________________________________________________________________
Added: svn:ignore
+ build
develop-eggs
eggs
lib
bin
parts
.installed.cfg
Added: zope-story-website/branches/what_who_why_zope/src/_static/basic.css
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/_static/basic.css (rev 0)
+++ zope-story-website/branches/what_who_why_zope/src/_static/basic.css 2009-04-01 06:19:02 UTC (rev 98744)
@@ -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%;
+}
Property changes on: zope-story-website/branches/what_who_why_zope/src/_static/basic.css
___________________________________________________________________
Added: svn:mime-type
+ text/css
Added: svn:keywords
+ Author Date Id Revision
Added: svn:eol-style
+ native
Added: zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/layout.html
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/layout.html (rev 0)
+++ zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/layout.html 2009-04-01 06:19:02 UTC (rev 98744)
@@ -0,0 +1,199 @@
+{%- block doctype -%}
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+{%- endblock %}
+{%- set reldelim1 = reldelim1 is not defined and ' »' or reldelim1 %}
+{%- set reldelim2 = reldelim2 is not defined and ' |' or reldelim2 %}
+
+{%- macro relbar() %}
+ <div class="related">
+ <h3>{{ _('Navigation') }}</h3>
+ <ul>
+ {%- for rellink in rellinks %}
+ <li class="right" {% if loop.first %}style="margin-right: 10px"{% endif %}>
+ <a href="{{ pathto(rellink[0]) }}" title="{{ rellink[1]|striptags }}"
+ {{ accesskey(rellink[2]) }}>{{ rellink[3] }}</a>
+ {%- if not loop.first %}{{ reldelim2 }}{% endif %}</li>
+ {%- endfor %}
+ {%- block rootrellink %}
+ <li><a href="{{ pathto(master_doc) }}">{{ shorttitle|e }}</a>{{ reldelim1 }}</li>
+ {%- endblock %}
+ {%- for parent in parents %}
+ <li><a href="{{ parent.link|e }}" {% if loop.last %}{{ accesskey("U") }}{% endif %}>{{ parent.title }}</a>{{ reldelim1 }}</li>
+ {%- endfor %}
+ {%- block relbaritems %} {% endblock %}
+ </ul>
+ </div>
+{%- endmacro %}
+
+{%- macro sidebarNULL() %}
+{%- endmacro %}
+
+{%- macro sidebar() %}
+ {%- if not embedded %}{% if not theme_nosidebar|tobool %}
+ <div class="sphinxsidebar">
+ <div class="sphinxsidebarwrapper">
+ {%- block sidebarlogo %}
+ {%- if logo %}
+ <p class="logo"><a href="{{ pathto(master_doc) }}">
+ <img class="logo" src="{{ pathto('_static/' + logo, 1) }}" alt="Logo"/>
+ </a></p>
+ {%- endif %}
+ {%- endblock %}
+ {%- block sidebartoc %}
+ {%- if display_toc %}
+ <h3><a href="{{ pathto(master_doc) }}">{{ _('Table Of Contents') }}</a></h3>
+ {{ toc }}
+ {%- endif %}
+ {%- endblock %}
+ {%- block sidebarrel %}
+ {%- if prev %}
+ <h4>{{ _('Previous topic') }}</h4>
+ <p class="topless"><a href="{{ prev.link|e }}"
+ title="{{ _('previous chapter') }}">{{ prev.title }}</a></p>
+ {%- endif %}
+ {%- if next %}
+ <h4>{{ _('Next topic') }}</h4>
+ <p class="topless"><a href="{{ next.link|e }}"
+ title="{{ _('next chapter') }}">{{ next.title }}</a></p>
+ {%- endif %}
+ {%- endblock %}
+ {%- block sidebarsourcelink %}
+ {%- if show_source and has_source and sourcename %}
+ <h3>{{ _('This Page') }}</h3>
+ <ul class="this-page-menu">
+ <li><a href="{{ pathto('_sources/' + sourcename, true)|e }}"
+ rel="nofollow">{{ _('Show Source') }}</a></li>
+ </ul>
+ {%- endif %}
+ {%- endblock %}
+ {%- if customsidebar %}
+ {% include customsidebar %}
+ {%- endif %}
+ {%- block sidebarsearch %}
+ {%- if pagename != "search" %}
+ <div id="searchbox" style="display: none">
+ <h3>{{ _('Quick search') }}</h3>
+ <form class="search" action="{{ pathto('search') }}" method="get">
+ <input type="text" name="q" size="18" />
+ <input type="submit" value="{{ _('Go') }}" />
+ <input type="hidden" name="check_keywords" value="yes" />
+ <input type="hidden" name="area" value="default" />
+ </form>
+ <p class="searchtip" style="font-size: 90%">
+ {{ _('Enter search terms or a module, class or function name.') }}
+ </p>
+ </div>
+ <script type="text/javascript">$('#searchbox').show(0);</script>
+ {%- endif %}
+ {%- endblock %}
+ </div>
+ </div>
+ {%- endif %}{% endif %}
+{%- endmacro %}
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ {{ metatags }}
+ {%- if not embedded %}
+ {%- set titlesuffix = " — "|safe + docstitle|e %}
+ {%- else %}
+ {%- set titlesuffix = "" %}
+ {%- endif %}
+ <title>{{ title|striptags }}{{ titlesuffix }}</title>
+ <link rel="stylesheet" href="{{ pathto('_static/' + style, 1) }}" type="text/css" />
+ <link rel="stylesheet" href="{{ pathto('_static/pygments.css', 1) }}" type="text/css" />
+ {%- if not embedded %}
+ <script type="text/javascript">
+ var DOCUMENTATION_OPTIONS = {
+ URL_ROOT: '{{ pathto("", 1) }}',
+ VERSION: '{{ release|e }}',
+ COLLAPSE_MODINDEX: false,
+ FILE_SUFFIX: '{{ file_suffix }}',
+ HAS_SOURCE: {{ has_source|lower }}
+ };
+ </script>
+ {%- for scriptfile in script_files %}
+ <script type="text/javascript" src="{{ pathto(scriptfile, 1) }}"></script>
+ {%- endfor %}
+ {%- if use_opensearch %}
+ <link rel="search" type="application/opensearchdescription+xml"
+ title="{% trans docstitle=docstitle|e %}Search within {{ docstitle }}{% endtrans %}"
+ href="{{ pathto('_static/opensearch.xml', 1) }}"/>
+ {%- endif %}
+ {%- if favicon %}
+ <link rel="shortcut icon" href="{{ pathto('_static/' + favicon, 1) }}"/>
+ {%- endif %}
+ {%- endif %}
+{%- block linktags %}
+ {%- if hasdoc('about') %}
+ <link rel="author" title="{{ _('About these documents') }}" href="{{ pathto('about') }}" />
+ {%- endif %}
+ {%- if hasdoc('genindex') %}
+ <link rel="index" title="{{ _('Index') }}" href="{{ pathto('genindex') }}" />
+ {%- endif %}
+ {%- if hasdoc('search') %}
+ <link rel="search" title="{{ _('Search') }}" href="{{ pathto('search') }}" />
+ {%- endif %}
+ {%- if hasdoc('copyright') %}
+ <link rel="copyright" title="{{ _('Copyright') }}" href="{{ pathto('copyright') }}" />
+ {%- endif %}
+ <link rel="top" title="{{ docstitle|e }}" href="{{ pathto('index') }}" />
+ {%- if parents %}
+ <link rel="up" title="{{ parents[-1].title|striptags }}" href="{{ parents[-1].link|e }}" />
+ {%- endif %}
+ {%- if next %}
+ <link rel="next" title="{{ next.title|striptags }}" href="{{ next.link|e }}" />
+ {%- endif %}
+ {%- if prev %}
+ <link rel="prev" title="{{ prev.title|striptags }}" href="{{ prev.link|e }}" />
+ {%- endif %}
+{%- endblock %}
+{%- block extrahead %} {% endblock %}
+ </head>
+ <body>
+{%- block header %}{% endblock %}
+
+{%- block relbar1 %}{{ relbar() }}{% endblock %}
+
+{%- block sidebar1 %} {# possible location for sidebar #} {% endblock %}
+
+ <div class="document">
+{%- block document %}
+ <div class="documentwrapper">
+ {%- if not embedded %}{% if not theme_nosidebar|tobool %}
+ <div class="bodywrapper">
+ {%- endif %}{% endif %}
+ <div class="body">
+ {% block body %} {% endblock %}
+ </div>
+ {%- if not embedded %}{% if not theme_nosidebar|tobool %}
+ </div>
+ {%- endif %}{% endif %}
+ </div>
+{%- endblock %}
+
+{%- block sidebar2 %}{{ sidebarNULL() }}{% endblock %}
+ <div class="clearer"></div>
+ </div>
+
+{%- block relbar2 %}{{ relbar() }}{% endblock %}
+
+{%- block footer %}
+ <div class="footer">
+ {%- if hasdoc('copyright') %}
+ {% trans path=pathto('copyright'), copyright=copyright|e %}© <a href="{{ path }}">Copyright</a> {{ copyright }}.{% endtrans %}
+ {%- else %}
+ {% trans copyright=copyright|e %}© Copyright {{ copyright }}.{% endtrans %}
+ {%- endif %}
+ {%- if last_updated %}
+ {% trans last_updated=last_updated|e %}Last updated on {{ last_updated }}.{% endtrans %}
+ {%- endif %}
+ {%- if show_sphinx %}
+ {% trans sphinx_version=sphinx_version|e %}Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> {{ sphinx_version }}.{% endtrans %}
+ {%- endif %}
+ </div>
+{%- endblock %}
+ </body>
+</html>
Property changes on: zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/layout.html
___________________________________________________________________
Added: svn:mime-type
+ text/html
Added: svn:keywords
+ Author Date Id Revision
Added: svn:eol-style
+ native
Added: zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/basic.css
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/basic.css (rev 0)
+++ zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/basic.css 2009-04-01 06:19:02 UTC (rev 98744)
@@ -0,0 +1,414 @@
+/**
+ * Sphinx stylesheet -- basic theme
+ * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ */
+
+/* -- main layout ----------------------------------------------------------- */
+
+div.documentwrapper {
+ float: left;
+ width: 100%;
+}
+
+div.bodywrapper {
+ margin: 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;
+ }
+}
Property changes on: zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/basic.css
___________________________________________________________________
Added: svn:mime-type
+ text/css
Added: svn:keywords
+ Author Date Id Revision
Added: svn:eol-style
+ native
Added: zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css (rev 0)
+++ zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css 2009-04-01 06:19:02 UTC (rev 98744)
@@ -0,0 +1,238 @@
+/**
+ * Sphinx stylesheet -- default theme
+ * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ */
+
+ at import url("basic.css");
+
+/* -- page layout ----------------------------------------------------------- */
+
+body {
+ font-family: {{ theme_bodyfont }};
+ font-size: 100%;
+ background-color: {{ theme_footerbgcolor }};
+ color: #000;
+ margin: 0;
+ padding: 0;
+}
+
+div.document {
+ background-color: {{ theme_sidebarbgcolor }};
+}
+
+div.body {
+ background-color: {{ theme_bgcolor }};
+ color: {{ theme_textcolor }};
+ padding: 0 20px 30px 20px;
+}
+
+{%- if theme_rightsidebar|tobool %}
+div.bodywrapper {
+ margin: 0 230px 0 0;
+}
+{%- endif %}
+
+div.bodywrapper {
+ margin: 0 0 /* 230px */ 0 0;
+}
+
+div.footer {
+ color: {{ theme_footertextcolor }};
+ width: 100%;
+ padding: 9px 0 9px 0;
+ text-align: center;
+ font-size: 75%;
+}
+
+div.footer a {
+ color: {{ theme_footertextcolor }};
+ text-decoration: underline;
+}
+
+div.related {
+ background-color: {{ theme_relbarbgcolor }};
+ line-height: 30px;
+ color: {{ theme_relbartextcolor }};
+}
+
+div.related a {
+ color: {{ theme_relbarlinkcolor }};
+}
+
+div.sphinxsidebar {
+ {%- if theme_stickysidebar|tobool %}
+ top: 30px;
+ margin: 0;
+ position: fixed;
+ overflow: auto;
+ height: 100%;
+ {%- endif %}
+ {%- if theme_rightsidebar|tobool %}
+ float: right;
+ {%- if theme_stickysidebar|tobool %}
+ right: 0;
+ {%- endif %}
+ {%- endif %}
+}
+
+{%- if theme_stickysidebar|tobool %}
+/* this is nice, but it it leads to hidden headings when jumping
+ to an anchor */
+/*
+div.related {
+ position: fixed;
+}
+
+div.documentwrapper {
+ margin-top: 30px;
+}
+*/
+{%- endif %}
+
+div.sphinxsidebar h3 {
+ font-family: {{ theme_headfont }};
+ color: {{ theme_sidebartextcolor }};
+ font-size: 1.4em;
+ font-weight: normal;
+ margin: 0;
+ padding: 0;
+}
+
+div.sphinxsidebar h3 a {
+ color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar h4 {
+ font-family: {{ theme_headfont }};
+ color: {{ theme_sidebartextcolor }};
+ font-size: 1.3em;
+ font-weight: normal;
+ margin: 5px 0 0 0;
+ padding: 0;
+}
+
+div.sphinxsidebar p {
+ color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar p.topless {
+ margin: 5px 10px 10px 10px;
+}
+
+div.sphinxsidebar ul {
+ margin: 10px;
+ padding: 0;
+ color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar a {
+ color: {{ theme_sidebarlinkcolor }};
+}
+
+div.sphinxsidebar input {
+ border: 1px solid {{ theme_sidebarlinkcolor }};
+ font-family: sans-serif;
+ font-size: 1em;
+}
+
+/* -- body styles ----------------------------------------------------------- */
+
+a {
+ color: {{ theme_linkcolor }};
+ text-decoration: none;
+}
+
+a:hover {
+ text-decoration: underline;
+}
+
+div.body p, div.body dd, div.body li {
+ text-align: justify;
+ line-height: 130%;
+}
+
+div.body h1,
+div.body h2,
+div.body h3,
+div.body h4,
+div.body h5,
+div.body h6 {
+ font-family: {{ theme_headfont }};
+ background-color: {{ theme_headbgcolor }};
+ font-weight: normal;
+ color: {{ theme_headtextcolor }};
+ border-bottom: 1px solid #ccc;
+ margin: 20px -20px 10px -20px;
+ padding: 3px 0 3px 10px;
+}
+
+div.body h1 { margin-top: 0; font-size: 200%; }
+div.body h2 { font-size: 160%; }
+div.body h3 { font-size: 140%; }
+div.body h4 { font-size: 120%; }
+div.body h5 { font-size: 110%; }
+div.body h6 { font-size: 100%; }
+
+a.headerlink {
+ color: {{ theme_headlinkcolor }};
+ font-size: 0.8em;
+ padding: 0 4px 0 4px;
+ text-decoration: none;
+}
+
+a.headerlink:hover {
+ background-color: {{ theme_headlinkcolor }};
+ color: white;
+}
+
+div.body p, div.body dd, div.body li {
+ text-align: justify;
+ line-height: 130%;
+}
+
+div.admonition p.admonition-title + p {
+ display: inline;
+}
+
+div.note {
+ background-color: #eee;
+ border: 1px solid #ccc;
+}
+
+div.seealso {
+ background-color: #ffc;
+ border: 1px solid #ff6;
+}
+
+div.topic {
+ background-color: #eee;
+}
+
+div.warning {
+ background-color: #ffe4e4;
+ border: 1px solid #f66;
+}
+
+p.admonition-title {
+ display: inline;
+}
+
+p.admonition-title:after {
+ content: ":";
+}
+
+pre {
+ padding: 5px;
+ background-color: {{ theme_codebgcolor }};
+ color: {{ theme_codetextcolor }};
+ line-height: 120%;
+ border: 1px solid #ac9;
+ border-left: none;
+ border-right: none;
+}
+
+tt {
+ background-color: #ecf0f3;
+ padding: 0 1px 0 1px;
+ font-size: 0.95em;
+}
Property changes on: zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css
___________________________________________________________________
Added: svn:mime-type
+ text/css
Added: svn:keywords
+ Author Date Id Revision
Added: svn:eol-style
+ native
Added: zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css_t
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css_t (rev 0)
+++ zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/static/default.css_t 2009-04-01 06:19:02 UTC (rev 98744)
@@ -0,0 +1,234 @@
+/**
+ * Sphinx stylesheet -- default theme
+ * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ */
+
+ at import url("basic.css");
+
+/* -- page layout ----------------------------------------------------------- */
+
+body {
+ font-family: {{ theme_bodyfont }};
+ font-size: 100%;
+ background-color: {{ theme_footerbgcolor }};
+ color: #000;
+ margin: 0;
+ padding: 0;
+}
+
+div.document {
+ background-color: {{ theme_sidebarbgcolor }};
+}
+
+div.body {
+ background-color: {{ theme_bgcolor }};
+ color: {{ theme_textcolor }};
+ padding: 0 20px 30px 20px;
+}
+
+{%- if theme_rightsidebar|tobool %}
+div.bodywrapper {
+ margin: 0 230px 0 0;
+}
+{%- endif %}
+
+div.footer {
+ color: {{ theme_footertextcolor }};
+ width: 100%;
+ padding: 9px 0 9px 0;
+ text-align: center;
+ font-size: 75%;
+}
+
+div.footer a {
+ color: {{ theme_footertextcolor }};
+ text-decoration: underline;
+}
+
+div.related {
+ background-color: {{ theme_relbarbgcolor }};
+ line-height: 30px;
+ color: {{ theme_relbartextcolor }};
+}
+
+div.related a {
+ color: {{ theme_relbarlinkcolor }};
+}
+
+div.sphinxsidebar {
+ {%- if theme_stickysidebar|tobool %}
+ top: 30px;
+ margin: 0;
+ position: fixed;
+ overflow: auto;
+ height: 100%;
+ {%- endif %}
+ {%- if theme_rightsidebar|tobool %}
+ float: right;
+ {%- if theme_stickysidebar|tobool %}
+ right: 0;
+ {%- endif %}
+ {%- endif %}
+}
+
+{%- if theme_stickysidebar|tobool %}
+/* this is nice, but it it leads to hidden headings when jumping
+ to an anchor */
+/*
+div.related {
+ position: fixed;
+}
+
+div.documentwrapper {
+ margin-top: 30px;
+}
+*/
+{%- endif %}
+
+div.sphinxsidebar h3 {
+ font-family: {{ theme_headfont }};
+ color: {{ theme_sidebartextcolor }};
+ font-size: 1.4em;
+ font-weight: normal;
+ margin: 0;
+ padding: 0;
+}
+
+div.sphinxsidebar h3 a {
+ color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar h4 {
+ font-family: {{ theme_headfont }};
+ color: {{ theme_sidebartextcolor }};
+ font-size: 1.3em;
+ font-weight: normal;
+ margin: 5px 0 0 0;
+ padding: 0;
+}
+
+div.sphinxsidebar p {
+ color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar p.topless {
+ margin: 5px 10px 10px 10px;
+}
+
+div.sphinxsidebar ul {
+ margin: 10px;
+ padding: 0;
+ color: {{ theme_sidebartextcolor }};
+}
+
+div.sphinxsidebar a {
+ color: {{ theme_sidebarlinkcolor }};
+}
+
+div.sphinxsidebar input {
+ border: 1px solid {{ theme_sidebarlinkcolor }};
+ font-family: sans-serif;
+ font-size: 1em;
+}
+
+/* -- body styles ----------------------------------------------------------- */
+
+a {
+ color: {{ theme_linkcolor }};
+ text-decoration: none;
+}
+
+a:hover {
+ text-decoration: underline;
+}
+
+div.body p, div.body dd, div.body li {
+ text-align: justify;
+ line-height: 130%;
+}
+
+div.body h1,
+div.body h2,
+div.body h3,
+div.body h4,
+div.body h5,
+div.body h6 {
+ font-family: {{ theme_headfont }};
+ background-color: {{ theme_headbgcolor }};
+ font-weight: normal;
+ color: {{ theme_headtextcolor }};
+ border-bottom: 1px solid #ccc;
+ margin: 20px -20px 10px -20px;
+ padding: 3px 0 3px 10px;
+}
+
+div.body h1 { margin-top: 0; font-size: 200%; }
+div.body h2 { font-size: 160%; }
+div.body h3 { font-size: 140%; }
+div.body h4 { font-size: 120%; }
+div.body h5 { font-size: 110%; }
+div.body h6 { font-size: 100%; }
+
+a.headerlink {
+ color: {{ theme_headlinkcolor }};
+ font-size: 0.8em;
+ padding: 0 4px 0 4px;
+ text-decoration: none;
+}
+
+a.headerlink:hover {
+ background-color: {{ theme_headlinkcolor }};
+ color: white;
+}
+
+div.body p, div.body dd, div.body li {
+ text-align: justify;
+ line-height: 130%;
+}
+
+div.admonition p.admonition-title + p {
+ display: inline;
+}
+
+div.note {
+ background-color: #eee;
+ border: 1px solid #ccc;
+}
+
+div.seealso {
+ background-color: #ffc;
+ border: 1px solid #ff6;
+}
+
+div.topic {
+ background-color: #eee;
+}
+
+div.warning {
+ background-color: #ffe4e4;
+ border: 1px solid #f66;
+}
+
+p.admonition-title {
+ display: inline;
+}
+
+p.admonition-title:after {
+ content: ":";
+}
+
+pre {
+ padding: 5px;
+ background-color: {{ theme_codebgcolor }};
+ color: {{ theme_codetextcolor }};
+ line-height: 120%;
+ border: 1px solid #ac9;
+ border-left: none;
+ border-right: none;
+}
+
+tt {
+ background-color: #ecf0f3;
+ padding: 0 1px 0 1px;
+ font-size: 0.95em;
+}
Added: zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/theme.conf
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/theme.conf (rev 0)
+++ zope-story-website/branches/what_who_why_zope/src/_themes/zopestory/theme.conf 2009-04-01 06:19:02 UTC (rev 98744)
@@ -0,0 +1,28 @@
+[theme]
+inherit = basic
+stylesheet = default.css
+pygments_style = sphinx
+
+[options]
+rightsidebar = false
+stickysidebar = false
+
+footerbgcolor = #11303d
+footertextcolor = #ffffff
+sidebarbgcolor = #1c4e63
+sidebartextcolor = #ffffff
+sidebarlinkcolor = #98dbcc
+relbarbgcolor = #133f52
+relbartextcolor = #ffffff
+relbarlinkcolor = #ffffff
+bgcolor = #ffffff
+textcolor = #000000
+headbgcolor = #f2f2f2
+headtextcolor = #20435c
+headlinkcolor = #c60f0f
+linkcolor = #355f7c
+codebgcolor = #eeffcc
+codetextcolor = #333333
+
+bodyfont = sans-serif
+headfont = 'Trebuchet MS', sans-serif
Modified: zope-story-website/branches/what_who_why_zope/src/conf.py
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/conf.py 2009-04-01 05:24:47 UTC (rev 98743)
+++ zope-story-website/branches/what_who_why_zope/src/conf.py 2009-04-01 06:19:02 UTC (rev 98744)
@@ -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/branches/what_who_why_zope/src/index.rst
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/index.rst 2009-04-01 05:24:47 UTC (rev 98743)
+++ zope-story-website/branches/what_who_why_zope/src/index.rst 2009-04-01 06:19:02 UTC (rev 98744)
@@ -1,180 +1,185 @@
+.. role:: header
+.. role:: zsection
-What is Zope?
-================
+.. container::
+ :class: menuacross
+ + `What is Zope? <index.html>`_
+ + `Who is Zope? <who_is_zope.html>`_
+ + `Why Zope? <why_use_zope.html>`_
+
.. container::
- :class: LeftCol
-
- Zope is a Community
- -------------------
- Hundreds of companies and thousands of developers devoted to solutions
- to the perennial problems of building complex, scalable web applications.
- `More...<Who is Zope?>`_
-
- 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.
-
- Zope is a Broad Software Technology
- -----------------------------------
-
- The base Zope Framework has powered web development frameworks,
- web application servers, content management systems, and many
- other software components.
-
- 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. `More...<Why use Zope?>`_
-
-
- Zope is Python-based
- ------------------------------
-
- Zope is written in `Python`_, a highly-productive, object-oriented scripting
- language.
+ :class: LeftCol
+ .. rubric:: Zope is a Community
+ Hundreds of companies and thousands of developers devoted to solutions to
+ the perennial problems of building complex, scalable web applications.
+ `More... <who_is_zope.rst>`__
+
+ .. 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.
+
+ .. rubric:: Zope is a Broad Software Technology
+
+ The base Zope Framework has powered web development frameworks, web
+ application servers, content management systems, and many other software
+ components.
+
+ .. rubric:: 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. `More... <why_use_zope.rst>`__
+
+ .. rubric:: Zope is Python-based
+
+ Zope is written in `Python`_, a highly-productive, object-oriented
+ scripting language.
+
+
.. container::
- :class: LeftCol
-
- Frameworks
- ===========
-
- The following are notable frameworks which users are advised to look at if
- they are looking at entering the world of Zope.
-
- .. raw:: html
-
- <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>
-
- Applications
- ============
-
- Several applications are built atop the Zope Framework, providing rich user
- experiences.
-
-
- .. raw:: html
-
- <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>
-
-
- Compose Your Own
- ================
-
- 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.
-
- * `Zope 2 Application Server`_, a mature application server which
- has thrived in enterprise production systems for nearly 10 years.
-
- * `Zope Framework Wiki`_, a place where more information about the Zope
- framwork 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.
-
-
-
-
- Python Community Cross-Pollination
- ===================================
-
- Zope software components are also deployed in the wider Python community; for
- example:
-
- * `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.
+ :class: RightCol
-.. _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
+ .. container::
+ :class: frameworks
+
+ :zsection:`Frameworks`
+
+ The following are notable frameworks which users are advised to look at if
+ they are looking at entering the world of Zope.
+
+ .. container::
+ :class: framework
+
+ |Grok|_
+
+ aimed at making the full power of the Zope Framework accessible to any
+ Python developer.
+
+ .. container::
+ :class: framework
+
+ |Repoze|_
+
+ a web framework toolkit integrating WSGI middleware with Zope.
+
+ .. container::
+ :class: framework
+
+ |Zope 2|_
+
+ a mature application server which has thrived in enterprise production
+ systems for nearly 10 years.
+
+
+ .. container::
+ :class: applications
+
+ :zsection:`Applications`
+
+ Several applications are built atop the Zope Framework, providing rich user
+ experiences.
+
+ .. container::
+ :class: application
+
+ |Plone|_
+
+ 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 Canonical 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 Wiki`_, 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" />
+
+
+Python Community Cross-Pollination
+===================================
+
+Zope software components are also deployed in the wider Python community; for
+example:
+
+* `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.
+
+.. |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 Wiki`: http://wiki.zope.org/zope3/Zope3Wiki/
+.. _`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/
Modified: zope-story-website/branches/what_who_why_zope/src/who_is_zope.rst
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/who_is_zope.rst 2009-04-01 05:24:47 UTC (rev 98743)
+++ zope-story-website/branches/what_who_why_zope/src/who_is_zope.rst 2009-04-01 06:19:02 UTC (rev 98744)
@@ -1,86 +1,87 @@
+Who is Zope?
+============
-Who is Zope
-==============
-..
- Three Columns: community, business, history
-
+.. role:: header
+.. 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 Projects
+
+ + Zope Framework
+ + Plone
+ + Grok
+ + Repoze
+ + Repoze.BFG
+ + Zope 2
+ + Plone Community
+ + `Planet Zope <http://planet.zope.org/>`_
+
+ .. rubric:: Zope Community Intersections
+
+ + Python Community
+ + Twisted
+ + Zope 2 community (mailing lists, irc, etc.)
+ + Turbogears
+ + Pylons
+ + Buildout
+ + LaunchPad
+
.. container::
- :class: LeftCol
-
+ :class: MiddleColOfThree
- 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.
-
- Zope Community Projects
- ------------------------
- Zope Framework
- Plone
- Grok
- Repose
- Repose.BFG
- Zope 2
- Plone Community
- `Planet Zope <http://planet.zope.org/>`_
-
-
- Zope Community Intersections
- ----------------------------
- Python Community
- Twisted
- Zope 2 community (mailing lists, irc, etc.)
- Turbogears
- Pylons
- Buildout
- LaunchPad
-
-
-
+ :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.
+
+ + Partners (is there an existing page?)
+ + Solution Providers (link to existing page)
+
.. container::
- :class: MiddleCol
+ :class: RightColOfThree
- Business
- ---------
- The `Zope Foundation`_ takes care of business, shepherding Zope's
- intellectual property and providing the server infrastructure needed
- to support community projects.
-
- Partners (is there an existing page?)
- Solution Providers (link to existing page)
-
+ :header:`History`
-.. container::
- :class: RightCol
-
- 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
+ .. 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/
Modified: zope-story-website/branches/what_who_why_zope/src/why_use_zope.rst
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/why_use_zope.rst 2009-04-01 05:24:47 UTC (rev 98743)
+++ zope-story-website/branches/what_who_why_zope/src/why_use_zope.rst 2009-04-01 06:19:02 UTC (rev 98744)
@@ -1,43 +1,46 @@
Why Use Zope?
-==============
+=============
-Zope applications, libraries, and frameworks are suited for different
-purposes and environments; each has a set of strengths and weaknesses.
+Zope applications, libraries, and frameworks are suited for different purposes
+and environments; each has a set of strengths and weaknesses.
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.
+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.
+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.
+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.
+--------------------
+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 complexity of a relational database
@@ -48,15 +51,13 @@
mappers such as SQLAlchemy and 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.
+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.
-RDBMs
-
-
+RDBMs
Modified: zope-story-website/branches/what_who_why_zope/src/zope_history.rst
===================================================================
--- zope-story-website/branches/what_who_why_zope/src/zope_history.rst 2009-04-01 05:24:47 UTC (rev 98743)
+++ zope-story-website/branches/what_who_why_zope/src/zope_history.rst 2009-04-01 06:19:02 UTC (rev 98744)
@@ -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