Comment: YACS 6.4: subscriptors, centralised user database, aggregation, usability

Tof: Actually YACS support a special flavor of groups, which is blended in web spaces. I know that this sounds quite unusual, but it has proven to be very efficient because it's visual. Look at some section and you will immedialtely know who is allowed to do something special here.

Also, when you comment some page YACS will automatically add this page to your watch list, even if you have not started the thread. This means you should receive a message on subsequent comments sent to this page. And this feature does not work it's a bug...

For me, the issue for page.php is not the same than for skin.php. Every skin is supposed to feature some skin.php, therefore the creation of skin_skeleton.php to have a nice library in the background. But within a template you are perfectly free to use, or not, page.php, or another derived script like altaPage.php. My feeling is that the creation of a page_skeleton.php would only add complexity to all skins, without a real necessity to do that. Therefore, for the third point you must admit that "altaPage.php" is a very nice name, and it is definitely pretty, if this is what you wanted to achieve.

Thank you for your valid input, and interest in YACS.