From cb4fbda4ac3cd5386d4aabb3c9a72d592ca2869d Mon Sep 17 00:00:00 2001 From: "R. Tyler Ballance" Date: Mon, 1 Jun 2009 10:46:54 -0700 Subject: Nuke a lot of the old site Signed-off-by: R. Tyler Ballance --- WikiRoot.html | 394 ---------------- WikiRoot.tmpl | 160 ------- buildwiki.py | 24 - community.html | 402 ----------------- community.tmpl | 29 -- developers.html | 423 ----------------- developers.tmpl | 58 --- docs.html | 447 ------------------ docs.tmpl | 93 ---- download.html | 407 ----------------- download.tmpl | 34 -- index.html | 500 --------------------- index.tmpl | 63 --- .../content/@staticmethod_and_@classmethod.html | 436 ------------------ .../@staticmethod_and_@classmethod.markdown | 52 --- recipes/content/Basic_Inheritance.html | 441 ------------------ recipes/content/Basic_Inheritance.markdown | 60 --- recipes/content/Precompiled_Templates.html | 438 ------------------ recipes/content/Precompiled_Templates.markdown | 58 --- recipes/content/Writing_A_Recipe.html | 395 ---------------- recipes/content/Writing_A_Recipe.markdown | 4 - recipes/index.html | 404 ----------------- recipes/index.tmpl | 76 ---- roadmap.html | 422 ----------------- roadmap.tmpl | 51 --- runwiki.py | 17 - 26 files changed, 5888 deletions(-) delete mode 100644 WikiRoot.html delete mode 100644 WikiRoot.tmpl delete mode 100644 buildwiki.py delete mode 100644 community.html delete mode 100644 community.tmpl delete mode 100644 developers.html delete mode 100644 developers.tmpl delete mode 100644 docs.html delete mode 100644 docs.tmpl delete mode 100644 download.html delete mode 100644 download.tmpl delete mode 100644 index.html delete mode 100644 index.tmpl delete mode 100644 recipes/content/@staticmethod_and_@classmethod.html delete mode 100644 recipes/content/@staticmethod_and_@classmethod.markdown delete mode 100644 recipes/content/Basic_Inheritance.html delete mode 100644 recipes/content/Basic_Inheritance.markdown delete mode 100644 recipes/content/Precompiled_Templates.html delete mode 100644 recipes/content/Precompiled_Templates.markdown delete mode 100644 recipes/content/Writing_A_Recipe.html delete mode 100644 recipes/content/Writing_A_Recipe.markdown delete mode 100644 recipes/index.html delete mode 100644 recipes/index.tmpl delete mode 100644 roadmap.html delete mode 100644 roadmap.tmpl delete mode 100644 runwiki.py diff --git a/WikiRoot.html b/WikiRoot.html deleted file mode 100644 index 4ac1173..0000000 --- a/WikiRoot.html +++ /dev/null @@ -1,394 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - WikiRoot - - - - - - - - - - -

- -

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - - diff --git a/WikiRoot.tmpl b/WikiRoot.tmpl deleted file mode 100644 index 65411da..0000000 --- a/WikiRoot.tmpl +++ /dev/null @@ -1,160 +0,0 @@ -#from Cheetah.Template import Template -#extends Template -#implements respond - -#attr PathPrefix = '' - -## (Name, Link, IsTab) -#set global $Pages = [ - ('Home', 'index.html', True), - ('Download', 'download.html', True), - ('Documentation', 'docs.html', True), - ('Recipes', 'recipes/', True), - ('Community', 'community.html', True), - ('Developers', 'developers.html', True), - ('Issues', 'http://bugs.communitycheetah.org', False), - ('Source', 'http://github.com/rtyler/cheetah/tree/master', False), - ('Roadmap', 'roadmap.html', False), - ] - - - - - Community Cheetah - The Python-Powered Template Engine - $pagename() - - - - - - - $css() - - $header() - - #if $leftsidebar() -

- - $leftsidebar() - -

- #end if - -

- $content() -

- -

- - $rightsidebar() - -

- -
-
- - $footer() - - - - - - -#def pagename() - #return "WikiRoot" -#end def - -#def leftsidebar() - #return '' -#end def - -#def rightsidebar() -

- -

- - follow Cheetah on Twitter -

-#end def - -#def header() - -

- -

Community Cheetah

- #for $Name, $Link, $IsTab in $Pages - #if $IsTab and not $Name == 'Home' - #continue - #end if - $Name | - #end for -

- -

- - $Name - -

-#end def - -#def footer() -

-
-
- -#end def - -#def _css() - #include raw "./stylesheet.css" -#end def - -#def css() - -#end def - -#def content() - #return '' -#end def diff --git a/buildwiki.py b/buildwiki.py deleted file mode 100644 index 777dde4..0000000 --- a/buildwiki.py +++ /dev/null @@ -1,24 +0,0 @@ -#!/usr/bin/env python - -import sys -import os - -def fullpath(folder, file): - return '%s%s%s' % (folder, os.path.sep, file) - -def main(): - print '==> Generating Python files' - for paths, dirs, files in os.walk('.'): - for file in files: - if file.endswith('.tmpl'): - os.system('cheetah compile %s' % fullpath(paths, file)) - print '==> Generating HTML files' - for paths, dirs, files in os.walk('.'): - for file in files: - if file.endswith('.tmpl'): - os.system('python %(file)s.py > %(file)s.html' % {'file' : fullpath(paths, file[:-5])}) - return 0 - -if __name__ == '__main__': - rc = main() - sys.exit(rc) diff --git a/community.html b/community.html deleted file mode 100644 index 86a7c41..0000000 --- a/community.html +++ /dev/null @@ -1,402 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Community - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Cheetah Community

Roadmap

You can review the Community Cheetah Roadmap for what's coming up.

Mailing List

The majority of Cheetah discussions occur on the Cheetah mailing list. -Once you've subscribed to the Cheetah mailing list, you can just send an email to cheetahtemplate-discuss@lists.sourceforge.net

IRC

You can also find Cheetah on Freenode in the #Cheetah IRC channel. The channel is currently low traffic, so if there -is nobody available to answer your questions on IRC, you may be better served pinging the mailing list.

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - - diff --git a/community.tmpl b/community.tmpl deleted file mode 100644 index bd409f8..0000000 --- a/community.tmpl +++ /dev/null @@ -1,29 +0,0 @@ -#import WikiRoot -#from Cheetah.Filters import Markdown -#extends WikiRoot.WikiRoot - -#def pagename() - #return 'Community' -#end def - -#def content() -#transform Markdown -Cheetah Community -===================== - -Roadmap -------- -You can review the [Community Cheetah Roadmap](roadmap.html) for what's coming up. - -Mailing List ------------- -The majority of Cheetah discussions occur on the [Cheetah mailing list](http://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss). -Once you've subscribed to the Cheetah mailing list, you can just send an email to **cheetahtemplate-discuss@lists.sourceforge.net** - - -IRC ---- -You can also find Cheetah on [Freenode](http://freenode.net) in the **\#Cheetah** IRC channel. The channel is currently low traffic, so if there -is nobody available to answer your questions on IRC, you may be better served pinging the mailing list. - -#end def diff --git a/developers.html b/developers.html deleted file mode 100644 index 46462e0..0000000 --- a/developers.html +++ /dev/null @@ -1,423 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Developers - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Contributing to Cheetah

Cheetah is the work of many volunteers. If you use Cheetah, share your experiences, tricks, customizations, and frustrations. -Please join the mailing list.

Fork Me!

Community Cheetah is hosted by GitHub which encourages forking of projects in order -to facilitate truly distributed and decentralized development. That is not to say that Community Cheetah is -"decentralized" per sé but rather it's ready for community involvement from the get-go! To get started -with contributing to Community Cheetah, it's a good idea to clone the "central" Git repo here.

Development Process

The typical development workflow for Community Cheetah revolves around two primary branches maint and next. -The next branch is where development planned for the next release of Community Cheetah is. The maint branch -on the otherhand is where backported fixes and patches will be applied for the current release of Community Cheetah -will go, it's common for a patch to be applied to maint and next at the same time.

Bug reports and patches

If you have stubmled across a bug or have an improvement to suggest in Cheetah please consider reporting -the issue into Community Cheetah's bug tracker or emailing the -mailing list.

Please try to include the following bits of information:

A description of what you were trying to do, and what happened (i.e. reproduction steps)
Any and all tracebacks or compiler errors
The version of Cheetah you're using
The version of Python you're using
The operating system you're running Cheetah on
Any other pieces of information you might think are relevant

Example sites and tutorials

If you're developing a website with Cheetah, please send a link to the email list so we can keep track of Cheetah sites. Also, if you discover new and interesting ways to use Cheetah please share your experience and write a quick tutorial about your technique.

Test cases

Cheetah is packaged with a regression testing suite that is run with each new release to ensure that everything is working as expected and that recent changes haven't broken anything. The test cases are in the Cheetah.Tests module. If you find a reproduceable bug please consider writing a test case that will pass only when the bug is fixed. Send any new test cases to the email list with the subject-line "new test case for Cheetah."

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - - diff --git a/developers.tmpl b/developers.tmpl deleted file mode 100644 index f5ecd6f..0000000 --- a/developers.tmpl +++ /dev/null @@ -1,58 +0,0 @@ -#import WikiRoot -#from Cheetah.Filters import Markdown -#extends WikiRoot.WikiRoot - -#def pagename() - #return 'Developers' -#end def - -#def content() -#transform Markdown -Contributing to Cheetah -======================== - -Cheetah is the work of many volunteers. If you use Cheetah, share your experiences, tricks, customizations, and frustrations. -Please join the [mailing list](http://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss). - -Fork Me! --------- -Community Cheetah is hosted by [GitHub](http://www.github.com) which encourages forking of projects in order -to facilitate truly distributed and decentralized development. That is not to say that Community Cheetah is -"decentralized" per sé but rather it's ready for community involvement from the get-go! To get started -with contributing to Community Cheetah, it's a good idea to clone the "central" Git repo [here](http://github.com/rtyler/cheetah). - -Development Process -------------------- -The typical development workflow for Community Cheetah revolves around two primary branches **maint** and **next**. -The **next** branch is where development planned for the next release of Community Cheetah is. The **maint** branch -on the otherhand is where backported fixes and patches will be applied for the *current* release of Community Cheetah -will go, it's common for a patch to be applied to **maint** and **next** at the same time. - - -Bug reports and patches ------------------------ - -If you have stubmled across a bug or have an improvement to suggest in Cheetah please consider reporting -the issue into Community Cheetah's [bug tracker](http://bugs.communitycheetah.org) or emailing the -[mailing list](http://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss). - -Please try to include the following bits of information: - -* A description of what you were trying to do, and what happened (i.e. reproduction steps) -* Any and all tracebacks or compiler errors -* The version of Cheetah you're using -* The version of Python you're using -* The operating system you're running Cheetah on -* Any other pieces of information you might think are relevant - -Example sites and tutorials ---------------------------- - -If you're developing a website with Cheetah, please send a link to the email list so we can keep track of Cheetah sites. Also, if you discover new and interesting ways to use Cheetah please share your experience and write a quick tutorial about your technique. - - -Test cases ----------- - -Cheetah is packaged with a regression testing suite that is run with each new release to ensure that everything is working as expected and that recent changes haven't broken anything. The test cases are in the Cheetah.Tests module. If you find a reproduceable bug please consider writing a test case that will pass only when the bug is fixed. Send any new test cases to the email list with the subject-line "new test case for Cheetah." -#end def diff --git a/docs.html b/docs.html deleted file mode 100644 index fc47f76..0000000 --- a/docs.html +++ /dev/null @@ -1,447 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Documentation - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Cheetah Documentation

Currently the Community Cheetah documentation is in a state-of flux, you can however -still refer to the older Cheetah v2.0.1 documentation for most of the basics

Unofficial Documentation and Articles

Building and filling out templates with Python and Cheetah by Leonard Richardson, Software Engineer -at CollabNet. Published in IBM Developer Works, August 9th, 2005. Leonard -Richardson is the author of many Python applications and libraries, including -NewsBruiser and Beautiful Soup. He is a co-author of the new tome Beginning -Python, from Wrox.

Python-Powered Templates with Cheetah -by Andrew Glover, founder and CTO of Vanward -Technologies, a company specializing in building automated testing frameworks. -Published in O'Reilly's ONLamp.com, January 13th, 2005

Templating with Cheetah -A DevShed article by Peyton McCullough. Published in December 2005.

Templating in Python A -Linux Gazette article by Mike Orr. Published in Issue 117 of Linux Gazette, -August 2005.

Regular Expressions: CherryPy proves its worth -An Unix Review article by Miki Tebeka and Cameron Laid. They build a small addressbook application in less -than 150 lines of code using the CherryPy web framework and Cheetah. -Published May 2006.

How to install Cheetah on Dreamhost -A blog article published by Bruce Kroeze in January 2006.

Tierisch gut Das Cheetah Templating-System in der Praxis -A German-language article by Markus Jais. Published in the -December 2004 edition of linuxenterprise.de

Python Success Stories: Python Enterprise-Wide at the University of St Andrews in Scotland -by Hamish Lawson. Cheetah is used for the presentation -layer. Hamish Lawson is a software developer in the IT Services department at -the University of St Andrews, Scotland. Published January 17th, 2003.

Code Generation Network - Case Study with Peter White -An interview that discusses using Cheetah for generating Java code in a financial services -application. "Given my recent experience with Python and Cheetah, I can't -imagine an easier way to generate code!" Published March 1st, 2004.

In Literature

Cheetah is covered in Python in a Nutshell -by Alex Martelli. Alex writes on the Cheetah list: "Nutshell -readers looking for templating engines will be tempted by my ultra-brief -coverage enough to come visit the Cheetah site and get stunned. Indeed, I'm -impressed enough that I plan to cover only Cheetah as the one tool for any -serious templating need."

It is also introduced in the New Riders book Python Web Programming -by Steve Holden. Steve writes "Although the software is still in beta at the -time of writing, it is already stable and easy to use either with or without -Webware. It looks as though Cheetah will be useful to many web projects, as -well as any others that need flexible template substitution of a general -nature." Published Jan 8th, 2002.

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - - diff --git a/docs.tmpl b/docs.tmpl deleted file mode 100644 index 998364f..0000000 --- a/docs.tmpl +++ /dev/null @@ -1,93 +0,0 @@ -#import WikiRoot -#from Cheetah.Filters import Markdown -#extends WikiRoot.WikiRoot - -#def pagename() - #return 'Documentation' -#end def - -#def content() -#transform Markdown -Cheetah Documentation -===================== - -Currently the Community Cheetah documentation is in a state-of flux, you can however -still refer to the older Cheetah v2.0.1 documentation for most of the basics - -* [Single-page HTML](http://www.cheetahtemplate.org/docs/users_guide_html/) -* [Multi-page HTML](http://www.cheetahtemplate.org/docs/users_guide_html_multipage/) -* [Text](http://www.cheetahtemplate.org/docs/users_guide.txt) -* [PDF](http://www.cheetahtemplate.org/docs/users_guide.pdf) - - -Unofficial Documentation and Articles -------------------------------------- - -[Building and filling out templates with Python and Cheetah](http://www-128.ibm.com/developerworks/opensource/library/os-pythcheetah/?ca=dgr-lnxw06PythonCheetah) by Leonard Richardson, Software Engineer -at CollabNet. Published in IBM Developer Works, August 9th, 2005. Leonard -Richardson is the author of many Python applications and libraries, including -NewsBruiser and Beautiful Soup. He is a co-author of the new tome Beginning -Python, from Wrox. - - -[Python-Powered Templates with Cheetah](http://www.onlamp.com/pub/a/python/2005/01/13/cheetah.html) -by Andrew Glover, founder and CTO of Vanward -Technologies, a company specializing in building automated testing frameworks. -Published in O'Reilly's ONLamp.com, January 13th, 2005 - - -[Templating with Cheetah](http://www.devshed.com/c/a/Python/Templating-with-Cheetah/) -A DevShed article by Peyton McCullough. Published in December 2005. - - -[Templating in Python](http://linuxgazette.net/117/orr.html) A -Linux Gazette article by Mike Orr. Published in Issue 117 of Linux Gazette, -August 2005. - - -[Regular Expressions: CherryPy proves its worth](http://www.unixreview.com/documents/s=10075/ur0604h/) -An Unix Review article by Miki Tebeka and Cameron Laid. They build a small addressbook application in less -than 150 lines of code using the CherryPy web framework and Cheetah. -Published May 2006. - - -[How to install Cheetah on Dreamhost](http://coderseye.com/2006/how-to-install-cheetah-on-dreamhost.html) -A blog article published by Bruce Kroeze in January 2006. - - -[Tierisch gut Das Cheetah Templating-System in der Praxis](http://www.linuxenterprise.de/itr/online_artikel/psecom,id,639,nodeid,9.html) -A German-language article by Markus Jais. Published in the -December 2004 edition of [linuxenterprise.de](http://www.linuxenterprise.de/) - - -[Python Success Stories: Python Enterprise-Wide at the University of St Andrews in Scotland](http://wingware.com/python/success/st-andrews) -by Hamish Lawson. Cheetah is used for the presentation -layer. Hamish Lawson is a software developer in the IT Services department at -the University of St Andrews, Scotland. Published January 17th, 2003. - - -[Code Generation Network - Case Study with Peter White](http://www.codegeneration.net/tiki-read_article.php?articleId=39) -An interview that discusses using Cheetah for generating Java code in a financial services -application. "Given my recent experience with Python and Cheetah, I can't -imagine an easier way to generate code!" Published March 1st, 2004. - - -In Literature -------------- - -Cheetah is covered in [Python in a Nutshell](http://www.amazon.com/exec/obidos/tg/detail/-/0596001886/ref=pd_sim_b_2/002-9262270-4252038?%5Fencoding=UTF8&v=glance) -by Alex Martelli. Alex writes on the Cheetah list: "Nutshell -readers looking for templating engines will be tempted by my ultra-brief -coverage enough to come visit the Cheetah site and get stunned. Indeed, I'm -impressed enough that I plan to cover _only_ Cheetah as the one tool for any -serious templating need." - - -It is also introduced in the New Riders book [Python Web Programming](http://www.informit.com/title/0735710902) -by Steve Holden. Steve writes "Although the software is still in beta at the -time of writing, it is already stable and easy to use either with or without -Webware. It looks as though Cheetah will be useful to many web projects, as -well as any others that need flexible template substitution of a general -nature." Published Jan 8th, 2002. - -#end def diff --git a/download.html b/download.html deleted file mode 100644 index 440031c..0000000 --- a/download.html +++ /dev/null @@ -1,407 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Downloads - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Cheetah Downloads

The most recent stable release of Community Cheetah is Cheetah v2.2.0 which was released -on May 17th, 2009. The most recent "mainstream" release of Cheetah (i.e. from SourceForge and the original -author) was released on November 16th, 2007 (v2.0.1).

Download v2.2.0

v2.2.0 tarball
v2.2.0 zip

You can keep up to date with release candidates, and other misc downloads provided by Community Cheetah -by visiting the GitHub downloads page

Important note to Windows users: You should install the compiled version of Cheetah's NameMapper. -It is dramatically faster than the pure Python version! Python 2.4: namemapper.pyd2.4, Python 2.5: namemapper.pyd2.5. -Install it wherever your system puts Cheetah/NameMapper.py. Strip the version numbers off the filename.

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - - diff --git a/download.tmpl b/download.tmpl deleted file mode 100644 index d975d53..0000000 --- a/download.tmpl +++ /dev/null @@ -1,34 +0,0 @@ -#import WikiRoot -#from Cheetah.Filters import Markdown -#extends WikiRoot.WikiRoot - -#def pagename() - #return 'Downloads' -#end def - -#def content() -#transform Markdown -#set currentVersion = 'v2.2.0' -#set releaseDate = 'May 17th, 2009' - -Cheetah Downloads -================= - -The most recent *stable* release of Community Cheetah is **Cheetah $currentVersion** which was released -on $releaseDate. The most recent "mainstream" release of Cheetah (i.e. from SourceForge and the original -author) was released on November 16th, 2007 (v2.0.1). - -Download $currentVersion --------------------------- -* [$currentVersion tarball](http://github.com/rtyler/cheetah/tarball/$currentVersion) -* [$currentVersion zip](http://github.com/rtyler/cheetah/zipball/$currentVersion) - -You can keep up to date with release candidates, and other misc downloads provided by Community Cheetah -by visiting the [GitHub downloads page](http://github.com/rtyler/cheetah/downloads) - - -**Important note to Windows users**: You should install the compiled version of Cheetah's NameMapper. -It is dramatically faster than the pure Python version! Python 2.4: _namemapper.pyd2.4, Python 2.5: _namemapper.pyd2.5. -Install it wherever your system puts Cheetah/NameMapper.py. Strip the version numbers off the filename. - -#end def diff --git a/index.html b/index.html deleted file mode 100644 index cc78dc3..0000000 --- a/index.html +++ /dev/null @@ -1,500 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Home - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Community Cheetah

Community Cheetah is the rebirth of the Cheetah Template engine. -The Cheetah Templating engine is a Python-powered templating engine -that can output or generate practically any text-based format (including Python itself!)

Cheetah already has a large and active user community, and there are a number of products built with Cheetah in the -Fortune 500, as well startups in Silicon Valley (like Slide and Yelp)

Cheetah in a nutshell

Below is a simple example of some Cheetah code, as you can see it's pretty much just Python. You can import, inherit and -define methods just like in a regular Python module, since that's what your Cheetah templates are compiled to :)

- - -

#from Cheetah.Template import Template
-#extends Template
-
-#set $people = [{'name' : 'Tom', 'mood' : 'Happy'}, {'name' : 'Dick', 'mood' : 'Sad'}, {'name' : 'Harry', 'mood' : 'Hairy'}]
-<strong>How are you feeling?</strong>
-<ul>
-    #for $person in $people
-        <li>
-            $person['name'] is $person['mood']
-        </li>
-    #end for
-</ul>
-

- -

Why should I use Cheetah?

Cheetah is supported by every major Python web framework.
It is fully documented and is supported by an active user community.
It can output/generate any text-based format.
Cheetah compiles templates into optimized, yet readable, Python code.
It blends the power and flexibility of Python with a simple template language that non-programmers can understand.
It gives template authors full access to any Python data structure, module, function, object, or method in their templates. Meanwhile, it provides a way for administrators to selectively restrict access to Python when needed.
Cheetah makes code reuse easy by providing an object-oriented interface to templates that is accessible from Python code or other Cheetah templates. One template can subclass another and selectively reimplement sections of it. Cheetah templates can be subclasses of any Python class and vice-versa.
It provides a simple, yet powerful, caching mechanism that can dramatically improve the performance of a dynamic website.
It encourages clean separation of content, graphic design, and program code. This leads to highly modular, flexible, and reusable site architectures, shorter development time, and HTML and program code that is easier to understand and maintain. It is particularly well suited for team efforts.
Cheetah can be used to generate static html via its command-line tool.

Why Community Cheetah?

The primary motivations for the Community Cheetah fork is to maintain active development outside of -the currently-stale Cheetah CVS tree. Community Cheetah -isn't meant to diverge from the main goals of Cheetah: speed, ease of use and stability, but rather Community -Cheetah is meant to reinvirgorate the community surrounding Cheetah and provide monthly releases incorporating -patches and improvements to the engine.

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - - diff --git a/index.tmpl b/index.tmpl deleted file mode 100644 index 2640e5d..0000000 --- a/index.tmpl +++ /dev/null @@ -1,63 +0,0 @@ -#import WikiRoot -#from Cheetah.Filters import Markdown, CodeHighlighter -#extends WikiRoot.WikiRoot - -#def pagename() - #return 'Home' -#end def - -#def nutshell() -#transform CodeHighlighter -\#from Cheetah.Template import Template -\#extends Template - -\#set \$people = [{'name' : 'Tom', 'mood' : 'Happy'}, {'name' : 'Dick', 'mood' : 'Sad'}, {'name' : 'Harry', 'mood' : 'Hairy'}] -How are you feeling? -

- \$person['name'] is \$person['mood'] -

-#end def - -#def content() -#transform Markdown -Community Cheetah -================= -Community Cheetah is the rebirth of the [Cheetah Template](http://www.cheetahtemplate.org/) engine. -The Cheetah Templating engine is a [Python](http://www.python.org)-powered templating engine -that can output or generate practically **any** text-based format (including Python itself!) - -Cheetah already has a large and active user community, and there are a number of products built with Cheetah in the -Fortune 500, as well startups in Silicon Valley (like [Slide](http://www.slide.com) and [Yelp](http://www.yelp.com)) - -Cheetah in a nutshell ---------------------- -Below is a simple example of some Cheetah code, as you can see it's *pretty much* just Python. You can import, inherit and -define methods just like in a regular Python module, since that's what your Cheetah templates are compiled to :) - -$nutshell() - -Why should I use Cheetah? -------------------------- -* Cheetah is supported by every major Python web framework. -* It is fully documented and is supported by an active user community. -* It can output/generate any text-based format. -* Cheetah compiles templates into optimized, yet readable, Python code. -* It blends the power and flexibility of Python with a simple template language that non-programmers can understand. -* It gives template authors full access to any Python data structure, module, function, object, or method in their templates. Meanwhile, it provides a way for administrators to selectively restrict access to Python when needed. -* Cheetah makes code reuse easy by providing an object-oriented interface to templates that is accessible from Python code or other Cheetah templates. One template can subclass another and selectively reimplement sections of it. Cheetah templates can be subclasses of any Python class and vice-versa. -* It provides a simple, yet powerful, caching mechanism that can dramatically improve the performance of a dynamic website. -* It encourages clean separation of content, graphic design, and program code. This leads to highly modular, flexible, and reusable site architectures, shorter development time, and HTML and program code that is easier to understand and maintain. It is particularly well suited for team efforts. -* Cheetah can be used to generate static html via its command-line tool. - -Why Community Cheetah? ----------------------- -The primary motivations for the Community Cheetah fork is to maintain *active* development outside of -the currently-stale [Cheetah CVS tree](http://sourceforge.net/scm/?type=cvs&group_id=28961). Community Cheetah -isn't meant to diverge from the main goals of Cheetah: speed, ease of use and stability, but rather Community -Cheetah is meant to reinvirgorate the community surrounding Cheetah and provide **monthly** releases incorporating -patches and improvements to the engine. -#end def diff --git a/recipes/content/@staticmethod_and_@classmethod.html b/recipes/content/@staticmethod_and_@classmethod.html deleted file mode 100644 index 30e622e..0000000 --- a/recipes/content/@staticmethod_and_@classmethod.html +++ /dev/null @@ -1,436 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - @staticmethod_and_@classmethod - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

@staticmethod and @classmethod

Refer the Python's documentation if you're unfamiliar with either -@staticmethod or @classmethod and their uses in Python, as they -pertain to their uses in Cheetah as well. Using @staticmethod it's -trivial to create utility templates which are common when using -Cheetah for web development. These utility templates might contain -a number of small functions which generate useful snippets of markup.

For example:

#def copyright()
-    #import time
-    &copy; CheetahCorp, Inc. $time.strftime('%Y', time.gmtime())
-#end def
-

Figure 1, util.tmpl

Prior to version v2.2.0 of Cheetah, there wasn't really an easy means -of filling templates with bunches of these small utility functions. In -v2.2.0 however, you can decorate these methods with #@staticmethod -and use "proper" Python syntax for calling them, fig 1 revisited:

#@staticmethod
-#def copyright()
-    #import time
-    &copy; CheetahCorp, Inc. $time.strftime('%Y', time.gmtime())
-#end def
-

Figure 1.1, util.tmpl

With the addition of the @staticmethod decorator, the copyright() -function can now be used without instantiating an instance of the util -template class. In effect:

#from util import util
-
-<strong>This is my page</strong>
-<br/>
-<hr noshade/>
-$util.copyright()
-

Figure 2, index.tmpl

This approach is however no means to structure anything complex, -@staticmethod and @classmethod use in Cheetah is not meant as a -replacement for properly structured class hierarchies (which -Cheetah supports). That said if you are building a web application -@staticmethod/@classmethod are quite useful for the little snippets -of markup, etc that are needed (Google AdSense blocks, footers, -banners, etc).

Last edited: Sun May 31 18:40:24 2009

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - diff --git a/recipes/content/@staticmethod_and_@classmethod.markdown b/recipes/content/@staticmethod_and_@classmethod.markdown deleted file mode 100644 index de2f995..0000000 --- a/recipes/content/@staticmethod_and_@classmethod.markdown +++ /dev/null @@ -1,52 +0,0 @@ -@staticmethod and @classmethod -============================== -#set $staticmethod = '[@staticmethod](http://docs.python.org/library/functions.html#staticmethod)' -#set $classmethod = '[@classmethod](http://docs.python.org/library/functions.html#classmethod)' - -Refer the Python's documentation if you're unfamiliar with either -$staticmethod or $classmethod and their uses in Python, as they -pertain to their uses in Cheetah as well. Using $staticmethod it's -trivial to create *utility templates* which are common when using -Cheetah for web development. These *utility templates* might contain -a number of small functions which generate useful snippets of markup. - -For example: - - \#def copyright() - \#import time - © CheetahCorp, Inc. \$time.strftime('%Y', time.gmtime()) - \#end def -**Figure 1, util.tmpl** - -Prior to version **v2.2.0** of Cheetah, there wasn't really an easy means -of filling templates with bunches of these small utility functions. In -**v2.2.0** however, you can decorate these methods with `\#@staticmethod` -and use "proper" Python syntax for calling them, **fig 1** revisited: - - \#@staticmethod - \#def copyright() - \#import time - © CheetahCorp, Inc. \$time.strftime('%Y', time.gmtime()) - \#end def -**Figure 1.1, util.tmpl** - -With the addition of the $staticmethod decorator, the `copyright()` -function can now be used without instantiating an instance of the `util` -template class. In effect: - - \#from util import util - - This is my page -
-

- \$util.copyright() -**Figure 2, index.tmpl** - - -This approach is however no means to structure anything complex, -$staticmethod and $classmethod use in Cheetah is not meant as a -replacement for properly structured class hierarchies (which -Cheetah supports). That said if you are building a web application -$staticmethod/$classmethod are quite useful for the little snippets -of markup, etc that are needed (Google AdSense blocks, footers, -banners, etc). diff --git a/recipes/content/Basic_Inheritance.html b/recipes/content/Basic_Inheritance.html deleted file mode 100644 index 1331ecd..0000000 --- a/recipes/content/Basic_Inheritance.html +++ /dev/null @@ -1,441 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Basic_Inheritance - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Basic Inheritance

Introduction

Cheetah, like Python, is an object-oriented language if you so choose to -use it in that fashion. That is to say that you can use Cheetah in with -object-oriented principles or you can use Cheetah in a strictly functional -sense, like Python, Cheetah does not place restrictions on these barriers.

While Cheetah is not strictly Python, it was designed as such to interoperate, -particularly with the notion of classes, with Python itself. In effect you can -define Python classes that inherit and extend from Cheetah-derived classes and -vice versa. For this, Cheetah defines a few directives (denoted with the # -hash-mark) that are of some help, the most important one being the #extends -directive, with others playing important roles like #import, #attr and #super

In this recipe/tutorial I intend to explain and define a few key inheritance -patterns with Cheetah, being:

A Cheetah Template inheriting from Python
Python inheriting from a Cheetah Template
Cheetah Templates and "mixins"

This document also operates on the assumption that the reader is at least -somewhat familiar with the basic tenets of object-oriented programming in -Python.

Cheetah inheriting from Python

Whether or not you are aware of it, Cheetah templates are always inheriting from -a Python class by default. Unless otherwise denoted, Cheetah templates are compiled -to Python classes that subclass from the Cheetah.Template.Template class.

What if you would like to introduce your own Template base class? Easily acheived by -defining your own Template class in a Python module, for example:

import Cheetah.Template
-
-class CookbookTemplate(Cheetah.Template.Template):
-    _page = 'Cookbook'
-    author = 'R. Tyler Ballance'
-    def pageName(self):
-        return self._page or 'Unknown'
-

Figure 1. cookbook.py

For this example, I want all my subclasses of the CookbookTemplate to define a -page author which will be used in some shared rendering code, to accomplish this -my templates will need to subclass from CookbookTemplate explicitly instead of -implicitly subclassing from Cheetah.Template.Template

#import cookbook
-#extends cookbook.CookbookTemplate
-#attr author = 'Tavis Rudd'
-
-## The rest of my recipe template would be below
-

Figure 2. recipe1.tmpl

Last edited: Sun May 31 18:40:24 2009

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - diff --git a/recipes/content/Basic_Inheritance.markdown b/recipes/content/Basic_Inheritance.markdown deleted file mode 100644 index 19eaac0..0000000 --- a/recipes/content/Basic_Inheritance.markdown +++ /dev/null @@ -1,60 +0,0 @@ -Basic Inheritance -================= - -Introduction ------------- -Cheetah, like Python, is an object-oriented language if you so choose to -use it in that fashion. That is to say that you can use Cheetah in with -object-oriented principles *or* you can use Cheetah in a strictly functional -sense, like Python, Cheetah does not place restrictions on these barriers. - -While Cheetah is not strictly Python, it was designed as such to interoperate, -particularly with the notion of classes, with Python itself. In effect you can -define Python classes that inherit and extend from Cheetah-derived classes and -vice versa. For this, Cheetah defines a few **directives** (denoted with the `\#` -hash-mark) that are of some help, the most important one being the `\#extends` -directive, with others playing important roles like `\#import`, `\#attr` and `\#super` - -In this recipe/tutorial I intend to explain and define a few key inheritance -patterns with Cheetah, being: - -* A Cheetah Template inheriting from Python -* Python inheriting from a Cheetah Template -* Cheetah Templates and "*mixins*" - -This document also operates on the assumption that the reader is at least -somewhat familiar with the basic tenets of object-oriented programming in -Python. - - -Cheetah inheriting from Python ------------------------------- -Whether or not you are aware of it, Cheetah templates are always inheriting from -a Python class by default. Unless otherwise denoted, Cheetah templates are compiled -to Python classes that subclass from the `Cheetah.Template.Template` class. - -What if you would like to introduce your own Template base class? Easily acheived by -defining your own Template class in a Python module, for example: - - import Cheetah.Template - - class CookbookTemplate(Cheetah.Template.Template): - _page = 'Cookbook' - author = 'R. Tyler Ballance' - def pageName(self): - return self._page or 'Unknown' -**Figure 1. cookbook.py** - -For this example, I want all my subclasses of the `CookbookTemplate` to define a -page author which will be used in some shared rendering code, to accomplish this -my templates will need to subclass from `CookbookTemplate` explicitly instead of -implicitly subclassing from `Cheetah.Template.Template` - - \#import cookbook - \#extends cookbook.CookbookTemplate - \#attr author = 'Tavis Rudd' - - \#\# The rest of my recipe template would be below -**Figure 2. recipe1.tmpl** - - diff --git a/recipes/content/Precompiled_Templates.html b/recipes/content/Precompiled_Templates.html deleted file mode 100644 index 08ed9c2..0000000 --- a/recipes/content/Precompiled_Templates.html +++ /dev/null @@ -1,438 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Precompiled_Templates - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Precompiled Templates

Why bother?

Since Cheetah supports two basic modes: dynamic and precompiled templates, you have -a lot of options when it comes to utilizing Cheetah, particularly in web environments.

There is added speed to be gained by using pre-compiled templates, especially when -using mod_python with Apache. Precompiling your templates means Apache/mod_python -can load your template's generated module into memory and then execution is only -limited by the speed of the Python being executed, and not the Cheetah compiler. -You can further optimize things by then pre-compiling the generated Python files -(.py) down to Python byte-code (.pyc) so save cycles interpreting the Python.

Basic Pre-compilation

Suppose you have a template that looks something like this:

#attr title = "This is my Template"
-<html>
-    <head>
-        <title>${title}</title>
-    </head>
-    <body>
-        Hello ${who}!
-    </body>
-</html>
-

Figure 1. hello.tmpl

In order to compile this down to a Python file, you need to only execute the -cheetah compile hello.tmpl command. The results will be a Python file (.py) -which you can then treat as any other Python module in your code base.

Importing and lookup

Typically for the template in Figure 1, I could easily import it post-compilation -as any other Python module:

from templates import hello
-
-def myMethod():
-    tmpl = hello.hello(searchList=[{'who' : 'world'}])
-    results = tmpl.respond()
-

Figure 2. runner.py

Note: If you use the #implements directive, respond may not be your "main -method" for executing the Cheetah template. You can adjust the example above in -Figure 2 by using getattr() to make the lookup of the main method dynamic:

def myMethod():
-    tmpl = hello.hello(searchList=[{'who' : 'world'}])
-    mainMethod = getattr(tmpl, '_mainCheetahMethod_for_%s' % tmpl.__class__.__name__)
-    results = getattr(tmpl, mainMethod)()
-

Figure 3. Dynamic runner.py

Last edited: Sun May 31 18:40:24 2009

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - diff --git a/recipes/content/Precompiled_Templates.markdown b/recipes/content/Precompiled_Templates.markdown deleted file mode 100644 index 3849d16..0000000 --- a/recipes/content/Precompiled_Templates.markdown +++ /dev/null @@ -1,58 +0,0 @@ -Precompiled Templates -===================== - -Why bother? ------------ -Since Cheetah supports two basic modes: dynamic and precompiled templates, you have -a lot of options when it comes to utilizing Cheetah, particularly in web environments. - -There is added speed to be gained by using pre-compiled templates, especially when -using mod_python with Apache. Precompiling your templates means Apache/mod_python -can load your template's generated module into memory and then execution is only -limited by the speed of the Python being executed, and not the Cheetah compiler. -You can further optimize things by then pre-compiling the generated Python files -(.py) down to Python byte-code (.pyc) so save cycles interpreting the Python. - - -Basic Pre-compilation ---------------------- -Suppose you have a template that looks something like this: - - \#attr title = "This is my Template" - - - \${title} - - - Hello \${who}! - - -**Figure 1. hello.tmpl** - -In order to compile this down to a Python file, you need to only execute the -`cheetah compile hello.tmpl` command. The results will be a Python file (.py) -which you can then treat as any other Python module in your code base. - - -Importing and lookup --------------------- -Typically for the template in *Figure 1*, I could easily import it post-compilation -as any other Python module: - - from templates import hello - - def myMethod(): - tmpl = hello.hello(searchList=[{'who' : 'world'}]) - results = tmpl.respond() -**Figure 2. runner.py** - -*Note:* If you use the `\#implements` directive, `respond` may not be your "main -method" for executing the Cheetah template. You can adjust the example above in -*Figure 2* by using `getattr()` to make the lookup of the main method dynamic: - - def myMethod(): - tmpl = hello.hello(searchList=[{'who' : 'world'}]) - mainMethod = getattr(tmpl, '_mainCheetahMethod_for_%s' % tmpl.__class__.__name__) - results = getattr(tmpl, mainMethod)() -**Figure 3. Dynamic runner.py** - diff --git a/recipes/content/Writing_A_Recipe.html b/recipes/content/Writing_A_Recipe.html deleted file mode 100644 index e78b003..0000000 --- a/recipes/content/Writing_A_Recipe.html +++ /dev/null @@ -1,395 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Writing_A_Recipe - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Writing a "Recipe"

I'll fill this out soon enough :)

Last edited: Sun May 31 18:40:24 2009

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - diff --git a/recipes/content/Writing_A_Recipe.markdown b/recipes/content/Writing_A_Recipe.markdown deleted file mode 100644 index 1a00001..0000000 --- a/recipes/content/Writing_A_Recipe.markdown +++ /dev/null @@ -1,4 +0,0 @@ -Writing a "Recipe" -================= - -I'll fill this out soon enough :) diff --git a/recipes/index.html b/recipes/index.html deleted file mode 100644 index 4542cca..0000000 --- a/recipes/index.html +++ /dev/null @@ -1,404 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Recipes - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Cheetah Recipes

Here are the available recipes thus far:

If you're really hungry for some Cheetah recipies, you can check out the -out-of-date Cheetah recipes page -from the old Wiki

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - - diff --git a/recipes/index.tmpl b/recipes/index.tmpl deleted file mode 100644 index c1808b6..0000000 --- a/recipes/index.tmpl +++ /dev/null @@ -1,76 +0,0 @@ -#compiler-settings -useAutocalling=False -useLegacyImportMode=False -#end compiler-settings - -#import os -#import time -#From Cheetah.Template import Template -#from Cheetah.Filters import Markdown - -#import WikiRoot -#extends WikiRoot.WikiRoot - -#attr PathPrefix = '../' -#attr ExecuteContentPath = 'recipes/content/' -#attr HyperlinkContentPath = 'content/' - -#def pagename() - #return 'Recipes' -#end def - -#def content() -#transform Markdown -Cheetah Recipes -=============== - -Here are the available recipes thus far: - -#for dirpath, dirnames, filenames in $os.walk($ExecuteContentPath) - #for file in filenames - #if file.endswith('.markdown') and $generateRecipePage($file) -* [${file.replace('_', ' ').replace('.markdown', '')}](${HyperlinkContentPath}${file.replace('.markdown', '.html')}) - #end if - #end for -#end for - - -If you're really hungry for some Cheetah recipies, you can check out the -out-of-date [Cheetah recipes page](http://wiki.cheetahtemplate.org/cheetah-recipes.html?) -from the old Wiki -#end def - -#def generateRecipePage(filepath) - ## Open and read in the .markdown document - #set fd = open('%s%s' % ($ExecuteContentPath, filepath), 'r') - #set content = fd.readlines() - #silent fd.close() - - #set tmpl = Template(''' -#from Cheetah.Filters import Markdown -#import WikiRoot -#extends WikiRoot.WikiRoot -#attr PathPrefix = '../../' -#def pagename() - #return $PageName -#end def - -#def content -#transform Markdown -%s - - - -*Last edited: $Edited * -#end def - ''' % (''.join(content)), - searchList=[{'Edited' : time.ctime(), 'PageName' : filepath.replace('.markdown', '')}]) - - ## Write the results of the template's execution to a .html file - #set fd = open('%s%s' % ($ExecuteContentPath, filepath.replace('.markdown', '.html')), 'w') - #silent fd.write(unicode(tmpl).encode('utf-8')) - #silent fd.close() - - #return True -#end def - diff --git a/roadmap.html b/roadmap.html deleted file mode 100644 index ea59afe..0000000 --- a/roadmap.html +++ /dev/null @@ -1,422 +0,0 @@ - - - - - - - Community Cheetah - The Python-Powered Template Engine - Roadmap - - - - - - - - - - -

- -

Community Cheetah

- Home | - Issues | - Source | - Roadmap | -

- -

- - - -

Community Cheetah Roadmap

Overview

The general intention of this document is to outline planned -development for Community Cheetah

Cheetah v2.2

The v2.2 release of the Cheetah is a minor change as far as the code-level -changes are concerned but has much farther reaching implications. These -changes currently reside in the unicode branch

Moving internal representation of source inside the compiler/parser -to unicode() objects instead of a potential mix of str() and unicode() -objects
Modify the implications of the #encoding directive to determine -the encoding to use when writing out the generated Python module

Cheetah v2.3

Still in planning

Planned for the third "major" release of Community Cheetah is an internal reworking -of the Cheetah compiler/parser/template code and the resulting Python they generate.

Analyze runtime performance of template execution
Update internal objects to "new-style" objects to prepare for moving towards Python 3000
"Modernize" other aspects of Cheetah infrastructure

Cheetah v3.0

Still in planning

Upgrade Cheetah to be fully Python 2.xx and 3.xx compatible

- -

- - follow Cheetah on Twitter -

- - -

- -
-
- -

-
-
- - - - - - - - - - - - - - - - diff --git a/roadmap.tmpl b/roadmap.tmpl deleted file mode 100644 index 9302a6d..0000000 --- a/roadmap.tmpl +++ /dev/null @@ -1,51 +0,0 @@ -#import WikiRoot -#from Cheetah.Filters import Markdown -#extends WikiRoot.WikiRoot - -#def pagename() - #return 'Roadmap' -#end def - -#def content() -#transform Markdown -Community Cheetah Roadmap -========================= - -Overview --------- -The general intention of this document is to outline planned -development for Community Cheetah - - -Cheetah v2.2 ------------- -The v2.2 release of the Cheetah is a minor change as far as the code-level -changes are concerned but has much farther reaching implications. These -changes currently reside in the [unicode branch](http://github.com/rtyler/cheetah/tree/unicode) - -- Moving internal representation of source inside the compiler/parser -to unicode() objects instead of a potential mix of str() and unicode() -objects -- Modify the implications of the \#encoding directive to determine -the encoding to use when writing out the generated Python module - - -Cheetah v2.3 ------------- -*Still in planning* - -Planned for the third "major" release of Community Cheetah is an internal reworking -of the Cheetah compiler/parser/template code and the resulting Python they generate. - -- Analyze runtime performance of template execution -- Update internal objects to "new-style" objects to prepare for moving towards Python 3000 -- "Modernize" other aspects of Cheetah infrastructure - - -Cheetah v3.0 ------------- -*Still in planning* - -- Upgrade Cheetah to be fully Python 2.xx and 3.xx compatible - -#end def diff --git a/runwiki.py b/runwiki.py deleted file mode 100644 index c86a745..0000000 --- a/runwiki.py +++ /dev/null @@ -1,17 +0,0 @@ -#!/usr/bin/env python - -import sys -import os -import SimpleHTTPServer - -def main(): - print '==> Starting wiki server on port 8000' - try: - SimpleHTTPServer.test() - except KeyboardInterrupt: - print '===> Exiting..' - return 0 - -if __name__ == '__main__': - rc = main() - sys.exit(rc) -- cgit v1.2.1

Twitter Updates

Twitter Updates

Cheetah Community

Roadmap

Mailing List

IRC

Twitter Updates

Contributing to Cheetah

Fork Me!

Development Process

Bug reports and patches

Example sites and tutorials

Test cases

Twitter Updates

Cheetah Documentation

Unofficial Documentation and Articles

In Literature

Twitter Updates

Cheetah Downloads

Download v2.2.0

Twitter Updates

Community Cheetah

Cheetah in a nutshell

Why should I use Cheetah?

Why Community Cheetah?

Twitter Updates

@staticmethod and @classmethod

Twitter Updates

Basic Inheritance

Introduction

Cheetah inheriting from Python

Twitter Updates

Precompiled Templates

Why bother?

Basic Pre-compilation

Importing and lookup

Twitter Updates

Writing a "Recipe"

Twitter Updates

Cheetah Recipes

Twitter Updates

Community Cheetah Roadmap

Overview

Cheetah v2.2

Cheetah v2.3

Cheetah v3.0

Twitter Updates