> The next question that comes to mind is how to structure the > domains / subdomains for the CMS's.
Rick, How about using DNS wildcard? Lots of app-as-a-service sites already use it. You can register a single generic sounding domain like realtoroffice.net. Then pre-append your client's company name on the URL like http:// Stickfordhomes.realtoroffice.net . This way, you do not need to manage any subdomains. Michael > -----Original Message----- > From: Rick Faircloth [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 02, 2006 8:16 AM > To: CF-Talk > Subject: RE: Advice needed on how to proceed with app... > > Now, after our little Farcry sidebar (which I have no plans to use, cause > I like to build my own, even while simpler, at least I understand it and > can > troubleshoot it much easier)... back to my original question, or at least > a continuation thereof... > > If I decide to take this approach: > > - Build Custom Front Ends > - Build a CMS for all relevant sites to use > - Build a database for each client's site > > The next question that comes to mind is how to structure the > domains / subdomains for the CMS's. > > If I'm *only* doing a CMS for Real Estate agents, then I can create > a subdomain for my domain, whitestonemedia.com, called > REA.WhiteStoneMedia.com, > and send them all to that for content management. I found that using > subdomains > like this confuses many clients who think that www has to be in there > somewhere, > and they end up trying to go to www.REA.WhiteStoneMedia.com, which, of > course, > doesn't work and leads to phone calls from them trying to figure out why > they can't > access their sites... > > If I build a CMS for churches (my next project) and their sites, then I > could > use a subdomain called, say, CMS.WhiteStoneMedia.com (Church Management > System > for this particular CMS acronym), and send my client's there for content > management. > > Is this the way to go? Or should I have dedicated domains for each > category > of site, > such as www.RealEstateSiteManager.com for agents and > www.ChurchSiteManager.com > for churches. > > It would be nice, and feel more personal to the client if I could tie > their > domain name into > the CMS name, somehow. Perhaps this where Aliases in DNS come into play? > Let's say I have > a single site manager for Real Estate agents, then an agent's site called > www.StrickfordHomes.com. > For their site manager, I use a subdomain called cms.StrickfordHomes.com. > I > then use an alias > and forward them to my overall CMS site for Real Estate agents, called > REA.WhiteStoneMedia.com. > Would that be a better approach? > > Or is there a better way (probably) that I haven't considered, yet? > > Rick > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262609 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
