1 person found this helpful
To minimize the client's need for technical know-how (primarily uploading a revised xml file, etc), my approach would be to create an interface that has each element the client can edit that they can submit (click a button) for storage to a datafile or database. The web site file would read from the datafile/database to populate the content.
Thanks Ned. That's what I'd prefer to offer the client, but if the interface shows all the editable text from a particular state/page, eg headings and body text together, then I will have to handle styles to some extent which I want to avoid. I could restrict all my text blocks to a single text format, ie one block for the heading, another for body etc, and providing editing of individual blocks only. But I was wondering about using HTML-formatted text and making use of an existing editor - similar to that used on this forum and on countless other sites.
Individual blocks is what I was alluding to. In my scenario, the client has to live with the format the site is designed around--but that's just me... I tend to be on the shy side when it comes to suggesting design approaches that are going to cost my clients lots more. You could design an editor that does all the nice things these editing interfaces do, but who do you charge for the time spent doing it? And then you have to spend extra time designing the Flash site to be self adjusting for the untold freedom the client now has... html pages are more forgiving in that aspect because they can expand, but Flash sites are limited by their stage borders.
Ok, we're agreed then! I'll try the individual text block approach.
Thanks for your input.