embed the root page
+/information/license+ to embed the license
+..+ to embed the parent structure
Ok, the light is going on! Finally.
Of course I have more questions. My experimenting
leads me to believe
that there is one Design for the entire kernel, is this true?
No. The page "/environment" defines the default design (it is sort of
a meta-page for Pier). In the settings of the root page you see that
the environment is set to "/environment".
I am hoping that I can customize the design on a per
page basis as
opposed to having one global design.
Now you can copy the default environment, modify it and go to a
different page. In the settings of this other page you select the
copied environment. Here you go, now you have two different designs.
Child structures will inherit the design of their parent, if the
structure does not define the design.
Another question: How does one go about creating a new
will guide you through the process of creating a new kernel and
register it as a Seaside entry point. You might want to have a look at
that code, to see how it exactly works (essentially it just creates an
instance of PRKernel, creates a new Seaside application and tells it
to use the new kernel instance).