[giapeto] Giapeto usage - who relies on it?

[Chuck Hagenbuch]

Quoting Roel Gloudemans <roel at gloudemans.info>:

> Just my thoughts on Giapeto. I think now is the time to spill'em... :-)
> (and hoping to start a discussion on what the final product should look
> like)

I've taken a while to respond to this, but yes, that's what I was 
hoping for too. :)

> ** Blocks **
> From the Wiki:
>
> * Rely on Horde_Template blocks integration, instead of "main" content
> area with confusing block splitting?
>
> I actually quite like the block splitting. It is quite an easy way to
> create page layouts. However:

Okay, I can see that.

> 1) The splitting should be more intelligent. e.g. if you split the top
> block of 2 vertical aligned blocks the content of the bottom block ends
> up in the top-right block

Something to add to the roadmap or to create a ticket for.

> 2) Some kind of block level templates (in addition to pagelevel
> templates) should be nice (e.g. when you give the block a title at the
> moment you get another block layout). However we should make it in such
> a way that CSS from one block doesn't spillover into another

Unless we do search and replace on classnames, this is technically 
impossible, the way CSS works.

> 3) Versioning for the templates would be nice, but not a requirement
> (versioning for the contents is more important)

Indeed.

> ** Workflow **
> On the workflow; There are several possibilities:
> 1) The same as in Jonah; set a release date for the page/block
> 2) Require signoff from another Horde user
> 3) Both. This would be best. The designer/pagebuilder creates the page
> and e.g. marketing signs off the page and sets the release date.

I'd actually like to see a general workflow designer.

> ** Templates **
> I don't know if we should include a template editor. Mine are actually
> quite complex, you wouldn't want to build an editor for those ;-). And
> editor for block level templates would be quite handy though. Same goes
> for storage in VFS. I would prefer the global page templates to be on
> disk (this is handier for development; if you really need access to it
> you can always use gollem) and the block level templates to be in VFS
> (I think the latter would also be more dynamic)

I want to move away from the assumption that the person using Giapeto 
is the server admin, which almost requires putting all templates in the 
VFS. I'd also like Giapeto to be able to serve multiple sites - again, 
need to get away from the filesystem. That's the main reason for the 
move to put templates into VFS.

-chuck

-- 
"But she goes not abroad in search of monsters to destroy." - John 
Quincy Adams