Most often I would say that 'inline' editing is most comfortable for the users. The only proviso would be where the user requries to make several updates across a number of pages, and all need to be viewed and authorised together. Some systems provide this 'unpublished mode' where the author can see all the changes across several pages, others allow only a 'preview' of the current page. One note of detail, if your page is made up of several content elements, some systems provide an icon to directly edit each content element (so there are several 'edit' options on the page, not just one at the top. Julian Voelcker [EMAIL-REMOVED]> wrote: What do you think is the best way to present a content editor to the end users. We currently use a completely separate site that users have to log in to and then go through a page listing to find a page they want to edit. They can also edit a number of other elements for the site. Other systems I have seen provide a facility so that after you have logged in, one or more edit buttons will appear at the top of each page. Which do you think is the best approach? I am toying with our current structure, but introducing a facility so that the user can browse the site to select a page to edit as well. Any thoughts would be appreciated. -- Cheers, Julian Voelcker The Virtual World (UK) Limited Cirencester, United Kingdom -- http://cms-list.org/ please trim your posts. --------------------------------- Want to chat instantly with your online friends? Get the FREE Yahoo!Messenger --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- -- http://cms-list.org/ please trim your posts.
