to template or to use a skeleton file

[bj_]

I am going to have database driven articles on my website. I am trying to choose between having one generic file that can load any article from the article index or having a skeleton file for each article I have.

to illustrate:

// connect to database
// get articles from database
// $article = results by associative array.
// $article_name = $article['name'];
// $article_source = $article['source'];

// method one
// an example link
<a href="article.php?<?php echo $article_name;?>";>

// method two
// an example link
<a href="<?php echo $article_source;?>">

I want to do the second do the second method even though I would have only one place to edit changes. Other than that there doesn't seem like there is much of an advantage to doing the first method. Is there any other advantages doing one method over the other.

[Weedpacket]

Heh, do both 🙂. That is, use the second form for any and all links to your articles and then have your web server rewrite those URLs into the first form. Gives you the best of both worlds. A single generic file that needs maintaining, and nice URLs.

As well as nicer-looking URLs, it means you can later on change how things work behind the scenes and not have to go through changing all the URLs everywhere, just the rewriting rules.

[bj_]

I like what your saying and it sounds real good, but I don't get what you are syaing.
Do you mean I should template page be a redirect to the generic article script?