On Wed, Aug 20, 2008 at 10:33 AM, cdrick
<cdrick65@gmail.com> wrote:
2008/8/20 stéphane ducasse <ducasse@iam.unibe.ch>:
> you are not the only one :)
>
> Stef
>
I find the difficulty of Pier is its... simplicity, uniformity... A
bit like Smalltalk. All is a structure (wich is meta-described
etc...). It's hard to have a user guide as Pier is more powerful than
a classic CMS or wiki. We could have some but it will inevitably
restricts the usage possibilities of Pier. This said, I think we
could agree on some directions to bring help under the form of
tutorials etc..:
How-To use Pier (user)
1-wiki syntax
How-To use Pier (admin)
2-admin/user right management
3-admin content mamangment (rules)
4-edit versus settings (I think this is important)
5-How to integrate seaside component (easy for a counter, more
complicated when an apps that require its own session...)
6-How-to change the layout, eventually use template here but his is
not "out the box". I think Keith did some work in this area but I
didn't really used it
How-To Develop components for Pier
7-How to interact with Structure, persistency, logs
8-How to create structure (different of a seaside component...)
...
This is just what I'll find useful as documentation... but no time to
help there right now.
Also, I think we need to have an admin page per defaut (that will ease
people management of the Pier site...) - System managements (user
group system update google analytics). Maybe I can find some time in
the next days to do such a page. I can evetually add a default blog
page (with its own environment to display blog related component).
What do you think Lukas ? This is kind of restricting, but that could
be a better default setup for newcomers ? Maybe there's a need for a
"Pier distribution" called... moor ;)
Cheers,
Cédrick