We have a page and a design!
[philo.git] / index.html
1 <!DOCTYPE html>
2
3 <html>
4         <head>
5                 <title>Philo</title>
6                 <link rel="stylesheet" type="text/css" href="static/css/screen.css" media="screen" />
7                 <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.6.0/jquery.min.js"></script>
8                 <script src="static/js/init.js"></script>
9         </head>
10         <body>
11                 <div id="container">
12                         <header id="nameplate">
13                                 <h1>Philo</h1>
14                         </header><!-- /#nameplate -->
15                         
16                         <div id="content">
17                                 <p>Philo is a powerful content-management system built with Django.</p>
18                         
19                                 <h2 id="features">Features</h2>
20                         
21                                 <p>Philo allows the creation of complex site structures from Django&#8217;s web-based admin interface (or any other database-editing interface). For a simple site, you will use the following three objects, included in the Philo core.</p>
22                         
23                                 <ul>
24                                 <li><strong>Nodes</strong> are the basic building blocks of a website using Philo. They define the URL hierarchy and connect each URL to a View subclass instance which is used to generate an HttpResponse.</li>
25                                 <li><strong>Templates</strong> are Django templates, stored in the database and editable from the Django admin (or similar).</li>
26                                 <li><strong>Pages</strong> are a simple view subclass which return a basic HTML page according to a template. They have related, editable Contentlets and Content References based on {% container %} tags used in the template.</li>
27                                 </ul>
28                         
29                                 <p>Philo also provides a number of useful template tags, in particular <code>{% container &lt;name&gt; %}</code>, which generates a relationship (and a field in the admin interface) on any pages which use that template.</p>
30                         
31                                 <h2>A Simple Example</h2>
32                         
33                                 <div class="three-up">
34                                         <figure>
35                                                 <img src="static/img/container1.png" />
36                                                 <figcaption>Put container tags in your template.</figcaption>
37                                         </figure>
38                                         <figure>
39                                                 <img src="static/img/container2.png" />
40                                                 <figcaption>Edit the contentlets on the page.</figcaption>
41                                         </figure>
42                                         <figure>
43                                                 <img src="static/img/container3.png" />
44                                                 <figcaption>See the results on your site!</figcaption>
45                                         </figure>
46                                 </div>
47                         
48                                 <p>You can use also collections, redirects, files, content references (all included in the Philo core), as well as the Philo contrib apps and your own code to create and manage more powerful, complex websites.</p>
49                         
50                                 <h2 id="batteries_included">Batteries Included</h2>
51                         
52                                 <p>Following Python and Django&#8217;s <a href="http://docs.python.org/tutorial/stdlib.html#batteries-included">&ldquo;batteries included&rdquo; philosophy</a>, Philo includes a number of optional packages that simplify common website structures. These are stored in philo.contrib and include:</p>
53                         
54                                 <ul id="contribList">
55                                         <li>
56                                                 <span class="name">Penfield</span>
57                                                 <span class="description">Blog and newsletter management.</span>
58                                         </li>
59                                         <li>
60                                                 <span class="name">Shipherd</span>
61                                                 <span class="description">Powerful site-navigation.</span>
62                                         </li>
63                                         <li>
64                                                 <span class="name">Sobol</span>
65                                                 <span class="description">Custom search-engines.</span>
66                                         </li>
67                                         <li>
68                                                 <span class="name">Waldo</span>
69                                                 <span class="description">Custom authentication systems.</span>
70                                         </li>
71                                         <li>
72                                                 <span class="status">(in development)</span>
73                                                 <span class="name">Gilbert</span>
74                                                 <span class="description">Alternative web-based admin.</span>
75                                         </li>
76                                         <li>
77                                                 <span class="status">(in development)</span>
78                                                 <span class="name">Julian</span>
79                                                 <span class="description">Calendar and events system.</span>
80                                         </li>
81                                         <li>
82                                                 <span class="status">(planned)</span>
83                                                 <span class="description">Forums.</span>
84                                         </li>
85                                         <li>
86                                                 <span class="status">(planned)</span>
87                                                 <span class="description">Wikis.</span>
88                                         </li>
89                                 </ul>
90                                 
91                         </div><!-- /#content -->
92                         
93                 </div>
94         </body>
95 </html>