webby 0.8.0 → 0.8.1

data/History.txt

@@ -1,3 +1,18 @@
+== 0.8.1 / 2008-03-09
+
+* 2 major enhancement
+  - Added support for UltraViolet syntax highlighting
+    (code provided by Guillaume Carbonneau)
+  - Added rake tasks to validate the hyperlinks for the HTML files
+    in the output directory
+* 2 minor enhancements
+  - Improved error handling and reporting during the build process
+  - Added site defaults for the helpers (coderay, graphviv, latex,
+    etc.)
+* 1 bug fix
+  - Fixed an error with the prev / next calls in the paginator and
+    rendering links to those pages
+
 == 0.8.0 / 2008-02-28
 
 * 3 major enhancements

data/Manifest.txt

@@ -36,6 +36,7 @@ data/tasks/deploy.rake
 data/tasks/growl.rake
 data/tasks/heel.rake
 data/tasks/setup.rb
+data/tasks/validate.rake
 data/templates/_partial.erb
 data/templates/atom_feed.erb
 data/templates/page.erb
@@ -44,9 +45,9 @@ examples/webby/content/css/blueprint/print.css
 examples/webby/content/css/blueprint/screen.css
 examples/webby/content/css/coderay.css
 examples/webby/content/css/site.css
-examples/webby/content/download.txt
 examples/webby/content/index.txt
 examples/webby/content/manual/index.txt
+examples/webby/content/reference/index.txt
 examples/webby/content/robots.txt
 examples/webby/content/script/jquery.corner.js
 examples/webby/content/script/jquery.js
@@ -58,6 +59,7 @@ examples/webby/tasks/deploy.rake
 examples/webby/tasks/growl.rake
 examples/webby/tasks/heel.rake
 examples/webby/tasks/setup.rb
+examples/webby/tasks/validate.rake
 examples/webby/templates/page.erb
 lib/webby.rb
 lib/webby/auto_builder.rb
@@ -76,7 +78,9 @@ lib/webby/helpers/coderay_helper.rb
 lib/webby/helpers/graphviz_helper.rb
 lib/webby/helpers/tag_helper.rb
 lib/webby/helpers/tex_img_helper.rb
+lib/webby/helpers/ultraviolet_helper.rb
 lib/webby/helpers/url_helper.rb
+lib/webby/link_validator.rb
 lib/webby/main.rb
 lib/webby/renderer.rb
 lib/webby/resources.rb

data/Rakefile

@@ -1,4 +1,4 @@
-# $Id: Rakefile 155 2008-02-17 00:48:30Z tim_pease $
+# $Id: Rakefile 196 2008-03-09 23:03:30Z tim_pease $
 
 load 'tasks/setup.rb'
 
@@ -17,17 +17,29 @@ PROJ.rubyforge_name = 'webby'
 PROJ.rdoc_dir = 'doc/rdoc'
 PROJ.rdoc_remote_dir = 'rdoc'
 PROJ.version = Webby::VERSION
+PROJ.release_name = 'Wandering Wookie'
 
-PROJ.exclude << '^examples/[^/]+/output'
-PROJ.exclude << '^tasks/archive'
-PROJ.exclude << '^tags$'
-
-PROJ.rdoc_exclude << '^data'
-PROJ.rdoc_exclude << '^examples'
+PROJ.exclude << %w(^examples/[^/]+/output ^tasks/archive ^tags$)
+PROJ.rdoc_exclude << %w(^data ^examples)
 
 PROJ.svn = true
 PROJ.spec_opts << '--color'
 
+PROJ.ann_email[:to] << 'webby-forum@googlegroups.com'
+PROJ.ann_email[:server] = 'smtp.gmail.com'
+PROJ.ann_email[:port] = 587
+
+PROJ.ann_text = <<-ANN
+== FUN FACT
+
+A Boeing 747's wingspan is longer than the Wright brothers first flight.
+
+== POST SCRIPT
+
+Blessings,
+TwP
+ANN
+
 depend_on 'directory_watcher'
 depend_on 'heel'
 depend_on 'hpricot'

data/data/tasks/deploy.rake

@@ -3,15 +3,15 @@ require 'rake/contrib/sshpublisher'
 
 namespace :deploy do
 
-  desc 'deploy to the server using rsync'
+  desc 'Deploy to the server using rsync'
   task :rsync do
     cmd = "rsync #{SITE.rsync_args.join(' ')} "
     cmd << "#{SITE.output_dir}/ #{SITE.host}:#{SITE.remote_dir}"
     sh cmd
   end
 
-  desc 'deploy to the server using ssh'
-  task 'ssh' do
+  desc 'Deploy to the server using ssh'
+  task :ssh do
     Rake::SshDirPublisher.new(
         SITE.host, SITE.remote_dir, SITE.output_dir
     ).upload

data/data/tasks/growl.rake

@@ -1,5 +1,5 @@
 
-desc 'send log events to Growl (Mac OS X only)'
+desc 'Send log events to Growl (Mac OS X only)'
 task :growl do
   Logging::Logger['Webby'].add_appenders(Logging::Appenders::Growl.new(
     "Webby",

data/data/tasks/heel.rake

@@ -1,12 +1,12 @@
 
 namespace :heel do
 
-  desc 'start the heel server to view website (not for Windows)'
+  desc 'Start the heel server to view website (not for Windows)'
   task :start do
     sh "heel --root #{SITE.output_dir} --port #{SITE.heel_port} --daemonize"
   end
   
-  desc 'stop the heel server'
+  desc 'Stop the heel server'
   task :stop do
     sh "heel --kill"
   end

data/data/tasks/setup.rb

@@ -8,25 +8,6 @@ end
 
 SITE = Webby.site
 
-# Webby defaults
-SITE.content_dir   = 'content'
-SITE.output_dir    = 'output'
-SITE.layout_dir    = 'layouts'
-SITE.template_dir  = 'templates'
-SITE.exclude       = %w[tmp$ bak$ ~$ CVS \.svn]
-  
-SITE.page_defaults = {
-  'layout' => 'default'
-}
-
-# Items used to deploy the webiste
-SITE.host       = 'user@hostname.tld'
-SITE.remote_dir = '/not/a/valid/dir'
-SITE.rsync_args = %w(-av --delete)
-
-# Options passed to the 'tidy' program when the tidy filter is used
-SITE.tidy_options = '-indent -wrap 80'
-
 # Load the other rake files in the tasks folder
 Dir.glob('tasks/*.rake').sort.each {|fn| import fn}
 

data/data/tasks/validate.rake

@@ -0,0 +1,19 @@
+
+namespace :validate do
+
+  desc 'Validate hyperlinks (exclude exteranl sites)'
+  task :internal => :build do
+    Webby::LinkValidator.validate(:external => false)
+  end
+
+  desc 'Validate hyperlinks (include external sites)'
+  task :external => :build do
+    Webby::LinkValidator.validate(:external => true)
+  end
+
+end  # validate
+
+desc 'Alias to validate:internal'
+task :validate => 'validate:internal'
+
+# EOF

data/examples/webby/Rakefile

@@ -10,6 +10,9 @@ SITE.host = 'tim_pease@rubyforge.org'
 SITE.remote_dir = '/var/www/gforge-projects/webby/'
 SITE.create_mode = 'directory'
 
+SITE.uv[:theme] = 'blackboard'
+SITE.uv[:line_numbers] = true
+
 task :autobuild => :growl
 
 # EOF

data/examples/webby/content/css/site.css

@@ -133,6 +133,13 @@ ul
   ul
     :margin-bottom    0
 
+table.reference
+  :width  100%
+  td
+    :padding  2px 5px
+    ul
+      :margin-bottom 0
+
 span.heading-num
   :margin-right  10px
 

data/examples/webby/content/index.txt

@@ -15,9 +15,10 @@ sudo gem install -y webby
 
 h2. Features
 
-* choose your templating language: *eRuby*, *Textile*, *Markdown*, *HAML*, *SASS*
-* support for "CodeRay":http://coderay.rubychan.de/ syntax highlighting
+* choose your templating language: *ERB*, *Textile*, *Markdown*, *HAML*, *SASS*
+* support for "UltraViolet":http://ultraviolet.rubyforge.org/ and "CodeRay":http://coderay.rubychan.de/ syntax highlighting
 * embeddable DOT scripts for "Graphviz":http://www.graphviz.org/ graphs
+* "LaTeX":http://www.latex-project.org/ snippets for mathematical formulas
 * automatically clean up generated content using "Tidy":http://tidy.sourceforge.net/
 * quick and speedy - only builds pages that have changed
 * deploy anywhere - it's just HTML, no special server stuff required
@@ -38,4 +39,4 @@ heel --root output --daemonize
 
 Webby is not limited to producing HTML. By no means! Do you ever get tired of repeating the same color code *#D3C4A2* in your CSS files? Webby can help. Need some customized JavaScript for your website. Webby can help. Anytime you find yourself repeating the same bit of text over and over, then you should be using Webby.
 
-Read the "tutorial":tutorial.html section for a quick introduction to Webby, and enjoy the wonders of *ASCII Alchemy*.
+Read the "tutorial":/tutorial section for a quick introduction to Webby, and enjoy the wonders of *ASCII Alchemy*.

data/examples/webby/content/manual/index.txt

@@ -13,7 +13,7 @@ p(title). Table of Contents
 <toc />
 </div>
 
-h2{clear:none}. Introduction
+h2. Introduction
 
 Webby was created out of the need for a simple way to build and manage small websites. The desire was for a system that could take files written in plain text, combine them with a layout file and produce web pages. In this system, a single page can be written quickly without the need for HTML markup; the look and feel of the entire site can be changed by modifying the site layout file.
 
@@ -41,16 +41,16 @@ The diagram above shows the basic concept of how Webby works. Changing the layou
 
 Webby does not limit the output to HTML. Webby can be used to generate XML files for RSS or Atom news feeds, CSS files for styling web pages, or any other type of text file that you can think of.
 
-h3{clear:none}. Requirements
+h3. Requirements
 
 Webby is written in the Ruby programming language. To install and run Webby you will need the following applications installed on your system:
 
 * "Ruby":http://ruby-lang.org
 * "RubyGems":http://rubygems.org/read/chapter/3
 
-h3{clear:none}. Installation
+h3. Installation
 
-Webby is easily installed as a Ruby gem. From a command prompt, type in the following:
+Webby is easily installed as a Ruby gem. From a command prompt type in the following:
 
 <pre>
 sudo gem install -y webby
@@ -63,16 +63,18 @@ bq. For those users installing Webby on the Windows platform, please omit the @s
 To make use of all the features Webby has to offer, the following gems should also be installed. These gems provide different ways to transform text into HTML or CSS.
 
 <pre>
+sudo gem install -y RedCloth
 sudo gem install -y BlueCloth
 sudo gem install -y haml
 sudo gem install -y coderay
+sudo gem install -y ultraviolet
 </pre>
 
-Webby can also use a few other programs to clean up generated HTML and to created pretty graphs. You can read more about these programs and how they are used in the Filters section of this manual  --  specifically, the sections on the "Tidy":#tidy filter and the "Graphviz":#graphviz filter.
+Webby can also use a few other programs to clean up generated HTML and to created pretty graphs and pictures. Where external programs are required, they will be duly noted in the manual.
 
 h3. Running Webby
 
-When the Webby gem is installed it also installs a @webby@ executable program. This program is used to create a new website and to update the associated rake tasks when a new version of Webby is released. Typing in @webby --help@ will show you the options this program supports. After you create a webiste, though, the webby command will not be needed. 
+When the Webby gem is installed it also installs a @webby@ executable program. This program is used to create a new website and to update the associated rake tasks when a new version of Webby is released. Typing in @webby --help@ will show you the options this program supports. After you create a website, though, the webby command will not be needed. 
 
 <pre>
 $ webby --help
@@ -86,21 +88,27 @@ common options:
         --version                    show version
 </pre>
 
-The tasks of building the webiste and deploying it to the destination server are handled by "Rake":http://docs.rubyrake.org/, a Ruby version of the more famous *make* program. Several rake tasks are provided by default. You are free to create others to make developing and deploying your webiste easier. To see the current list of rake tasks type in @rake -T@.
+
+The day to day tasks of working with a webiste - creating pages, building the website, deploying changes to the server - are handled by the "Rake":http://docs.rubyrake.org/ application, a Ruby version of the more famous *make* program. Several rake tasks are provided by default. You are free to create others to make developing and deploying your website easier. To see the current list of rake tasks type in @rake -T@.
 
 <pre>
 $ rake -T
 
-rake autobuild     # continuously build the website
-rake build         # build the website
-rake clobber       # delete the website
-rake create:page   # create a new page
-rake deploy        # deploy the site to the webserver
-rake deploy:rsync  # deploy to the server using rsync
-rake deploy:ssh    # deploy to the server using ssh
-rake heel:start    # start the heel server to view website (not for Windows)
-rake heel:stop     # stop the heel server
-rake rebuild       # rebuild the website
+rake autobuild          # Continuously build the website
+rake build              # Build the website
+rake clobber            # Delete the website
+rake create:page        # Create a new page
+rake create:partial     # Create a new partial
+rake deploy             # deploy the website to Rubyforge
+rake deploy:rsync       # Deploy to the server using rsync
+rake deploy:ssh         # Deploy to the server using ssh
+rake growl              # Send log events to Growl (Mac OS X only)
+rake heel:start         # Start the heel server to view website (not for Windows)
+rake heel:stop          # Stop the heel server
+rake rebuild            # Rebuild the website
+rake validate           # Alias to validate:internal
+rake validate:external  # Validate hyperlinks (include external sites)
+rake validate:internal  # Validate hyperlinks (exclude exteranl sites)
 </pre>
 
 h2. Working With Resources

data/examples/webby/content/reference/index.txt

@@ -0,0 +1,57 @@
+---
+title:      Reference
+created_at: 2008-03-04 22:00:08.439182 -07:00
+filter:
+  - erb
+  - textile
+  - outline
+---
+<div class="toc push-1">
+
+p(title). Table of Contents
+
+<toc />
+</div>
+
+h3. Resources
+
+Resources are the files that are found in the _content_ and _layouts_ folders of a webby site. They come in the following four flavors:
+
+* *Pages*  --  contain meta-data at the top of the file, are found in the content folder, and are processed by the Webby filter engine
+* *Files*  --  are found in the content folder and copied "as is" to the output folder
+* *Partials*  --  contain snippets of text that can be used in multiple locations; partial filenames begin with an underscore are are _not_ copied to the output folder
+* *Layouts*  --  are found in the layout folder and provide the basic framework of the webpage - the header, the footer, the navigation
+
+h3. Attributes
+
+Attributes are defined in the meta-data section of pages and layouts.
+
+table(reference).
+| *destination* | Defines the path in the output directory where the rendered page should be stored. |
+| *dirty* | The dirty flag is used to determine whether the page should rendered or not. Normally this is automatically determined by the filter engine, but it can be overridden by setting this attribute. If the dirty flag is set to _true_ then the page will always be rendered. If the dirty flag is set to _false_ then the page will never be rendered. |
+| *extension* | Defines the extension that will be appended to the filename of the rendered page in the output folder. The extension is determined by looking at the following:
+* the meta-data of the current page for an @extension@ attribute
+* the meta-data of layout file of the current page for an @extension@ attribute
+* the extension of this page file in the _content_ folder |
+| *filter* | Defines the list of filters that will be applied to the contents of this page. If left blank, then the default filter will be applied to the page contents. |
+| *layout* | Defines the layout that the page contents will be rendered into. The default layout will be used if this attribute is not defined. The value of @nil@ should be specified if the page should not be rendered into any layout. |
+
+The following attributes are defined for each page in the content folder. These attributes cannot be changed in the page's meta-data section. However, they are available to the ERB filter when rendering the contents of a page.
+
+table(reference).
+| *path* | The full path to the file in the _content_ folder |
+| *dir* | The relative directory in the output folder where the page will be rendered |
+| *filename* | The name of the file in the _content_ folder excluding any path information |
+| *ext* | The extension of the file in the _content_ folder |
+| *mtime* | The modification time of the file in the _content_ folder |
+| *number* | Reserved variable used for multi-page content |
+| *url* | A URL suitable for creating a link to the page |
+| *render* | Returns the contents of the page as rendered by the Webby filter engine |
+
+h3. Filters
+
+h3. ERB Variables & Methods
+
+h3. Rake Tasks
+
+h3. Site Defaults

data/examples/webby/content/tips_and_tricks/index.txt

@@ -1,35 +1,77 @@
 --- 
 title:      Tips & Tricks
 created_at: Wed Aug 29 08:57:11 -0600 2007
-filter:     textile
+filter:
+- textile
+- outline
 --- 
 <div class="toc push-1">
 
-h4. Table of Contents
-
-* "CodeRay":#toc_cr
+p(title). Table of Contents
 
+<toc />
 </div>
 
-h2(#toc_cr){clear:none}. CodeRay
+h2. Pagination
+
+Pagination is the process of organizing information onto a page such that a fixed number of items appear on each page. Webby provides some methods for paginating information.
+
+Let's assume that your website has a collection of articles in a folder called "articles" in the content directory. The goal is to display these articles ten at a time in reverse chronological order.
+
+<pre>
+---
+title: Articles
+filter: erb
+---
+h2. <%= h(@page.title) %>
+
+<%
+  articles = @pages.find(:limit => :all, :in_directory => "articles",
+                         :sort_by => "mtime", :reverse => true)
+  paginate(articles, 10) do |page|
+%>
+<%= page.render %>
+<hr />
+<% end %>
+
+<%= link_to("Prev", @pager.prev) if @pager.prev? %>
+<%= link_to("Next", @pager.next) if @pager.next? %>
+</pre>
+
+In the example page above, the first step is get the collection of articles we are interested in the paginating. This is done using the <code>@pages.find</code> method to retrieve all the pages from the articles folder sorted in reverse order by modification time. When we have the collection of articles, we pass them to the @paginate@ method along with the desired number of articles per page. The @paginate@ method will pass each page in the @articles@ collection to the supplied block of code, but for each ten pages passed to the block, a new webpage will be created.
+
+Inside the block of code we simple render each page and separate the rendered pages using a horizontal rule. Finally, at the end of each page we generate _Prev_ and _Next_ links to supply navigation.
+
+The <code>@pager</code> object provides a few other useful methods:
+
+* *number*  --  the current page number
+* *number_of_pages*  --  the total number of pages that will be generated
+* *first_item_number*  --  the "item number" of the first item on this page
+* *last_item_number*  --  the "item number" of the last item on this page
+* *first*  --  a reference to the first pager (useful for @link_to@ methods)
+* *last*  --  a reference to the last pager (useful for @link_to@ methods)
+* *page( number )*  --  a reference to the pager for page _number_ (useful for @link_to@ methods)
+
+bq. *NOTE*: the <code>@pager</code> is not instantiated until _after_ the @paginate@ method has been called. Therefore, references to other pages and item numbers cannot be made before the @paginate@ method is called in the page.
+
+h2. CodeRay
 
 To include "CodeRay":http://coderay.rubychan.de/ syntax highlighting support in a page you need to have the @coderay@ gem installed, and you need to include the CodeRay stylesheet in your layout. The following example shows a page that uses CodeRay syntax highlighting combined with Textile markup.
 
-<pre class="code">
+<pre>
 ---
 title:  CodeRay Example
 filter:
-  - erb
-  - coderay
-  - textile
+- erb
+- textile
 --- 
 h2. <%= h(@page.title) %>
 
 This is the @render_page@ function from the Webby static website generation
 system. It is used to render a page by applying the specified filters in
 succession to the page contents.
-<notextile>
-&lt;coderay lang="ruby" line_numbers="inline"&gt;</notextile>
+
+<% coderay(:lang => "ruby", :line_numbers => "inline") do -%>
 # call-seq:
 #    render_page    => string
 #
@@ -46,7 +88,7 @@ def render_page
 
   str
 end
-<notextile>&lt;/coderay&gt;
-</notextile></pre>
+<% end -%>
+</pre>
 
-There are more options that can be passed to the CodeRay syntax highlighter than those shown in the example above. Take a look at the RDoc documentation for the "CodeRay Filter":http://webby.rubyforge.org/rdoc/classes/Webby/CodeRayFilter.html class for more information.
+There are more options that can be passed to the CodeRay syntax highlighter than those shown in the example above. Take a look at the RDoc documentation for the "CodeRay Helper":/rdoc/classes/Webby/Helpers/CodeRayHelper.html class for more information.

data/examples/webby/content/tutorial/index.txt

@@ -25,7 +25,7 @@ content/
 layouts/
 lib/
 output/
-rakelib/
+tasks/
 templates/
 </pre> 
 
@@ -49,7 +49,8 @@ Of course "Lorem Ipsum" is some great content, but if everyone posted their site
 
 <pre class="code">
 --- 
-title:  Home Page
+title:      Home Page
+created_at: Tue Aug 21 17:02:40 -0600 2007
 filter:
   - erb
   - textile
@@ -97,7 +98,7 @@ The output from the command tells you that a new file has been created - @conten
 
 h2. Change the Layout
 
-The next step is to change how the page looks. In fact, we want to change the appearance of all the pages in our website. This is easily by done by changing the website layout file in the _layouts_ folder. Open the *layouts/default.rhtml* file in your favorite editor.
+The next step is to change how the page looks. In fact, we want to change the appearance of all the pages in our website. This is easily done by changing the website layout file in the _layouts_ folder. Open the *layouts/default.rhtml* file in your favorite editor.
 
 <pre class="code">
 --- 
@@ -121,10 +122,10 @@ You'll notice that the layout file has meta-data just like the content files we'
 
 The meta-data of the layout is not made available in the layout itself - just the meta-data of the content file being rendered.
 
-Let's change the layout by removing the sidebar from every page. Find the sidebar div @<div class="column span-3 last">@. Delete that div, run rake to build the website again, and take a look at the site in your browser. You'll notice that both pages have been updated since both depend upon the default layout.
+Let's change the layout by removing the sidebar from every page. Find the sidebar div <notextile><code>&lt;div&nbsp;class="column&nbsp;span-5&nbsp;append-2&nbsp;last"&gt;</code></notextile>. Delete that div, run rake to build the website again, and take a look at the site in your browser. You'll notice that both pages have been updated since both depend upon the default layout.
 
 h2. What Now?
 
 Let your creativity run wild!
 
-You can read more about the features of Webby in the "manual":manual/index.html. There you'll discover how to reference layouts other than the default, how to create page templates for simplifying blog posts. Take a look at the "tips &amp; tricks":tips_and_tricks.html for more ideas on simplifying your web development work cycle.
+You can read more about the features of Webby in the "manual":/manual. There you'll discover how to reference layouts other than the default, how to create page templates for simplifying blog posts. Take a look at the "tips &amp; tricks":/tips_and_tricks for more ideas on simplifying your web development work cycle.

data/examples/webby/layouts/default.rhtml

@@ -38,14 +38,14 @@ filter:
    <div class="column span-4 prepend-1 first" id="navigation">
       <ul
         ><li><%= link_to_page_unless_current 'Home' %></li
-        ><li><%= link_to_page_unless_current 'Download' %></li
         ><li><%= link_to_page_unless_current 'Tutorial' %></li
         ><li><%= link_to_page_unless_current 'Manual' %></li
+        ><li><%= link_to_page_unless_current 'Reference' %></li
         ><li><%= link_to_page_unless_current 'Tips & Tricks' %></li
+        ><li><a href="http://groups.google.com/group/webby-forum">Forum</a></li
         ></ul>
    </div>
 
-
    <div class="column span-16 append-3 last">
       <%= @content %>
    </div>

data/examples/webby/tasks/deploy.rake

@@ -3,15 +3,15 @@ require 'rake/contrib/sshpublisher'
 
 namespace :deploy do
 
-  desc 'deploy to the server using rsync'
+  desc 'Deploy to the server using rsync'
   task :rsync do
     cmd = "rsync #{SITE.rsync_args.join(' ')} "
     cmd << "#{SITE.output_dir}/ #{SITE.host}:#{SITE.remote_dir}"
     sh cmd
   end
 
-  desc 'deploy to the server using ssh'
-  task 'ssh' do
+  desc 'Deploy to the server using ssh'
+  task :ssh do
     Rake::SshDirPublisher.new(
         SITE.host, SITE.remote_dir, SITE.output_dir
     ).upload

data/examples/webby/tasks/growl.rake

@@ -1,5 +1,5 @@
 
-desc 'send log events to Growl (Mac OS X only)'
+desc 'Send log events to Growl (Mac OS X only)'
 task :growl do
   Logging::Logger['Webby'].add_appenders(Logging::Appenders::Growl.new(
     "Webby",

data/examples/webby/tasks/heel.rake

@@ -1,12 +1,12 @@
 
 namespace :heel do
 
-  desc 'start the heel server to view website (not for Windows)'
+  desc 'Start the heel server to view website (not for Windows)'
   task :start do
     sh "heel --root #{SITE.output_dir} --port #{SITE.heel_port} --daemonize"
   end
   
-  desc 'stop the heel server'
+  desc 'Stop the heel server'
   task :stop do
     sh "heel --kill"
   end

data/examples/webby/tasks/validate.rake

@@ -0,0 +1,19 @@
+
+namespace :validate do
+
+  desc 'Validate hyperlinks (exclude exteranl sites)'
+  task :internal => :build do
+    Webby::LinkValidator.validate(:external => false)
+  end
+
+  desc 'Validate hyperlinks (include external sites)'
+  task :external => :build do
+    Webby::LinkValidator.validate(:external => true)
+  end
+
+end  # validate
+
+desc 'Alias to validate:internal'
+task :validate => 'validate:internal'
+
+# EOF

data/lib/webby/builder.rb

@@ -1,4 +1,4 @@
-# $Id: builder.rb 167 2008-02-24 00:59:54Z tim_pease $
+# $Id: builder.rb 192 2008-03-08 16:27:29Z tim_pease $
 
 require 'find'
 require 'fileutils'
@@ -88,7 +88,6 @@ class Builder
     end
 
     load_files if opts[:load_files]
-    loop_check
 
     Resources.pages.each do |page|
       next unless page.dirty? or opts[:rebuild]
@@ -128,27 +127,6 @@ class Builder
     end
   end
 
-  # Loop over all the layout resources looking for circular reference -- a
-  # layout that eventually refers back to itself. These are bad. Raise an
-  # error if one is detected.
-  #
-  def loop_check
-    layouts = Resources.layouts
-
-    layouts.each do |lyt|
-      stack = []
-      while lyt
-        if stack.include? lyt.filename
-          stack << lyt.filename
-          raise Error,
-                "loop detected in layout references: #{stack.join(' > ')}"
-        end
-        stack << lyt.filename
-        lyt = layouts.find :filename => lyt.layout
-      end  # while
-    end  # each
-  end
-
   %w(output_dir layout_dir content_dir).each do |key|
     self.class_eval <<-CODE
       def #{key}( ) ::Webby.site.#{key} end