RE: Link Management
Dominic Cronin <Dominic.Cronin-g7/[email protected]>
| Newsgroups | gmane.comp.cms.cms-forum.general |
|---|---|
| Message-ID | <65461C1A6FEE3A45814FA70665901DD69F7708@NL1EXCH01> |
This discussion at W3C is probably relevant. http://www.w3.org/Provider/Style/URI.html In other words, you can move your stuff, but it should still be where it was. D -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Robert Koberg Sent: 15 September 2004 11:51 To: James Robertson Cc: [email protected] Subject: Re: [CMS] Link Management James Robertson wrote: > >> To me, a redirect is an ugly hack. And to me, the CMS should build >> document relative links (as opposed to root relative) so a site can >> be dropped anywhere. >> >> This type of feature was one of most important when building our CMS. >> Since we focused on a storyboard metaphor, we started with the >> assumption that the site changes a great deal at least when starting >> -- build it, try it for usablity, rebuild based on feedback, rinse, >> lather, repeat... > > > Rob, > > Relative URLs are a good thing, but solve a quite different > problem to the one we're talking about. > > The situation that causes problems is when a file is moved > from one section of the site to another. This might make the > URL change as follows: > > www.site.com/about/background/ --> www.site.com/seminars/background/ > > In this situation, external visitors who have bookmarked the first > URL would get a page-not-found. This is where the CMS needs to > automatically generate redirects (or rewriting, etc) when pages > are moved in the site hierarchy. This is a different problem than I thought we were discussing. I thought we were discussing link management within the CMS (I discussed that in a different post or two). I also have posted why I felt relying on redirects for link management /in the CMS/ was not a good idea. I guess the bookmarking problem would be better handled by a CMS that edits the live site directly and has the ability/knowledge to affect the webserver. I personally don't think a CMS should edit the live site directly without a development and QA stage, but that is a different topic. best, -Rob > > Cheers, > James > > ------------------------- > James Robertson > Step Two Designs Pty Ltd > Knowledge Management / Content Management / Intranets > > http://www.steptwo.com.au/ > [email protected] > _______________________________________________ cms mailing list [email protected] Subscription controls: http://lists.cms-forum.org/mailman/listinfo/cms Netiquette FAQ and related CMS lists - [CMS-Forum], [CMS-Meta], [CMS-PR], [CMS-Develop] http://www.cmsreview.com/NetiquetteFAQ.html