OK, I've read loads of docs all over the place and havn't come across how, or if the CMS works for front end users....
Maybe I'm missing something but all I want to know is how SilverStripe works for my client.
I've set up a user group and changed their permissions to only edit pages (not security admin etc.)
But seeing the back end is a bit of an overkill for what I had in mind... is this the only option?
Is it possible to lets say have the "home" page with some text, and an image, which after logging in they can edit at the front end with the TinyMCE editor or something... and if so what do I need to make this happen.
Sorry if this is already documented somewhere but Im struggling to find it.
You can remove the options/tabs/fields from the CMS if you don't want them to see it, and just leave them with what you want.
For example, for sites that don't have page comments, you might have this in your _config.php:
I seem to recall a feature request for a 'quick page edit' sort of tool, but I don't think anyone has built it yet (perhaps have a look at the experimental Wiki module for ideas here). If you build it, I'm sure others will be interested.
I'll give ur example a shot, seeing as I don't need comments that is something I will want to change.
Previously I was using a newsmanager ext. in MODx to do this kind of thing it would be a very valuable tool, I don't think I have the skills to build my own... maybe someone else would be interested.
It would mean that a new button would appear for logged in users (with the correct permissions) when viewing the front end. Such as "Edit Page" on the home page this would then open a form to edit the specified fields using TinyMCE and lightbox or somthing. Click "Save" and its done. I suppose this is very similar to the CMS anyway... but the point would be to make it very very simple for the client and they dont need to get to grips with the UI of the CMS. I know a lot of users would find this beneficial.
@pinkpoliceman - Silverstripe isn't exactly designed to be a WYSIWYG frontend as you describe. The real power here is a layered and extensible backend based on the Sapphire framework.
If you don't want to develop such functionality (I know some folks have done it in SS) you may want to evaluate other software that will support users with simple needs out-of-the-box. I would recommend WebGUI offhand. The site is a bit overwhelming, but just check out the demo: