Re: [WebDNA] Pretty URLS
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106575
interpreted = N
texte = This looks like a PITA to create and manage. I guess I've outgrown the desire to complicate things just because I can. Why not just use a daily script to generate a folder full of static pages, one for each sku, and be done with it? Sincerely, Kenneth Grome > What I think I'd like to do is tie into the page not > found system, i.e. have the server send my 404 request > to instead of error.html to URLs.tpl > > that way all pages act as they do currently BUT > for any "pretty" URL, it gets "not found" and rerouted to > URLs.tpl > > and inside that file i want to do something like: (yes > this is 100% wrong, just typing outloud here) [showif > [url][thispage][/url]=[grep]('notebook_battery/$')[/grep > ]] [include file=alphamfg.tpl&_CID=2][/showif] [showif > [url][thispage][/url]=[grep]('('notebook_battery/(?P
>\w+)/$')[/grep]] [include > file=pickmodel&_CID=2&_MFG=[MFG]][/showif] [showif > [url][thispage][/url]=[grep]('('notebook_battery/(?P >[^/]+)/(?P\d+).*')[/grep]] [include > file=modelinfo&_CID=2&_MFG=[MFG]&_FID=[FID]][/showif] > > (and have a last rule that actually redirects to a 404 > page...) > > I want to figure out how to use an include so that i'm > specifically not rewriting and redirecting the URL (thus > making it ugly) > > Anyone currently doing anything like this? > If I can figure out how to do it, is anyone else > interested in the code? > > > > > Brian B. Burton > brian@burtons.com > > ================================= > time is precious. waste it wisely > ================================= > > On Apr 27, 2011, at 6:22 AM, William DeVaul wrote: > > On Tue, Apr 26, 2011 at 11:38 PM, Kenneth Grome wrote: > >>> I'm not sure why you'd leave the humans ugly URLs. > >> > >> Because those URLs are the default URLs for WebDNA. > > > > I thought the parameterized URLs were a convention that > > came about in the early days of the Internet. Seems > > the convention is ripe for change. > > > > In general, I'm for programmer convenience versus > > optimization for the computer. But I'd put user > > convenience above the programmer's. In some > > frameworks the default is "prettier" to the benefit of > > users and programmers. > > > >>> The search engines like keywords. > >> > >> They get plenty of keywords in the static pages. > > > > I think it is about quality of the keyword placement > > (in incoming links, in the domain, in the URLs, in > > "important" tags e.g. ). > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
This looks like a PITA to create and manage. I guess I've outgrown the desire to complicate things just because I can. Why not just use a daily script to generate a folder full of static pages, one for each sku, and be done with it? Sincerely, Kenneth Grome > What I think I'd like to do is tie into the page not > found system, i.e. have the server send my 404 request > to instead of error.html to URLs.tpl > > that way all pages act as they do currently BUT > for any "pretty" URL, it gets "not found" and rerouted to > URLs.tpl > > and inside that file i want to do something like: (yes > this is 100% wrong, just typing outloud here) [showif > [url][thispage][/url]=[grep]('notebook_battery/$')[/grep > ]] [include file=alphamfg.tpl&_CID=2][/showif] [showif > [url][thispage][/url]=[grep]('('notebook_battery/(?P >\w+)/$')[/grep]] [include > file=pickmodel&_CID=2&_MFG=[MFG]][/showif] [showif > [url][thispage][/url]=[grep]('('notebook_battery/(?P >[^/]+)/(?P\d+).*')[/grep]] [include > file=modelinfo&_CID=2&_MFG=[MFG]&_FID=[FID]][/showif] > > (and have a last rule that actually redirects to a 404 > page...) > > I want to figure out how to use an include so that i'm > specifically not rewriting and redirecting the URL (thus > making it ugly) > > Anyone currently doing anything like this? > If I can figure out how to do it, is anyone else > interested in the code? > > > > > Brian B. Burton > brian@burtons.com > > ================================= > time is precious. waste it wisely > ================================= > > On Apr 27, 2011, at 6:22 AM, William DeVaul wrote: > > On Tue, Apr 26, 2011 at 11:38 PM, Kenneth Grome wrote: > >>> I'm not sure why you'd leave the humans ugly URLs. > >> > >> Because those URLs are the default URLs for WebDNA. > > > > I thought the parameterized URLs were a convention that > > came about in the early days of the Internet. Seems > > the convention is ripe for change. > > > > In general, I'm for programmer convenience versus > > optimization for the computer. But I'd put user > > convenience above the programmer's. In some > > frameworks the default is "prettier" to the benefit of > > users and programmers. > > > >>> The search engines like keywords. > >> > >> They get plenty of keywords in the static pages. > > > > I think it is about quality of the keyword placement > > (in incoming links, in the domain, in the URLs, in > > "important" tags e.g.