RE: CMS Site Structures

Hi Julian,
	Word of warning: Watch you don't get caught in the trap where
your public site templates become your admin site interfaces.  There
needs to be a clear distinction especially if you want to handle
multiple publications with multiple template sets for different
platforms (wap, rtf, pdf etc).  I've always believed it to be important
to allow content editing without templates - if you truly want to
separate content from presentation.

a+,a.

André Milton – CTO

mLore Inc
[email protected]
(514)395-4455 x 2
Use the cube : mcubes.com


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Julian Voelcker
Sent: Tuesday, January 18, 2005 10:19 AM
To: [email protected]
Subject: [CMS] CMS Site Structures

I am currently re-developing my home grown ASP.Net based CMS 
application and am debating changing the way that I structure the admin 
system.

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.

I am now considering moving the administration site into a sub 
directory of the main site, which will get over some of the drawbacks, 
but could present other issues.

How do most other CMS applications structure their sites.


Any pointers or views would be appreciate.

Cheers,

Julian Voelcker


_______________________________________________
cms mailing list
[email protected]
Subscription controls:
http://lists.cms-forum.org/mailman/listinfo/cms
Netiquette FAQ and related CMS lists - [cms-forum], [cms-pr],
[contentmanagers], [cmpros]
http://www.cmsreview.com/NetiquetteFAQ.html