Re: [WebDNA] Pretty URLS
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106576
interpreted = N
texte = the website in question sells replacement parts, so skus =3D couple = thousand. Things they fit into =3D couple hundred thousand. Oh, and = people google search for the thing the parts fit into. So I'd have a few = hundred thousand static pages, which although automated, is still quite = messy.=20 On Apr 27, 2011, at 10:13 AM, Kenneth Grome wrote: > This looks like a PITA to create and manage. I guess I've=20 > outgrown the desire to complicate things just because I can. =20 > Why not just use a daily script to generate a folder full of=20 > static pages, one for each sku, and be done with it? >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 >> 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 >>=20 >> that way all pages act as they do currently BUT >> for any "pretty" URL, it gets "not found" and rerouted to >> URLs.tpl >>=20 >> and inside that file i want to do something like: (yes >> this is 100% wrong, just typing outloud here) [showif >> [url][thispage][/url]=3D[grep]('notebook_battery/$')[/grep >> ]] [include file=3Dalphamfg.tpl&_CID=3D2][/showif] [showif >> [url][thispage][/url]=3D[grep]('('notebook_battery/(?P
>> \w+)/$')[/grep]] [include >> file=3Dpickmodel&_CID=3D2&_MFG=3D[MFG]][/showif] [showif >> [url][thispage][/url]=3D[grep]('('notebook_battery/(?P>> [^/]+)/(?P\d+).*')[/grep]] [include >> file=3Dmodelinfo&_CID=3D2&_MFG=3D[MFG]&_FID=3D[FID]][/showif] >>=20 >> (and have a last rule that actually redirects to a 404 >> page...) >>=20 >> 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) >>=20 >> Anyone currently doing anything like this? >> If I can figure out how to do it, is anyone else >> interested in the code? >>=20 >>=20 >>=20 >>=20 >> Brian B. Burton >> brian@burtons.com >>=20 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> time is precious. waste it wisely >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=20 >> On Apr 27, 2011, at 6:22 AM, William DeVaul wrote: >>> On Tue, Apr 26, 2011 at 11:38 PM, Kenneth Grome=20 > wrote: >>>>> I'm not sure why you'd leave the humans ugly URLs. >>>>=20 >>>> Because those URLs are the default URLs for WebDNA. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>>>> The search engines like keywords. >>>>=20 >>>> They get plenty of keywords in the static pages. >>>=20 >>> I think it is about quality of the keyword placement >>> (in incoming links, in the domain, in the URLs, in >>> "important" tags e.g. ). >>=20 >> --------------------------------------------------------- >> 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 > --------------------------------------------------------- > 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 >=20
Associated Messages, from the most recent to the oldest:
the website in question sells replacement parts, so skus =3D couple = thousand. Things they fit into =3D couple hundred thousand. Oh, and = people google search for the thing the parts fit into. So I'd have a few = hundred thousand static pages, which although automated, is still quite = messy.=20 On Apr 27, 2011, at 10:13 AM, Kenneth Grome wrote: > This looks like a PITA to create and manage. I guess I've=20 > outgrown the desire to complicate things just because I can. =20 > Why not just use a daily script to generate a folder full of=20 > static pages, one for each sku, and be done with it? >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 >> 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 >>=20 >> that way all pages act as they do currently BUT >> for any "pretty" URL, it gets "not found" and rerouted to >> URLs.tpl >>=20 >> and inside that file i want to do something like: (yes >> this is 100% wrong, just typing outloud here) [showif >> [url][thispage][/url]=3D[grep]('notebook_battery/$')[/grep >> ]] [include file=3Dalphamfg.tpl&_CID=3D2][/showif] [showif >> [url][thispage][/url]=3D[grep]('('notebook_battery/(?P>> \w+)/$')[/grep]] [include >> file=3Dpickmodel&_CID=3D2&_MFG=3D[MFG]][/showif] [showif >> [url][thispage][/url]=3D[grep]('('notebook_battery/(?P>> [^/]+)/(?P\d+).*')[/grep]] [include >> file=3Dmodelinfo&_CID=3D2&_MFG=3D[MFG]&_FID=3D[FID]][/showif] >>=20 >> (and have a last rule that actually redirects to a 404 >> page...) >>=20 >> 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) >>=20 >> Anyone currently doing anything like this? >> If I can figure out how to do it, is anyone else >> interested in the code? >>=20 >>=20 >>=20 >>=20 >> Brian B. Burton >> brian@burtons.com >>=20 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> time is precious. waste it wisely >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=20 >> On Apr 27, 2011, at 6:22 AM, William DeVaul wrote: >>> On Tue, Apr 26, 2011 at 11:38 PM, Kenneth Grome=20 > wrote: >>>>> I'm not sure why you'd leave the humans ugly URLs. >>>>=20 >>>> Because those URLs are the default URLs for WebDNA. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>>>> The search engines like keywords. >>>>=20 >>>> They get plenty of keywords in the static pages. >>>=20 >>> I think it is about quality of the keyword placement >>> (in incoming links, in the domain, in the URLs, in >>> "important" tags e.g.