<?xml version="1.0" encoding="iso-8859-1" ?>
<rss version="2.0" 
   xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" 
   xmlns:html="http://www.w3.org/1999/html" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
<channel>
   <title>PyBlosxom - main site</title>
   <link></link>
   <description>PyBlosxom project web-site</description>
   <language>en</language>
   <copyright></copyright>
   <ttl>60</ttl>
   <pubDate>Wed, 16 Mar 2011 14:55 GMT</pubDate>
   <managingEditor>pyblosxom-users@lists.sourceforge.net</managingEditor>
   <generator>PyBlosxom http://pyblosxom.bluesock.org/ 1.5-dev git-master</generator>
<item>
   <title>Welcome to PyBlosxom!</title>
   <guid isPermaLink="false">pages/frontpage</guid>
   <link>/pages/frontpage.</link>
   <description><![CDATA[
<!-- PAGES PAGE START -->


<h2>What is PyBlosxom?</h2>
<p>
  PyBlosxom is a lightweight file-based weblog system.  PyBlosxom
  focuses on three things: simplicity, extensibility, and community.
</p>

<ul>
<li><b>simplicity</b> - PyBlosxom uses the file system for all its
  data storage.  Because of this you can use whatever existing
  editor, scripts and tools you want to create, update and
  manipulate entries and other blog data.
<li><b>extensibility</b> - PyBlosxom has a plugin framework allowing
  you to build plugins in Python to augment and change PyBlosxom's
  default behavior.
<li><b>community</b> - There are hundreds of PyBlosxom users out there
  all of whom have different needs.  PyBlosxom is used on a variety
  of operating systems in a variety of environments.  The pyblosxom
  users list shares their experiences, plugins, and expertise.  The
  pyblosxom devel list shares their ideas for changes, patches and
  plugins.
</ul>

<h2>Features</h2>
<ul>
<li>run it as a static renderer to compile your blog to html
<li>run as a CGI script
<li>run as a WSGI application
<li>lots of plugins that modify and extend behavior
<li>RSS 2.0 and Atom syndication feeds
<li>category and date-based archives and feeds
</ul>

<p>
  PyBlosxom allows you to use your existing editor, toolset and
  workflow to maintain your blog without forcing you to build it all
  from scratch.
</p>

<h2>Quickstart</h2>
<pre>
 $ pip install pyblosxom
 $ pyblosxom-cmd create ./blog
 $ cd blog
 $ paster serve blog.ini
</pre>

<h2>Project information</h2>

<ul>
<li>Git repository: <a href="http://gitorious.org/pyblosxom/" class="menulink">http://gitorious.org/pyblosxom/</a>
<li>References/specifications: <a href="/static/reference.html" class="menulink">references/specs</a><br />
<li>IRC: <tt>#pyblosxom</tt> on freenode.net
<li>mailing lists
<ul>
<li><b>pyblosxom-users</b> -
  pyblosxom-users at lists dot sourceforge dot net
  (<a href="http://lists.sourceforge.net/lists/listinfo/pyblosxom-users">subscribe/unsubscribe</a>)
  (<a href="http://news.gmane.org/gmane.comp.web.pyblosxom.user">archives</a>)
  <br />
  This mailing list is for users who are having problems installing or
  configuring PyBlosxom.  It can also be used for questions, comments, bugs,
  ideas, and things of that nature as well.
  <br />
  The GMANE archives have RSS links if you're interested in following along
  that way.
  </li>

  <li><b>pyblosxom-devel</b> - 
  pyblosxom-devel at lists dot sourceforge dot net
  (<a href="http://lists.sourceforge.net/lists/listinfo/pyblosxom-devel">subscribe/unsubscribe</a>)
  (<a href="http://news.gmane.org/gmane.comp.web.pyblosxom.devel">archives</a>)
  <br />
  This mailing list is for developers who want to add/modify/delete
  functionality in PyBlosxom.  Since it revolves around PyBlosxom development,
  it's also a good place to ask questions about how to build plugins and
  for advice on working around various plugin development issues.
  <br />
  The GMANE archives have RSS links if you're interested in following along
  that way.
  </li>
</ul>
</ul>

<h2>Interested in contributing?</h2>
<div style="margin: 10px; padding-bottom: 10px;">
<form method="POST" action="https://openhatch.org/+do/project.views.wanna_help_do" id="openhatch-want2help_form">
            <input type="hidden" name="from_offsite" value="True" />
            <input type="hidden" value="61" name="project"/>
            <input type="submit" value="I want to help" rel="tipsy-south" id="openhatch-wannahelp-button" original-title="Click to add yourself to the list of people who want to contribute. People of all levels are welcome!"/>
</form>

<style>
  @import url('https://openhatch.org/static/css/tipsy.css?1269539648');
</style>

<style type="text/css">
#openhatch-wannahelp-button:hover, #openhatch-wannahelp-button:focus {
background-image:url('https://openhatch.org/static/images/wannahelp-button-bg-hover.png');
color:#222222;
text-decoration:none;
}
#openhatch-wannahelp-button {
-moz-background-clip:border;
-moz-background-inline-policy:continuous;
-moz-background-origin:padding;
background:#C8E29D url('https://openhatch.org/static/images/wannahelp-button-bg.png') repeat-x scroll center top;
border:3px solid #FFFFFF;
cursor:pointer;
font-family:Helvetica,sans-serif;
font-size:13pt;
font-weight:normal;
text-align:center;
text-shadow:0 1px 0 #FFFFFF;
white-space:normal;
}

#openhatch-wannahelp-button {
-moz-border-radius-bottomleft:8px;
-moz-border-radius-bottomright:8px;
-moz-border-radius-topleft:8px;
-moz-border-radius-topright:8px;
color:#444444;
float:left;
padding:10px 20px;
display:block;
padding:2px 8px;
}

#openhatch-wannahelp-button:focus {
outline-color:-moz-use-text-color;
outline-style:none;
outline-width:medium;
}
</style>

<script type="text/javascript" src="https://openhatch.org/static/js/jquery.js?1244261870"></script>
<script type="text/javascript" src="https://openhatch.org/static/js/jquery.tipsy.js?1269539649"></script>
<script type="text/javascript" src="https://openhatch.org/static/js/tipsy-onload.js"></script>
</div>


<!-- PAGES PAGE END -->

]]></description>
   <category domain=""></category>
   <pubDate>Wed, 16 Mar 2011 14:55 GMT</pubDate>
</item>
</channel>
</rss>

