Menus-the same issue
OK I'm cobfused-this is the third time I've posted this reply-if it turns up elsewhere my apologies.
I've had some similarly technical answers on this sort of issue which I genuinely do appreciate, but I also have to say that the whole point of a site builder package is that its for people like me who don't 'speak' sql or php etc. All I want to do is enable clients to log in to the Powercms admin area, create a page (no problem-tell it its a template when you set the site up), edit the page, (again, no problem) and then... here's the tricky bit-create a menu item to link it too.
In "help" it says : "Once you have updated the content, click the Create Link option to see how you can create a link to this new page." I wa s keen to do this-but all I can find is the 'insert/edit link" button in the WYSIWYG Fckeditor. This will insert an inline hyperlink-not a menu item. So a link can be inserted (the dialogue box brought up by the insert link button insists there are no pages or files to link to, so I can't even do it that way, but that's another issue).
Clearly you need to define the top navigation or other menu as an editable part of the site. I cannot figure out how to add an area into the template using SiteSculptor that will be a menu that shows up in the CMS admin area-it looks like I need some pretty advanced programming knowledge in Sql etc to do this, involving recordsets, and hand manipulation of tables in a mySql database...-which is a shame as something like SiteSculptor is aimed at people like me who don't have these skills.
So my conclusion is that Sitesculptor, great as it is at doing what it does , doesn't seem let you/enable you to include an option for clients to add/edit a menu item-you have to do that as the designer-and once the site is on a server it has to be hand coded. All menus seem to be fixed at design stage-client has no access. I'm not suggesting it's Webassist's fault, (caveat emptor etc) but I do feel I spent $100 or so on something with a crucial shortcoming, in that (and I'd love to be shown I'm wrong!) CSS Menu Writer and SiteSculptor don't communicate once the site is deployed on a server. It does what it does well, but seems that it utterly fails to enable clients to do what surely nearly all will need to do-at least in any accessible way to non mySql speaking mortals like me. I really don't get it. I'd really love to be wrong but I think this just doesn't do what I need it to do.