[geeklog-cvs] Geeklog-1.x/public_html/docs config.html,1.85,1.86

[Dirk Haun]

Update of /cvsroot/geeklog/Geeklog-1.x/public_html/docs
In directory qs1489.pair.com:/tmp/cvs-serv89958/public_html/docs

Modified Files:
	config.html 
Log Message:
Regrouped options to be in sync with the Configuration admin panel


Index: config.html
===================================================================
RCS file: /cvsroot/geeklog/Geeklog-1.x/public_html/docs/config.html,v
retrieving revision 1.85
retrieving revision 1.86
diff -C2 -d -r1.85 -r1.86
*** config.html	2 May 2008 19:30:11 -0000	1.85
--- config.html	3 May 2008 08:36:09 -0000	1.86
***************
*** 20,163 ****
  
  <p>For technical reasons, some configuration options still have to be
! stored in files. There are two such configuration files now, called
! <tt>db-config.php</tt> and <tt>siteconfig.php</tt>. These files are updated
  when you install Geeklog and you will not normally have to edit them
  manually.</p>
  
! <h2>Configuration options</h2>
  
! <p>Geeklog's configuration options can be grouped like this:</p>
[...2269 lines suppressed...]
+ 
+ <h2><a name="url-rewrite">URL Rewriting</a></h2>
+ 
+ <p>Geeklog includes a simple but useful URL rewriting feature which can help
+ make your site more crawler friendly (i.e. the URLs of your site are more
+ likely to be picked up by the search engine's indexing bots). This feature is
+ supported for URLs to stories, static pages, the article directory, and links.
+ </p>
+ <p>URL rewriting means that your URLs will look like this</p>
+ <p align="center"><tt>http://www.geeklog.net/article.php/20021022234959146</tt></p>
+ <p>instead of like this</p>
+ <p align="center"><tt>http://www.geeklog.net/article.php?story=20021022234959146</tt></p>
+ <p>While some search engines will pick up the second form, Google seems to
+ prefer the first format and often ignores the second format.</p>
+ <p><strong>Note:</strong> This feature may not work with all web servers. It
+ is known to work with Apache (all versions) and known <em>not</em> to work
+ with IIS (at least some versions). Please try it out before you go public
+ with your site.</p>