webgen users - Aug 2008 - dumb upgrade questions and complaining

Hello,

I have read the upgrade docs, but I''m still confused.

Can you tell me exactly what I have to do to use textile instead of
maruku?  I put the following at the top of my default.template, but it
did not help:

--- name:content pipeline:tags,textile,blocks

I''m almost positive that is not correct, but I''m not sure what
I''m
supposed to do.  Not to be critical, but the upgrade guide
(http://webgen.rubyforge.org/documentation/0.5.x/upgrading.html ) is
confusing.

I''d like to just know what to do to make my existing textile-formatted
site work, step by step.  I don''t really have time to learn about
content processor blocks and pipelines.

To be honest, I would like to see either a cleaner deprecation path or
much clearer and more explicit upgrade documentation.  I guess I
should just stay on the old version, but I don''t really want to do
that either.  It feels like there should be some more hand-holding for
current users - if I''m going to learn something completely new and
redesign my site anyway, I''ve more inclined to try a different tool,
like webby.  Not saying that *I''m* going to do that, just that some
people might ;)

Thanks,
-- Chad

> Can you tell me exactly what I have to do to use textile instead of
> maruku?  I put the following at the top of my default.template, but it
> did not help:
> 
> --- name:content pipeline:tags,textile,blocks
The textile processor is RedCloth, so you need to specify redcloth
instead of textile. I just realized that this is a little odd and have
added an alias for it named textile.

If you want to change the default pipeline for page and template files,
put the following in your config.yaml:

default_meta_info:
  Page:
    blocks:
      default: {pipeline: erb,tags,redcloth,blocks}
  Template:
    blocks:
      default: {pipeline: erb,tags,redcloth,blocks}

This states that page and template files should be processed by erb,
then by webgen tags, then by RedCloth and finally the blocks should be
substituted. And by writing this, I think I will implement another
configuration helper to make setting this easier.
> I''m almost positive that is not correct, but I''m not sure
what I''m
> supposed to do.  Not to be critical, but the upgrade guide
> (http://webgen.rubyforge.org/documentation/0.5.x/upgrading.html ) is
> confusing.
> 
> I''d like to just know what to do to make my existing
textile-formatted
> site work, step by step.  I don''t really have time to learn about
> content processor blocks and pipelines.
1) Edit your config.yaml like stated above
2) Migrate your metainfo.yaml like stated in the upgrading guide
3) Replace every occurence of {block: BLOCK_NAME} with <webgen:block
name=''BLOCK_NAME'' /> in page/template files.
4) Change the meta information names like stated in the upgrading guide
5) Write to the mailing list if there are still problems, I will do my
best to help you!
 
> To be honest, I would like to see either a cleaner deprecation path or
> much clearer and more explicit upgrade documentation.  I guess I
> should just stay on the old version, but I don''t really want to do
> that either.  It feels like there should be some more hand-holding for
> current users - if I''m going to learn something completely new and
> redesign my site anyway, I''ve more inclined to try a different
tool,
> like webby.  Not saying that *I''m* going to do that, just that
some
> people might ;)
The good thing is: you don''t need to redesign your site :) Although
webgen''s core was completely overhauled, the basic principle of a
webgen website stays the same. There were just some needed adjustments
which provide much more flexibility than before. And the price is that
old websites have to be adjusted. I will try to improve the upgrading
instructions.

-- Thomas