kodekopelli 0.8.0

data/CHANGELOG

@@ -0,0 +1,3 @@
+*0.8.0* (19 September, 2005)
+
+* Initial release into the wild.

data/LICENSE

@@ -0,0 +1,32 @@
+COPYRIGHT AND PERMISSION NOTICE
+
+Copyright (c) 2005 Free Range Data LLC
+
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name of a copyright holder shall
+not be used in advertising or otherwise to promote the sale, use or other
+dealings in this Software without prior written authorization of the
+copyright holder.
+
+Kodekopelli and the Kodekopelli logo are trademarks of
+Free Range Data.

data/README

@@ -0,0 +1,78 @@
+                            K                      
+                            ODE   KO               
+                             PEL  LI   K           
+                     ODEKOP   EL  LI   KO          
+                         DEK   O  PE   LL          
+                           IK  OD EK   OP          
+                 ELLIKODE   KO PELL   IK           
+                 O     DEK  OPELLIK ODE            
+                         KOPELLIKODEK              
+                          OPELLIKODEK              
+                  OPELLIKODEKOPELLIKOD             
+               EKOPELLIKODEKOPELLIKOD              
+             EKOPELLIKODE  KOPELLIKOD              
+           EKOPELLIKODEK     OPELLI                
+          KODEKOPELLIKOD       EK                  
+         OPELLIKODEKOPELL      IKO                 
+        DEKOPELLIKODEKOPE     LLI                  
+        KODEPELLIKODE  KOPELLIKODE                 
+        KOPELLIKODEKOPEL        LI                 
+        KODEKOPE    LLIKODEKOPELLIK                
+        ODEKOPELL                IK                
+         ODEKOPELL               IK                
+         ODEKOPELLI              KOD               
+          EKOPELLIKODE            KO               
+           PELLIKODEKOPELLIK      OD               
+            EKOPELLIKODEKOPEL                      
+             LIKODEKOPEL  LI                       
+              KODEKOP     ELLIKOD                  
+                EKOPE     LLIKO                    
+                   DEK                             
+                 OPELL            TM               
+                IKODEKOP                           
+                 ELLIKOD  
+
+Kodekopelli -- making code generation rock since 2003.  Do it well.
+Do it once.  Let Kodekopelli do the rest.
+
+Kodekopelli is an unobtrusive, unassuming code generator that leverages the
+expressiveness of the Ruby language and the ERB lightweight templating system
+to help facilitate the Don't Repeat Yourself (DRY) Principle in a manner
+consistent with agile development practices. That means playing well in an
+environment of continuous integration and utilizing idioms familiar
+(or, at least, intuitive) to users of automated build systems like Ant, 
+NAnt and Rake. Kodekopelli provides an additional layer of abstraction
+between the creative thought and real engineering work in which humans
+excel and the drudgery of those tedious tasks better left to computers.
+All too often, said tedium steals valuable time from the lives of developers
+who accept those burdens as badges of honor or as inevitable occupational hazards.
+
+== License
+
+Kodekopelli is released under the business-friendly MIT license.
+
+== _Legalese_
+
+The Kodekopelli logo and the Kodekopelli name are trademarks of Free Range Data LLC.
+
+== Additional Documentation
+
+Additional documentation, including a usage manual, may be found at the
+Kodekopelli site[http://www.kodekopelli.org].
+
+== Examples
+
+Numerous examples may be found both in the /examples folder
+of this distribution and on the
+Kodekopelli site[http://www.kodekopelli.org].
+
+== Support
+
+The Kodekopelli site is located at http://www.kodekopelli.org
+
+Technical assistance and Kodekopelli enterprise support services
+are available from Free Range Data LLC (http://www.freerangedata.com).
+
+Please feel free to submit comments, feature requests, or enhancements.
+If your enhancement is integrated into Kodekopelli, your name will be
+added to the list of contributors on the main site.

data/Rakefile

@@ -0,0 +1,87 @@
+require 'rubygems'
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+require 'rake/packagetask'
+require 'rake/gempackagetask'
+require 'rake/contrib/rubyforgepublisher'
+
+PKG_NAME = 'kodekopelli'
+PKG_VERSION = ENV['KODEKOPELLI_VERSION'] || '0.8.0'
+PKG_FILE_NAME = "#{PKG_NAME}-#{PKG_VERSION}"
+BUILD_DIR = "build"
+TEST_OUTPUT_DIR = "test/output"
+PACKAGE_DIR = "pkg"
+
+RELEASE_NAME = "REL #{PKG_VERSION}"
+
+RUBY_FORGE_PROJECT = 'kodekopelli'
+RUBY_FORGE_USER = 'hastyb0y'
+
+PKG_FILES = FileList[
+  "lib/**/*", "test/**/*", "doc/**/*", "examples/**/*", "[A-Z]*", "rakefile"
+  ].exclude(/\bCVS\b|-$/)
+  
+desc "Default Task"
+task :default => [ :clean, :prepare, :test, :rdoc ]
+
+desc "Scorch-the-earth removal of all build artifacts."
+task :clean do
+  rm_rf BUILD_DIR
+  rm_rf TEST_OUTPUT_DIR
+  rm_rf PACKAGE_DIR
+end
+
+desc "Prepares the blank canvas for build process(es)."
+task :prepare do
+  FileUtils.mkdir_p TEST_OUTPUT_DIR
+end
+
+# Run the unit and functional tests
+Rake::TestTask.new { |t|
+  t.libs << "test"
+  t.pattern = 'test/ts_all_tests.rb'
+  t.verbose = true
+}  
+desc "Run the unit tests."
+task :test => [ :clean, :prepare ] do
+end
+
+# Generate the RDoc documentation
+Rake::RDocTask.new { |rdoc|
+  rdoc.rdoc_dir = "#{BUILD_DIR}/doc/rdoc"
+  rdoc.title = "Kodekopelli"
+  rdoc.options << '--line-numbers' << '--inline-source' << '--main' << 'README'
+  rdoc.rdoc_files.include('README', 'LICENSE', 'CHANGELOG')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+}
+
+# Create compressed packages
+spec = Gem::Specification.new do |s|
+  s.platform = Gem::Platform::RUBY
+  s.name = PKG_NAME
+  s.summary = "Making code generation rock since 2003. Do it well. Do it once. Let Kodekopelli do the rest."
+  s.version = PKG_VERSION
+  
+  s.author = "Rich Wertz"
+  s.email = "rich@kodekopelli.org"
+  s.rubyforge_project = RUBY_FORGE_PROJECT
+  s.homepage = "http://www.kodekopelli.org"
+  
+  s.has_rdoc = true
+  s.extra_rdoc_files = [ "README", "CHANGELOG", "LICENSE" ]
+  s.test_file = "test/ts_all_tests.rb"
+  s.requirements << 'none'
+  s.require_path = "lib"
+  s.autorequire = PKG_NAME
+  s.files = PKG_FILES
+  
+  s.bindir = "bin"
+  s.executables = ["kodekopelli"]
+  s.default_executable = "kodekopelli"
+end
+
+Rake::GemPackageTask.new(spec) do |pkg|
+  # pkg.need_tar = true
+  # pkg.need_zip = true
+end

data/bin/kodekopelli

@@ -0,0 +1,5 @@
+Signal.trap("INT") { puts; exit }
+
+require File.dirname(__FILE__) + '/../lib/kodekopelli'
+
+Kodekopelli::FileGenerator.new.run(ARGV)

data/examples/faqomatic/config.xml

@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<kodekopelli>
+  <property location="." name="basedir" />
+  <property location="${basedir}/templates" name="template.dir" />
+  <property location="${basedir}/includes" name="include.dir" />
+  <property location="${basedir}/generated" name="output.dir" />
+  <property location="${template.dir}/html_wrapper.txt" name="html" />
+  <property location="${template.dir}/great_big.txt" name="big" />
+  <property location="${template.dir}/faqs.txt" name="faqs" />
+  <filegroup>
+    <file name="${output.dir}/faqs.html">
+      <composite template="${html}">
+        <composite template="${faqs}">
+          <composite question="Does fuzzy logic tickle?">
+            <template>Yes, but only on Tuesdays.</template>
+          </composite>
+          <composite
+            question="If vegetarians eat vegetables, what do humanitarians eat?">
+            <template><![CDATA[The world may never know...]]></template>
+          </composite>
+          <composite question="Is animal shampoo tested on humans?">
+            <include file="${include.dir}/shampoo_answer.txt" />
+          </composite>
+          <composite question="Can someone be a closet claustrophobic?">
+            <composite bigs="1" template="${big}">
+              <template>No.</template>
+            </composite>
+          </composite>
+          <composite
+            question="Can you imagine a world without hypothetical questions?">
+            <template>Absolutely</template>
+            <template> </template>
+            <template>not</template>
+            <template>.</template>
+          </composite>
+        </composite>
+      </composite>
+    </file>
+  </filegroup>
+</kodekopelli>

data/examples/faqomatic/content.rhtml

@@ -0,0 +1,376 @@
+<p class="note">
+  <strong>Please Note</strong> This example should be considered a work in progress.
+  Although all associated configuration files and templates have been completed and
+  are included in this example, not all supporting text has been added.
+</p>
+<p>
+  This simple example demonstrates basic Kodekopelli functionality
+  and recommended practices.  The following Kodekopelli concepts
+  not covered by previous examples are illustrated herein:
+</p>
+<ul>
+  <li>
+    Using <a href="<%= att 'manual' %>#templates">template</a> elements.
+  </li>
+  <li>
+    Using <a href="<%= att 'manual' %>#composites">composite</a> elements.
+  </li>
+  <li>
+    Creating <a href="<%= att 'manual' %>#kodekopellitemplates">Kodekopelli templates</a>
+    templates that access the attribute values of child
+    elements.
+  </li>
+  <li>
+    Explicitly specifying template text in a Kodekopelli configuration
+    file.
+  </li>
+</ul>
+<h2>Problem</h2>
+<p>
+  Your static web site contains a page dedicated to FAQs, or
+  <em>frequently-asked questions</em>.  Each time that a new
+  question/answer combination is added, you must
+  manually add the new question, create a link to the question's
+  answer and, possibly, shuffle the order of the questions.  Although
+  the amount of work required isn't overwhelming, it's tedious--especially
+  when questions must be rearranged.  Also, you would like to minimize the
+  coupling between the actual questions and answers and the presentation
+  logic.
+</p>
+<h2>Solution</h2>
+<p>
+  Use Kodekopelli to abstract questions and answers away from presentation
+  logic, so that any reordering or question additions, modifications or
+  deletions may be performed
+  within a single Kodekopelli configuration file.
+</p>
+<h3>Project Structure</h3>
+<p>
+  Starting from a fresh, empty folder
+  of your choice, create subfolders mirroring the following structure:
+</p>
+<pre class="code">
+  /generated
+  /templates
+  /includes
+</pre>
+<p>
+  The <em>generated</em> folder will contain those files that Kodekopelli
+  generates during processing.  The <em>templates</em> folder will contain
+  those files that Kodekopelli will interpret as
+  <a href="<%= att 'manual' %>#kodekopellitemplates">Kodekopelli templates</a>.
+  The <em>includes</em> folder will contain those static files that are available
+  to be <a href="<%= att 'manual' %>#includes">included</a>,
+  but not interpreted, by Kodekopelli.  Please note that this project layout is
+  not required for Kodekopelli to function correctly; rather, it is introduced as
+  a respectable starting point for your projects.
+</p>
+<h3>The Goal</h3>
+<p>
+  This example will demonstrate using Kodekopelli to create the simple
+  FAQ list shown below.  Questions listed at the top of the list
+  will contain links to their corresponding answers that will, conversely,
+  contain links back to their questions.  FAQ lists structured in this
+  manner make it very easy for users to navigate back and forth
+  between questions and answers without losing their relative positions
+  within the question list.
+</p>
+<div class="example">
+<big>
+	<strong>
+		Questions</strong></big>
+<br />
+<ol>
+	<li id="question_1">
+		Does fuzzy logic tickle? 
+		<a href="#faq_1">
+			Answer&nbsp;&#187;
+		</a>
+	</li>
+	<li id="question_2">
+		If vegetarians eat vegetables, what do humanitarians eat? 
+		<a href="#faq_2">
+			Answer&nbsp;&#187;
+		</a>
+	</li>
+	<li id="question_3">
+		Is animal shampoo tested on humans? 
+		<a href="#faq_3">
+			Answer&nbsp;&#187;
+		</a>
+	</li>
+	<li id="question_4">
+		Can someone be a closet claustrophobic? 
+		<a href="#faq_4">
+			Answer&nbsp;&#187;
+		</a>
+	</li>
+	<li id="question_5">
+		Can you imagine a world without hypothetical questions? 
+		<a href="#faq_5">
+			Answer&nbsp;&#187;
+		</a>
+	</li>
+</ol>
+<big>
+	<strong>
+		Answers</strong></big>
+<br />
+<br />
+<strong id="faq_1">
+	1.&nbsp;Does fuzzy logic tickle?</strong>
+<br />
+Yes, but only on Tuesdays. 
+<p>
+	<a href="#question_1">
+		&#171;&nbsp;Back
+	</a>
+</p>
+<strong id="faq_2">
+	2.&nbsp;If vegetarians eat vegetables, what do humanitarians eat?</strong>
+<br />
+The world may never know... 
+<p>
+	<a href="#question_2">
+		&#171;&nbsp;Back
+	</a>
+</p>
+<strong id="faq_3">
+	3.&nbsp;Is animal shampoo tested on humans?</strong>
+<br />
+Who told you!?! 
+<p>
+	<a href="#question_3">
+		&#171;&nbsp;Back
+	</a>
+</p>
+<strong id="faq_4">
+	4.&nbsp;Can someone be a closet claustrophobic?</strong>
+<br />
+<big>
+	<big>
+		<big>
+			<big>
+				No.</big></big></big>
+</big>
+<p>
+	<a href="#question_4">
+		&#171;&nbsp;Back
+	</a>
+</p>
+<strong id="faq_5">
+	5.&nbsp;Can you imagine a world without hypothetical questions?</strong>
+<br />
+Absolutely not. 
+<p>
+	<a href="#question_5">
+		&#171;&nbsp;Back
+	</a>
+</p>
+</div>
+<h3>The Configuration File</h3>
+<p>
+  Using your favorite text or XML
+  editor, create a file called config.xml with the following content at the
+  root level of your project folder:
+</p>
+<pre class="code">
+  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
+  &lt;kodekopelli&gt;
+  &lt;/kodekopelli&gt;
+</pre>
+<p>
+  Create properties representing the project structure.
+</p>
+<pre class="code">
+  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
+    <span class="focus">&lt;property location=&quot;.&quot; name=&quot;basedir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/templates&quot; name=&quot;template.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/includes&quot; name=&quot;include.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/generated&quot; name=&quot;output.dir&quot; /&gt;</span>
+  &lt;/kodekopelli&gt;
+</pre>
+<p>
+  The configuration file at this point does not contain enough information
+  for Kodekopelli to process without error.  Before additional configuration directives
+  are provided, however, our attention should turn to the templates that will
+  be required to create the <em>FAQ-O-Matic</em>.  Since the FAQ list
+  created in this example will be rendered as an HTML snippet, it would be
+  wise to create a wrapper template containing enough markup to house the
+  FAQ list in a well-formed HTML document.
+</p>
+<h3>The HTML Wrapper Template</h3>
+<p>
+  Using your favorite
+  text editor, create a new file containing the following markup.
+</p>
+<pre class="code">
+  &lt;html&gt;
+    &lt;head&gt;
+      &lt;title&gt;&lt;%= h att(&apos;title&apos;) %&gt;&lt;/title&gt;
+    &lt;/head&gt;
+    &lt;body&gt;
+      &lt;h1&gt;&lt;%= h att(&apos;title&apos;) %&gt;&lt;/h1&gt;
+      &lt;%= child_output %&gt;
+    &lt;/body&gt;
+  &lt;/html&gt;
+</pre>
+<p>
+  This template creates a minimal HTML wrapper that checks for the presence
+  of an attribute named <em>title</em>.  If found, the value of the
+  <em>title</em> attribute is used for the page title and also
+  for the page header.  More importantly, the template also includes the
+  outcome of all child element processing within the body of the HTML
+  document, using the <em>child_output</em> method.  Now that the
+  template is complete, save it under the <em>templates</em> folder
+  using the name <em>html_wrapper.txt</em>.
+</p>
+<p>
+  Now add the information for the new template to the configuration file.
+</p>
+<pre class="code">
+  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
+    &lt;property location=&quot;.&quot; name=&quot;basedir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/templates&quot; name=&quot;template.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/includes&quot; name=&quot;include.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/generated&quot; name=&quot;output.dir&quot; /&gt;
+    <span class="focus">&lt;property location=&quot;${template.dir}/html_wrapper.txt&quot; name=&quot;html&quot; /&gt;</span>
+  &lt;/kodekopelli&gt;
+</pre>
+
+<h3>The Great Big Text Template</h3>
+<p>
+  This template is very simple, as it wraps a variable number of
+  &lt;big&gt;...&lt;/big&gt; elements around all child element output.
+  The number of <em>big</em> wrappers added corresponds
+  to the value of the <em>bigs</em> attribute provided.  If no value is
+  provided for the <em>bigs</em> attribute, a default value of '1' is
+  used.  Save this template under the <em>templates</em> folder using the name
+  <em>great_big.txt</em>.
+</p>
+<pre class="code">
+  &lt;% att(&apos;bigs&apos;, 1).to_i.times {%&gt;&lt;big&gt;&lt;%} %&gt;
+  &lt;%= child_output %&gt;
+  &lt;% att(&apos;bigs&apos;, 1).to_i.times {%&gt;&lt;/big&gt;&lt;%} %&gt;
+</pre>
+<p>
+  Add the information for the <em>great big text</em> template to the configuration file.
+</p>
+<pre class="code">
+  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
+    &lt;property location=&quot;.&quot; name=&quot;basedir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/templates&quot; name=&quot;template.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/includes&quot; name=&quot;include.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/generated&quot; name=&quot;output.dir&quot; /&gt;
+    &lt;property location=&quot;${template.dir}/html_wrapper.txt&quot; name=&quot;html&quot; /&gt;
+    <span class="focus">&lt;property location=&quot;${template.dir}/great_big.txt&quot; name=&quot;big&quot; /&gt;</span>
+  &lt;/kodekopelli&gt;
+</pre>
+<h3>The FAQs Template</h3>
+<p>
+  The FAQs template is a <em>composite</em> template responsible for building
+  the actual FAQ list.  
+</p>
+
+<pre class="code">
+  &lt;big&gt;&lt;strong&gt;Questions&lt;/strong&gt;&lt;/big&gt;&lt;br /&gt;
+  &lt;ol&gt;
+  &lt;% question_counter = 1 %&gt;
+  &lt;% child_iterator { |current_child, text| %&gt;
+    &lt;li id="question_&lt;%= question_counter.to_s %&gt;"&gt;
+      &lt;%= node_att(current_child, 'question') %&gt;
+      &lt;a href="&lt;%= "#faq_#{question_counter.to_s}" %&gt;"&gt;Answer&nbsp;&#187;&lt;/a&gt;
+    &lt;/li&gt;
+  &lt;% question_counter += 1 %&gt;
+  &lt;% } %&gt;
+  &lt;/ol&gt;
+  &lt;big&gt;&lt;strong&gt;Answers&lt;/strong&gt;&lt;/big&gt;&lt;br /&gt;&lt;br /&gt;
+  &lt;% answer_counter = 1 %&gt;
+  &lt;% child_iterator { |current_child, text| %&gt;
+  &lt;strong id="faq_&lt;%= answer_counter.to_s %&gt;"&gt;
+    &lt;%= answer_counter.to_s %&gt;.&nbsp;&lt;%= node_att(current_child,'question') %&gt;&lt;/strong&gt;&lt;br /&gt;
+  &lt;%= text %&gt;
+  &lt;p&gt;
+    &lt;a href="#question_&lt;%= answer_counter.to_s %&gt;"&gt;&#171;&nbsp;Back&lt;/a&gt;
+  &lt;/p&gt;
+  &lt;% answer_counter += 1 %&gt;
+  &lt;% } %&gt;
+</pre>
+<p>
+  Add the information for the final template to the configuration file.
+</p>
+<pre class="code">
+  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
+    &lt;property location=&quot;.&quot; name=&quot;basedir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/templates&quot; name=&quot;template.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/includes&quot; name=&quot;include.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/generated&quot; name=&quot;output.dir&quot; /&gt;
+    &lt;property location=&quot;${template.dir}/html_wrapper.txt&quot; name=&quot;html&quot; /&gt;
+    &lt;property location=&quot;${template.dir}/great_big.txt&quot; name=&quot;big&quot; /&gt;
+    <span class="focus">&lt;property location=&quot;${template.dir}/faqs.txt&quot; name=&quot;faqs&quot; /&gt;</span>
+  &lt;/kodekopelli&gt;
+</pre>
+<h3>Back to the Configuration File</h3>
+<pre class="code">
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+  &lt;kodekopelli&gt;
+    &lt;property location=&quot;.&quot; name=&quot;basedir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/templates&quot; name=&quot;template.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/includes&quot; name=&quot;include.dir&quot; /&gt;
+    &lt;property location=&quot;${basedir}/generated&quot; name=&quot;output.dir&quot; /&gt;
+    &lt;property location=&quot;${template.dir}/html_wrapper.txt&quot; name=&quot;html&quot; /&gt;
+    &lt;property location=&quot;${template.dir}/great_big.txt&quot; name=&quot;big&quot; /&gt;
+    &lt;property location=&quot;${template.dir}/faqs.txt&quot; name=&quot;faqs&quot; /&gt;
+    &lt;filegroup&gt;
+      &lt;file name=&quot;${output.dir}/faqs.html&quot;&gt;
+        &lt;composite template=&quot;${html}&quot;&gt;
+          &lt;composite template=&quot;${faqs}&quot;&gt;
+            &lt;composite question=&quot;Does fuzzy logic tickle?&quot;&gt;
+              &lt;template&gt;Yes, but only on Tuesdays.&lt;/template&gt;
+            &lt;/composite&gt;
+            &lt;composite
+              question=&quot;If vegetarians eat vegetables, what do humanitarians eat?&quot;&gt;
+              &lt;template&gt;&lt;![CDATA[The world may never know...]]&gt;&lt;/template&gt;
+            &lt;/composite&gt;
+            &lt;composite question=&quot;Is animal shampoo tested on humans?&quot;&gt;
+              &lt;include file=&quot;${include.dir}/shampoo_answer.txt&quot; /&gt;
+            &lt;/composite&gt;
+            &lt;composite question=&quot;Can someone be a closet claustrophobic?&quot;&gt;
+              &lt;composite bigs=&quot;1&quot; template=&quot;${big}&quot;&gt;
+                &lt;template&gt;No.&lt;/template&gt;
+              &lt;/composite&gt;
+            &lt;/composite&gt;
+            &lt;composite
+              question=&quot;Can you imagine a world without hypothetical questions?&quot;&gt;
+              &lt;template&gt;Absolutely&lt;/template&gt;
+              &lt;template&gt; &lt;/template&gt;
+              &lt;template&gt;not&lt;/template&gt;
+              &lt;template&gt;.&lt;/template&gt;
+            &lt;/composite&gt;
+          &lt;/composite&gt;
+        &lt;/composite&gt;
+      &lt;/file&gt;
+    &lt;/filegroup&gt;
+  &lt;/kodekopelli&gt;
+</pre>
+<p>
+  The configuration file is complete and is now ready for processing by Kodekopelli.
+  From the top level of your project folder, invoke Kodekopelli from the command line:
+</p>
+<pre class="code">
+  % <span class="focus">kodekopelli config.xml</span>
+</pre>
+<p>
+  After Kodekopelli has finished processing the file, you may view the FAQ list
+  within the context of the HTML page located in the project's
+  <em>generated</em> folder.
+</p>
+<h2>Notes</h2>
+<ul>
+  <li>
+    The template and composite level elements used to create the answers
+    for the FAQ questions above have been made intentionally diverse so that
+    the reader may be aware that there are numerous solutions to the same
+    problem when using Kodekopelli.
+  </li>
+</ul>