RE: CMS Site Structures

> In the past I have used two sites, one for displaying the content and
> then another using a different URL for the content administration,
> however there are some drawback relating the file uploading/handling.

With our home-grown ASP.NET CMS, we did the same thing. Two
'applications'...one for admin, one for the front end.

We did this mainly because our backend content will eventually be used on
multiple sites...our intranet, our public site, and possibly some
'sattelite' sites. 

In that sense, we have the content management tool (for entering, editing,
sorting, and meta-data of all the content). And then we have 'site
publishing tools' that connect into this database to render out the content
in various ways. That seems to be a bit of a different way at looking at it
compared to your off-the-shelf all-in-one solution.

Is that better way to do it? I dunno.

-Darrel