RubyGems - gettalong-webgen - Versions diffs - 0.5.4.20080929 - Mend

@@ -0,0 +1,6 @@
+description:
+  Provides a minimalistic default style. The style defines a horizontal header, a horizontal bar with
+  the breadcrumb trail and the language menu, then a menu on the left and a footer.
+author:
+  Thomas Leitner

data/data/webgen/website_styles/simple/src/default.css ADDED Viewed

@@ -0,0 +1,84 @@
+#all { background-color: #CCCCCC; }
+#header {
+  border-bottom: 1px solid black;
+  padding: 1ex;
+  background-color: #888888;
+}
+#header h1 {
+  margin: 0ex;
+  font-size: 300%;
+  font-style: italic;
+  font-weight: normal;
+}
+#headerbar { border-bottom: 1px solid black; }
+#footer { border-top: 1px solid black; }
+#body {
+  margin-left: 250px;
+  margin-right: 20px;
+  padding: 10px;
+}
+#menu {
+  float: left;
+  width: 230px;
+  padding: 20px 0px 0px 2px;
+}
+.bar {
+  clear: both;
+  padding: 3px;
+  text-align: center;
+  font-size: 90%;
+  background-color: #AAAAAA;
+}
+.left, .right {
+  padding: 0px 1em;
+}
+.left {
+  float: left;
+  text-align: left;
+}
+.right {
+  float: right;
+  text-align: right;
+}
+/* styling the menu */
+#menu a, #menu span {
+  text-decoration: none;
+  font-weight: bold;
+  font-size: 130%;
+}
+#menu a:hover {
+  text-decoration: underline;
+}
+#menu .webgen-menu-item-selected {
+  border-left: 3px solid black;
+}
+#menu ul {
+  list-style-type: none;
+  padding: 0px;
+  margin-left: 10px;
+}
+#menu li > ul {
+  font-size: 95%;
+}
+#menu li {
+  margin: 0.0em 0px;
+  padding: 2px 0px;
+  padding-left: 5px;
+  border-left: 3px solid #CCCCCC;
+}

data/data/webgen/website_styles/simple/src/default.template ADDED Viewed

@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="{lang:}">
+  <head>
+    <title>{title: }</title>
+    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+    <meta name="description" content="Your description goes here..." />
+    <meta name="keywords" content="your,keywords,goes,here" />
+    <meta name="author" content="Your Name" />
+    <meta name="generator" content="webgen - http://webgen.rubyforge.com/" />
+    <link href="{relocatable: default.css}" rel="stylesheet" type="text/css" />
+  </head>
+  <body>
+    <div id="header">
+      <h1>{title: }</h1>
+    </div>
+    <div id="headerbar" class="bar">
+      <span class="left">Location: {breadcrumb_trail: }</span>
+      <span class="right">Language: {langbar: }</span>
+      <div style="clear:both"></div>
+    </div>
+    <div id="menu">
+      {menu: }
+    </div>
+    <div id="body">
+      <webgen:block name="content" />
+    </div>
+    <div id="footer" class="bar">
+      Generated by <a href="http://webgen.rubyforge.org">webgen</a> on <b>{date: }</b>
+    </div>
+  </body>
+</html>

data/data/webgen/website_templates/default/README ADDED Viewed

@@ -0,0 +1,6 @@
+description:
+  This is the default website template. It only contains the basic files and is a good
+  starting place for any website.
+author:
+  Thomas Leitner

data/data/webgen/website_templates/default/src/index.page ADDED Viewed

@@ -0,0 +1,8 @@
+---
+title: Empty index page
+in_menu: true
+routed_title: New Website
+---
+## Empty index file
+Fill this file with your own data!!!

data/data/webgen/website_templates/project/README ADDED Viewed

@@ -0,0 +1,5 @@
+description:
+  This template provides the basic files for a website for a software project.
+author:
+  Thomas Leitner

data/data/webgen/website_templates/project/src/about.page ADDED Viewed

@@ -0,0 +1,12 @@
+---
+title: About
+in_menu: true
+sort_info: 10
+---
+## About Project TODO
+Description of project!
+## About the Author
+Enter information about yourself here!

data/data/webgen/website_templates/project/src/download.page ADDED Viewed

@@ -0,0 +1,15 @@
+---
+title: Download
+in_menu: true
+sort_info: 30
+---
+## Download
+Download link will be here!
+List of dependencies:
+* Dep One v. 3.3.3
+* Dep Two v. 2.5.1 (optional)

data/data/webgen/website_templates/project/src/features.page ADDED Viewed

@@ -0,0 +1,8 @@
+---
+title: Features
+in_menu: true
+sort_info: 20
+---
+## Features
+Here is the place where the feature list for your project should go.

data/data/webgen/website_templates/project/src/index.page ADDED Viewed

@@ -0,0 +1,9 @@
+---
+title: Homepage
+in_menu: true
+sort_info: 0
+routed_title: Project TODO
+---
+## Project TODO
+This is the first page your viewers will see!

data/data/webgen/website_templates/project/src/screenshots.page ADDED Viewed

@@ -0,0 +1,18 @@
+---
+title: Screenshots
+in_menu: true
+sort_info: 40
+---
+## Screenshots
+### Main View
+Image of Main View
+Description of image
+### Next image
+Image
+bla bla bla

data/doc/contentprocessor.template ADDED Viewed

@@ -0,0 +1,11 @@
+---
+template: extensions.template
+--- name:summary pipeline:erb,tags,maruku,blocks
+As short name for the content processor (used, for example, in the `pipeline` option of a block in a
+file in [Webgen Page Format]({relocatable: webgen_page_format.html})) one of the following can be
+used: `<%= context.website.config['contentprocessor.map'].select {|k,v| v ==
+context.content_node['title']}.map {|k,v| k}.join(', ') %>`.
+--- name:content
+<webgen:block name='content' />

data/doc/contentprocessor/blocks.page ADDED Viewed

@@ -0,0 +1,66 @@
+---
+title: Webgen::ContentProcessor::Blocks
+---
+## Description
+This processor replaces a special xml tag with rendered blocks. It is used, for example, in
+templates to define the place where the actual page content should be.
+The general syntax is as follows:
+    <webgen:block name='BLOCK_NAME' chain='(L)CN;(L)CN;...' />
+So it is basically an XML tag with two attributes, `name` and `chain`. The `name` attribute
+specifies the name of the block that should be rendered in place of the block tag. The next node in
+the used node chain needs to have a block that is named so, otherwise an error is thrown (if there
+is only one node left in the node chain that node is used). The block is rendered according to its
+render pipeline and then inserted.
+The optional attribute `chain` specifies the node chain that should be used for rendering the
+block. Its value needs to be a list of (localized) canonical names of nodes separated by semicolons
+that should be used as node chain. If this attribute is not specified the default node chain is
+used.
+This is more easily explained with examples. Assume we have a `default.template` file, a
+`page.template` file and a `my.page` file with the following contents:
+The `default.template` file:
+    --- name:content pipeline:blocks
+    before default
+    <webgen:block name='content' />
+    after default 1
+    <webgen:block name='content' chain='page.template;my.html' />
+    after default 2
+The `page.template` file:
+    --- name:content pipeline:blocks
+    before page 1
+    <webgen:block name='content' />
+    after page 1
+And the `my.page` file:
+    --- name:content pipeline:
+    The content of the page file.
+When `my.page` gets rendered to `my.html`, the node chain looks like this by default:
+    default.template ---> my.page
+The first webgen block tag just inserts the rendered block named `content` of `my.page`. The second
+block tag uses a custom node chain. Therefore the block named `content` of `page.template` gets
+rendered using the node chain:
+    page.template ---> my.page
+and then inserted. Summing up the above, the rendered file `my.html` will then look like this:
+    before default 1
+    The content of the page file.
+    after default 1
+    before page 1
+    The content of the page file.
+    after page 1
+    after default 2

data/doc/contentprocessor/builder.page ADDED Viewed

@@ -0,0 +1,80 @@
+---
+title: Webgen::ContentProcessor::Builder
+---
+## Description
+This content processor can be used to programatically create XHTML/XML documents
+([Reference][1]). The top builder object is provided through the `xml` object. There are also other
+objects provided by webgen available - have a look at the [erb documentation]({relocatable:
+erb.html}).
+> This extension is only available if you have installed the [builder][1] library. The preferred way
+> to do this is via Rubygems:
+>
+>     gem install builder
+{.exclamation}
+## Examples
+Here is a short sample of content that is valid Ruby and uses the special `xml` object:
+    xml.h1("This a h1 header", :id => 'myid')
+    xml.p do |p|
+      p.text! "You can just write "
+      p.b "your"
+      p.text! "paragraphs here and"
+      p.a("link", :href => "http://someurl.com")
+      p.text! "them below. This is also a"
+      p.i "nice"
+      p.text! "format!"
+    end
+    xml.blockquote(:class => 'information') do |bq|
+      bq.text! "Citations are easy too."
+      bq.text! "Really. And you can assign them attributes."
+    end
+    xml.ul do |ul|
+      ul.li "Lists"
+      ul.li "aren't"
+      ul.li "difficult"
+      ul.li "either."
+    end
+Following is a complete example which shows how to use this extension in a page file which generates
+a custom XML document (the `content` block has to be valid Ruby!):
+    ---
+    output_path_style: [:parent, :cnbase, ['.', :lang], '.xml']
+    title: Person Object
+    template: ~
+    --- pipeline:builder
+    xml.persons(:path => node.absolute_lcn) do |p|
+      p.person do |b|
+        b.firstname('Thomas')
+        b.lastname('Leitner')
+      end
+      p.person do |b|
+        b.firstname('Other first')
+        b.lastname('Other last')
+      end
+    end
+The above will produce the following output:
+    <persons path="/test.xml">
+      <person>
+        <firstname>Thomas</firstname>
+        <lastname>Leitner</lastname>
+      </person>
+      <person>
+        <firstname>Other first</firstname>
+        <lastname>Other last</lastname>
+      </person>
+    </persons>
+[1]: http://builder.rubyforge.org "Homepage of builder library"

data/doc/contentprocessor/erb.page ADDED Viewed

@@ -0,0 +1,56 @@
+---
+title: Webgen::ContentProcessor::Erb
+---
+## Description
+This processer uses ERB (embedded Ruby) to process content. For detailed information about ERB have
+a look at its documentation by executing `ri ERB` or the [ruby documentation
+site](http://www.ruby-doc.org/)!
+You can use the following special objects in your ERB code:
+* `context`: This object provides the whole rendering context, the following objects are just for
+  backwards compatibility.
+* `ref_node` (or `context.ref_node`): The reference node which is the source of the ERB code that is
+  executed. Should be used, for example, for resolving paths.
+* `node` (or `context.content_node`): The node that gets currently rendered. Should be used for
+  retrieving meta information.
+* `dest_node` (or `context.dest_node`): The node in which the result gets inserted. Should be used
+  for calculating relative paths.
+Here is a small usage example. The following put in a page file
+    Counting 5 items dynamically:
+    <%% for i in 1..5 %>
+      * item <%%= i %>
+    <%% end %>
+    Outputting all meta information:
+    <%% node.meta_info.each do |k,v| %>
+      * <%%= k %> = <%%= v %>
+    <%% end %>
+... will give the result:
+    Counting 5 items dynamically:
+    <% for i in 1..5 %>
+      * item <%= i %>
+    <% end %>
+    Outputting all meta information:
+    <% node.meta_info.each do |k,v| %>
+      * <%= k %> = <%= v %>
+    <% end %>
+The second line shows the first form of the ERB tags which executes Ruby code but does not output
+anything: it just starts a `for` loop. On the third line the second form of ERB tags is used to
+output the result of the Ruby code (note the equation sign!). And the fourth line completes the
+`for` loop by adding the needed `end` keyword.
+> You may need to ensure that the ERB start and end tags are not processed by the content
+> processor. For example, when using the RedCloth content processor, you may need to surround the
+> ERB code with `<textile>` tags!
+{.exclamation}