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 released every two weeks. I know there must be a few of you out there that have done this already so I thought I'd ask the list for any advice from the trenches before I start. I'm unsure of whether I should keep all the content in the database or if I should use [included] text files. This raises the issue of whether the site could be indexed by the search robots vs whether I can perform WebCat searches on the content. The client also wants to keep a searchable archive of back issues as well. At some point, with two per month, the database size would become too large. I'm considering a system where the current site is in the database and archived content is created with [writefile] contexts each time a new issue is launched. At that point the archives would be static pages suitable for robot spidering but unsuitable for WebCat searching of content. Also, what method(s) of version control have been successful with your clients. What I mean by that is administrating the switching of new issues to the live site while retiring the last issue. Any other issues regarding this kind of site that could be helpful would also be appreciated.Thanks in advance, Mike Davis Associated Messages, from the most recent to the oldest:

    
  1. Re: Converting a Magazine to a Web Site with WebCat (Peter Ostry 1999)
  2. Re: Converting a Magazine to a Web Site with WebCat (webcat 1999)
  3. Converting a Magazine to a Web Site with WebCat (Mike_Davis 1999)
Hello, I'm just about to start designing a site for a magazine that is released every two weeks. I know there must be a few of you out there that have done this already so I thought I'd ask the list for any advice from the trenches before I start. I'm unsure of whether I should keep all the content in the database or if I should use [included] text files. This raises the issue of whether the site could be indexed by the search robots vs whether I can perform WebCat searches on the content. The client also wants to keep a searchable archive of back issues as well. At some point, with two per month, the database size would become too large. I'm considering a system where the current site is in the database and archived content is created with [writefile] contexts each time a new issue is launched. At that point the archives would be static pages suitable for robot spidering but unsuitable for WebCat searching of content. Also, what method(s) of version control have been successful with your clients. What I mean by that is administrating the switching of new issues to the live site while retiring the last issue. Any other issues regarding this kind of site that could be helpful 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)