[Checkins] SVN: zope-story-website/trunk/ Moved content files to src subdirectory; changed Sphinx Makefile to use new path
Brad Allen
brad at allendev.com
Mon Mar 30 17:24:33 EDT 2009
Log message for revision 98637:
Moved content files to src subdirectory; changed Sphinx Makefile to use new path
Changed:
U zope-story-website/trunk/Makefile
D zope-story-website/trunk/conf.py
D zope-story-website/trunk/index.rst
A zope-story-website/trunk/src/
A zope-story-website/trunk/src/_static/
A zope-story-website/trunk/src/conf.py
A zope-story-website/trunk/src/index.rst
A zope-story-website/trunk/src/zope_history.rst
D zope-story-website/trunk/zope_history.rst
-=-
Modified: zope-story-website/trunk/Makefile
===================================================================
--- zope-story-website/trunk/Makefile 2009-03-30 21:21:56 UTC (rev 98636)
+++ zope-story-website/trunk/Makefile 2009-03-30 21:24:33 UTC (rev 98637)
@@ -3,13 +3,13 @@
# You can set these variables from the command line.
SPHINXOPTS =
-SPHINXBUILD = sphinx-build
+SPHINXBUILD = bin/sphinx-build
PAPER =
# Internal variables.
PAPEROPT_a4 = -D latex_paper_size=a4
PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS = -d _build/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+ALLSPHINXOPTS = -d _build/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) src
.PHONY: help clean html dirhtml pickle json htmlhelp qthelp latex changes linkcheck doctest
Deleted: zope-story-website/trunk/conf.py
===================================================================
--- zope-story-website/trunk/conf.py 2009-03-30 21:21:56 UTC (rev 98636)
+++ zope-story-website/trunk/conf.py 2009-03-30 21:24:33 UTC (rev 98637)
@@ -1,194 +0,0 @@
-# -*- coding: utf-8 -*-
-#
-# Zope documentation build configuration file, created by
-# sphinx-quickstart on Mon Mar 30 10:17:47 2009.
-#
-# This file is execfile()d with the current directory set to its containing dir.
-#
-# Note that not all possible configuration values are present in this
-# autogenerated file.
-#
-# All configuration values have a default; values that are commented out
-# serve to show the default.
-
-import sys, os
-
-# If extensions (or modules to document with autodoc) are in another directory,
-# add these directories to sys.path here. If the directory is relative to the
-# documentation root, use os.path.abspath to make it absolute, like shown here.
-#sys.path.append(os.path.abspath('.'))
-
-# -- General configuration -----------------------------------------------------
-
-# Add any Sphinx extension module names here, as strings. They can be extensions
-# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
-extensions = []
-
-# Add any paths that contain templates here, relative to this directory.
-templates_path = ['_templates']
-
-# The suffix of source filenames.
-source_suffix = '.rst'
-
-# The encoding of source files.
-#source_encoding = 'utf-8'
-
-# The master toctree document.
-master_doc = 'index'
-
-# General information about the project.
-project = u'Zope'
-copyright = u'2009, Zope Developers'
-
-# The version info for the project you're documenting, acts as replacement for
-# |version| and |release|, also used in various other places throughout the
-# built documents.
-#
-# The short X.Y version.
-version = '0.1'
-# The full version, including alpha/beta/rc tags.
-release = '0.1'
-
-# The language for content autogenerated by Sphinx. Refer to documentation
-# for a list of supported languages.
-#language = None
-
-# There are two options for replacing |today|: either, you set today to some
-# non-false value, then it is used:
-#today = ''
-# Else, today_fmt is used as the format for a strftime call.
-#today_fmt = '%B %d, %Y'
-
-# List of documents that shouldn't be included in the build.
-#unused_docs = []
-
-# List of directories, relative to source directory, that shouldn't be searched
-# for source files.
-exclude_trees = ['_build']
-
-# The reST default role (used for this markup: `text`) to use for all documents.
-#default_role = None
-
-# If true, '()' will be appended to :func: etc. cross-reference text.
-#add_function_parentheses = True
-
-# If true, the current module name will be prepended to all description
-# unit titles (such as .. function::).
-#add_module_names = True
-
-# If true, sectionauthor and moduleauthor directives will be shown in the
-# output. They are ignored by default.
-#show_authors = False
-
-# The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
-
-# A list of ignored prefixes for module index sorting.
-#modindex_common_prefix = []
-
-
-# -- Options for HTML output ---------------------------------------------------
-
-# The theme to use for HTML and HTML Help pages. Major themes that come with
-# Sphinx are currently 'default' and 'sphinxdoc'.
-html_theme = 'default'
-
-# 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
-# documentation.
-#html_theme_options = {}
-
-# Add any paths that contain custom themes here, relative to this directory.
-#html_theme_path = []
-
-# The name for this set of Sphinx documents. If None, it defaults to
-# "<project> v<release> documentation".
-#html_title = None
-
-# A shorter title for the navigation bar. Default is the same as html_title.
-#html_short_title = None
-
-# The name of an image file (relative to this directory) to place at the top
-# of the sidebar.
-#html_logo = None
-
-# The name of an image file (within the static path) to use as favicon of the
-# docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
-# pixels large.
-#html_favicon = None
-
-# Add any paths that contain custom static files (such as style sheets) here,
-# relative to this directory. They are copied after the builtin static files,
-# so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ['_static']
-
-# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
-# using the given strftime format.
-#html_last_updated_fmt = '%b %d, %Y'
-
-# If true, SmartyPants will be used to convert quotes and dashes to
-# typographically correct entities.
-#html_use_smartypants = True
-
-# Custom sidebar templates, maps document names to template names.
-#html_sidebars = {}
-
-# Additional templates that should be rendered to pages, maps page names to
-# template names.
-#html_additional_pages = {}
-
-# If false, no module index is generated.
-#html_use_modindex = True
-
-# If false, no index is generated.
-#html_use_index = True
-
-# If true, the index is split into individual pages for each letter.
-#html_split_index = False
-
-# If true, links to the reST sources are added to the pages.
-#html_show_sourcelink = True
-
-# If true, an OpenSearch description file will be output, and all pages will
-# contain a <link> tag referring to it. The value of this option must be the
-# base URL from which the finished HTML is served.
-#html_use_opensearch = ''
-
-# If nonempty, this is the file name suffix for HTML files (e.g. ".xhtml").
-#html_file_suffix = ''
-
-# Output file base name for HTML help builder.
-htmlhelp_basename = 'Zopedoc'
-
-
-# -- Options for LaTeX output --------------------------------------------------
-
-# The paper size ('letter' or 'a4').
-#latex_paper_size = 'letter'
-
-# The font size ('10pt', '11pt' or '12pt').
-#latex_font_size = '10pt'
-
-# Grouping the document tree into LaTeX files. List of tuples
-# (source start file, target name, title, author, documentclass [howto/manual]).
-latex_documents = [
- ('index', 'Zope.tex', u'Zope Documentation',
- u'Zope Developers', 'manual'),
-]
-
-# The name of an image file (relative to this directory) to place at the top of
-# the title page.
-#latex_logo = None
-
-# For "manual" documents, if this is true, then toplevel headings are parts,
-# not chapters.
-#latex_use_parts = False
-
-# Additional stuff for the LaTeX preamble.
-#latex_preamble = ''
-
-# Documents to append as an appendix to all manuals.
-#latex_appendices = []
-
-# If false, no module index is generated.
-#latex_use_modindex = True
Deleted: zope-story-website/trunk/index.rst
===================================================================
--- zope-story-website/trunk/index.rst 2009-03-30 21:21:56 UTC (rev 98636)
+++ zope-story-website/trunk/index.rst 2009-03-30 21:24:33 UTC (rev 98637)
@@ -1,79 +0,0 @@
-Welcome to the Zope Community
-=============================
-
-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.
-
-Unity in Diversity
-==================
-The Zope Framework is collection of Python-based software
-components used as building blocks for a variety of projects,
-including:
-
- * `Plone`_, A powerful, flexible Content Management solution that is
- easy to install, use and extend.
-
- * `Zope 2 Application Server`_, a mature application server which
- has thrived in enterprise production systems for nearly 10 years.
-
- * `Grok`_, a heavyweight Python web framework aimed at making
- the full power of the Zope Framework accessible to the average
- Python developer.
-
- * `Repoze`_, a web framework toolkit integrating WSGI middleware with Zope.
-
-
- * ...and a collection of individual web applications
- built using the Zope Framework Components [#more_zca]_
-
-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.
-
-Organizational Support
-======================
-
-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 `Zope Foundation`_
-
-
-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`_, developed at Zope Corporation, has gained traction outside
- Zope Community as a Python-based build system for creating, assembling and
- deploying applications from multiple components.
-
-.. _Zope 2 Application Server: http://zope2.zopyx.de/
-.. _Plone: http://plone.org
-.. _Repoze: http://repoze.org
-.. _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
-
-Footnotes
-=========================
-.. [#more_zca]
-
- - `Schooltool`_
- - `Launchpad`_
-
-.. _Schooltool: http://www.schooltool.org/
-.. _Launchpad: http://launchpad.net
Copied: zope-story-website/trunk/src/conf.py (from rev 98625, zope-story-website/trunk/conf.py)
===================================================================
--- zope-story-website/trunk/src/conf.py (rev 0)
+++ zope-story-website/trunk/src/conf.py 2009-03-30 21:24:33 UTC (rev 98637)
@@ -0,0 +1,194 @@
+# -*- coding: utf-8 -*-
+#
+# Zope documentation build configuration file, created by
+# sphinx-quickstart on Mon Mar 30 10:17:47 2009.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys, os
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#sys.path.append(os.path.abspath('.'))
+
+# -- General configuration -----------------------------------------------------
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = []
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8'
+
+# The master toctree document.
+master_doc = 'index'
+
+# General information about the project.
+project = u'Zope'
+copyright = u'2009, Zope Developers'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+version = '0.1'
+# The full version, including alpha/beta/rc tags.
+release = '0.1'
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#language = None
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+#today_fmt = '%B %d, %Y'
+
+# List of documents that shouldn't be included in the build.
+#unused_docs = []
+
+# List of directories, relative to source directory, that shouldn't be searched
+# for source files.
+exclude_trees = ['_build']
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages. Major themes that come with
+# Sphinx are currently 'default' and 'sphinxdoc'.
+html_theme = 'default'
+
+# 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
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
+
+# The name for this set of Sphinx documents. If None, it defaults to
+# "<project> v<release> documentation".
+#html_title = None
+
+# A shorter title for the navigation bar. Default is the same as html_title.
+#html_short_title = None
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+#html_logo = None
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+#html_favicon = None
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_use_modindex = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it. The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# If nonempty, this is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = ''
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'Zopedoc'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+# The paper size ('letter' or 'a4').
+#latex_paper_size = 'letter'
+
+# The font size ('10pt', '11pt' or '12pt').
+#latex_font_size = '10pt'
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+ ('index', 'Zope.tex', u'Zope Documentation',
+ u'Zope Developers', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# Additional stuff for the LaTeX preamble.
+#latex_preamble = ''
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_use_modindex = True
Copied: zope-story-website/trunk/src/index.rst (from rev 98625, zope-story-website/trunk/index.rst)
===================================================================
--- zope-story-website/trunk/src/index.rst (rev 0)
+++ zope-story-website/trunk/src/index.rst 2009-03-30 21:24:33 UTC (rev 98637)
@@ -0,0 +1,79 @@
+Welcome to the Zope Community
+=============================
+
+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.
+
+Unity in Diversity
+==================
+The Zope Framework is collection of Python-based software
+components used as building blocks for a variety of projects,
+including:
+
+ * `Plone`_, A powerful, flexible Content Management solution that is
+ easy to install, use and extend.
+
+ * `Zope 2 Application Server`_, a mature application server which
+ has thrived in enterprise production systems for nearly 10 years.
+
+ * `Grok`_, a heavyweight Python web framework aimed at making
+ the full power of the Zope Framework accessible to the average
+ Python developer.
+
+ * `Repoze`_, a web framework toolkit integrating WSGI middleware with Zope.
+
+
+ * ...and a collection of individual web applications
+ built using the Zope Framework Components [#more_zca]_
+
+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.
+
+Organizational Support
+======================
+
+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 `Zope Foundation`_
+
+
+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`_, developed at Zope Corporation, has gained traction outside
+ Zope Community as a Python-based build system for creating, assembling and
+ deploying applications from multiple components.
+
+.. _Zope 2 Application Server: http://zope2.zopyx.de/
+.. _Plone: http://plone.org
+.. _Repoze: http://repoze.org
+.. _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
+
+Footnotes
+=========================
+.. [#more_zca]
+
+ - `Schooltool`_
+ - `Launchpad`_
+
+.. _Schooltool: http://www.schooltool.org/
+.. _Launchpad: http://launchpad.net
Copied: zope-story-website/trunk/src/zope_history.rst (from rev 98625, zope-story-website/trunk/zope_history.rst)
===================================================================
--- zope-story-website/trunk/src/zope_history.rst (rev 0)
+++ zope-story-website/trunk/src/zope_history.rst 2009-03-30 21:24:33 UTC (rev 98637)
@@ -0,0 +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
+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
Deleted: zope-story-website/trunk/zope_history.rst
===================================================================
--- zope-story-website/trunk/zope_history.rst 2009-03-30 21:21:56 UTC (rev 98636)
+++ zope-story-website/trunk/zope_history.rst 2009-03-30 21:24:33 UTC (rev 98637)
@@ -1,29 +0,0 @@
-
-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
More information about the Checkins
mailing list