Contrarian that I (sometimes) am, I like the static page scheme (option 3) given the comparatively small number of possible combinations of data and relative rarity of changes you expect in the db.
Your 3rd option can do more for you than provide user and SE friendly URLs. If you generate the thousand or fewer pages on a local machine, you can readily (with a bit of a big workload up front) tweak the DESCRIPTION and KEYWORDS metas, which may do more for your search engine ranking that many other optomizing techniques.
On the other hand, there are so many parameters that go into SE ranking ("How fresh is the 'Latest Update' or 'Last modified' date? How well do the keywords match the actual content? etc.) so this suggestion may be an example of something comparable to "premature optomization."
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
