Re: Best practice to re-write a tutorial website

On 23/07/2004, at 6:48 AM, EE wrote:

1. Printer Friendly Version Capability

This can be achieved with media specific style sheets stylesheets -- no need for separate templates.

2. Search-ability

For the most part, this can be achieved with MySQL's fulltext search capabilities. You just need to wrap it all in a search GUI and results page.

3. Search Engine Friendly

This relates back to #1. If you restrict your use of HTML to only semantic page elements (DIVs, H1-6s, Ps, etc), rather that filling it with presentational mark-up (FONT, TABLE, etc) your pages will be lighter, which will allow better indexing by search engines. This is a really quick overview of course, but standards-based web pages with all presentational stuff moved to a CSS file will help SE's index your content accurately, and it will be a pleasure to maintain. This seems to be a common stylesheet set-up: <link rel='stylesheet' media='all' href='css/basic.css' /> <link rel='stylesheet' media='print' href='css/print.css' /> <style type='text/css' media='screen'>@import url("css/advanced.css")</style> But we're getting WAY off topic here.

1. What is the best way to store the tutorials. Should they be in a database or each in a separate HTML file.

Either is fine, but searching will be easier in a database -- especially with MySQL's fulltext search built in. Search Google for specific help on any of the above, and you'll be set :) --- Justin French http://indent.com.au