webgen users - Oct 2008 - Config file docs confusing

Hi,

Just a suggestion, but the doc sections about the config file are a bit
unclear.

For example, I just added these config options to my config.yaml, which
seems a bit un-yamlish:

tag.menu.show_current_subtree_only: true
tag.menu.nested: false

I also already had these entries:

default_meta_info:
  Page:
    blocks:
      default: {pipeline: tags,maruku,blocks}
  Template:
    blocks:
      default: {pipeline: tags,maruku,blocks}

So, it is confusing to know for any given config entry what I should put.
When I added my entries, I could have guessed wrong and tried this, which
looks like my existing config.yaml entries:

tag:
  menu:
    show_current_subtree: true

...or this, which looks similar to some of the examples on the config
options reference page:

{tag: {menu: {show_current_subtree: true}}}

So, I guess I''m saying you should have a general section in the docs
about
what exactly config.yaml is for, and what formats are valid to be used in
it, and how these relate to all the possible config options.

Thanks,
-- Chad
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/webgen-users/attachments/20081017/9902cc60/attachment.html>

Am Fri, 17 Oct 2008 05:08:53 -0700
schrieb "Chad Woolley" <thewoolleyman at gmail.com>:
> Hi,
> 
> Just a suggestion, but the doc sections about the config file are a
> bit unclear.
> 
> For example, I just added these config options to my config.yaml,
> which seems a bit un-yamlish:
> 
> tag.menu.show_current_subtree_only: true
> tag.menu.nested: false
> 
> I also already had these entries:
> 
> default_meta_info:
>   Page:
>     blocks:
>       default: {pipeline: tags,maruku,blocks}
>   Template:
>     blocks:
>       default: {pipeline: tags,maruku,blocks}
> 
> So, it is confusing to know for any given config entry what I should
> put. When I added my entries, I could have guessed wrong and tried
> this, which looks like my existing config.yaml entries:
> 
> tag:
>   menu:
>     show_current_subtree: true
> 
> ...or this, which looks similar to some of the examples on the config
> options reference page:
> 
> {tag: {menu: {show_current_subtree: true}}}
> 
> So, I guess I''m saying you should have a general section in the
docs
> about what exactly config.yaml is for, and what formats are valid to
> be used in it, and how these relate to all the possible config
> options.
Thanks for the suggestions! I will make the examples clearer.

-- Thomas