My response keeps on getting too long. I wish I could find you on AIM to chat :(
My suggestion is to start with the database, then do the coding, and then move to css. It will just make everything else easier in the long run, because once you're done, if you get a new idea, you're much more likely to only need to change one line in one files as opposed to thirty in each of twelve.
I'd love to see an advanced (database-driven) search engine, where I could enter in the pairing, the time, and a keyword, to find that story I forgot about. But having no idea how you have things set up under the hood, I have no idea if that's ridiculously complicated. But I suspect I have a searching fetish when it comes to archive sites ;)
If I continue, I'll just sound greedy. I think it's the problem with me actually trusting you to do a good job, I just want everying possible. Like logins for reviews. (Which could help you to automate the author Q&As and beta lists and eliminate the drive-by spamming, I'm not being totally selfish.)
(no subject)
Date: 2004-01-03 12:52 am (UTC)My suggestion is to start with the database, then do the coding, and then move to css. It will just make everything else easier in the long run, because once you're done, if you get a new idea, you're much more likely to only need to change one line in one files as opposed to thirty in each of twelve.
I'd love to see an advanced (database-driven) search engine, where I could enter in the pairing, the time, and a keyword, to find that story I forgot about. But having no idea how you have things set up under the hood, I have no idea if that's ridiculously complicated. But I suspect I have a searching fetish when it comes to archive sites ;)
If I continue, I'll just sound greedy. I think it's the problem with me actually trusting you to do a good job, I just want everying possible. Like logins for reviews. (Which could help you to automate the author Q&As and beta lists and eliminate the drive-by spamming, I'm not being totally selfish.)