Converting a Magazine to a Web Site with WebCat
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 23656
interpreted = N
texte = Hello, I'm just about to start designing a site for a magazine that is releasedevery two weeks. I know there must be a few of you out there that have donethis already so I thought I'd ask the list for any advice from the trenchesbefore I start. I'm unsure of whether I should keep all the content in thedatabase or if I should use [included] text files. This raises the issue ofwhether the site could be indexed by the search robots vs whether I canperform WebCat searches on the content. The client also wants to keep asearchable archive of back issues as well. At some point, with two permonth, the database size would become too large. I'm considering a systemwhere the current site is in the database and archived content is createdwith [writefile] contexts each time a new issue is launched. At thatpoint the archives would be static pages suitable for robot spidering butunsuitable for WebCat searching of content. Also, what method(s) of versioncontrol have been successful with your clients. What I mean by that isadministrating the switching of new issues to the live site while retiringthe last issue. Any other issues regarding this kind of site that could behelpful would also be appreciated.Thanks in advance,Mike Davis
Associated Messages, from the most recent to the oldest:
Hello, I'm just about to start designing a site for a magazine that is releasedevery two weeks. I know there must be a few of you out there that have donethis already so I thought I'd ask the list for any advice from the trenchesbefore I start. I'm unsure of whether I should keep all the content in thedatabase or if I should use [included] text files. This raises the issue ofwhether the site could be indexed by the search robots vs whether I canperform WebCat searches on the content. The client also wants to keep asearchable archive of back issues as well. At some point, with two permonth, the database size would become too large. I'm considering a systemwhere the current site is in the database and archived content is createdwith
[writefile] contexts each time a new issue is launched. At thatpoint the archives would be static pages suitable for robot spidering butunsuitable for WebCat searching of content. Also, what method(s) of versioncontrol have been successful with your clients. What I mean by that isadministrating the switching of new issues to the live site while retiringthe last issue. Any other issues regarding this kind of site that could behelpful would also be appreciated.Thanks in advance,Mike Davis
Mike_Davis
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
I'm having trouble using [url][interpret][math] together inlookup (1997)
Database Updates (1997)
Multiple Unique SKUs (2000)
Dumb Question about Docs (1997)
Problem 2: Prefs file... (1997)
calculating tax rates, mail order solutions and version 2 (1997)
[ShowNext] (2007)
Checking two required fields (1998)
really wierd date stuff on NT (1997)
$purchase WITHOUT creditcar (1997)
[WebDNA] Which OS? (2009)
Can I invoke an ssi plugin from within a webcat page (1997)
Incrementing a number (1998)
Showif date > other date (2004)
Sami (1998)
Changing user submitted data (2000)
OH CRAP!!!!!- Template not found error!!! (1999)
formulas.db problem solved (1998)
Tag Corruption (2000)
Paypal merchant code tricks or pitfalls (2003)