I'm experimenting at the moment with "dynamic pages". I just need to extend
the static pages by one level. I did a subclass of PRPage that answers true on hasChildren
call so that PRPathLookup does accept the path being requested. If the page is really
requested the last path component is taken as query for an object. I then take a
"template page" copy its document and set the parent to the right page. Beside
having the need for returning a dummy page on a children call this works out pretty good.
If you understand that rather cryptic description :) you may have some hints about that.
The second approach is to have something like WATask in pier style. The pages
shouldn't be directly accessible via URL. The task should work on editabel pier pages
that pass/inject the right objects into page. Let's say there is a three steps task I
want to solve. I would start by taking on template page (copying its document) and
embedding the first form. On answer it will take the next template page and injects the
results from the previous step into the new page. This would lead to a task where the
textual decoration and such could be changed by editors and the task by programmers.
I'm sorry but I don't know how I can explain that in a more understandable
fashion. But maybe you understand it and have some hints or pointers how to approach that