A few notes

Before you go off and create your own content systems and come running to me when they don't work, let me mention a few things here.

One of the biggest concerns is security and user permissions. On one hand, you'd like to give writers enough permissions to do everything they need to do without having to bother you, but on the other hand, you don't want to give out too many permissions for fear of security risks. One way would be to put all this good stuff in a protected directory, that only authenticated users can access ( go here for a tutorial on how to set up protected folders). This makes sure the public can't find your system and start bombarding you with junky articles and such. You might also want to deny your writers access to the editor functions we spoke about in the previous page.

So the system works, but when you go and view the page, none of the images appear. What now? Well, there could be a few causes here. Did you verify the image sources in the HTML? And are the images in the correct directories? Remember if you used the FSO to move your files, you have to move, or at least rereference, your images too. Another sneaky culprit is directory permissions. Make sure that all files placed in the directories are viewable by internet users. In NT, this means making sure the files inherit the permissions of the directory.

Another thing to keep in mind is stray files. Every time you go through the submission process, you'll probably end up with a new set of files. Many times, for whatever reason, these files won't get published, possibly because they were test or duplicate files, deadlines changed, etc. By keeping track of things in the database, you are able to see what files are there. Make sure that if you delete something from the database, you delete the actual file as well. Otherwise you'll end up with a bunch of files that you didn't know existed, and you'll eat up valuable hard drive space on your server.

Naming files. Have you ever been to a larger web site, such as CNet.com or Enfused.com, and seen a filename in the address bar such as 10,31,95_0_0_1,2.html? Chances are, these pages are created using a content management system. The system names each page something unique that will never be confused with something else. Sometimes you may be able to get away using a simple name, such as review.html or intro.html. However, when you have many different articles to publish, you may find that you will run into naming problems. It may be a good idea to name your articles something unique, possibly something that depends on the current date/time. This will ensure your articles will never be overwritten if another article with the same name pops up.

Administration
Content Management Made Easy with ASP
Conclusion