| Greets All,
|
| BD said ---> The same way you would go about using CSS
| in any other page (unless there's a specific problem
| you're running into, and if that's the case, post back
| to the list and describe that problem).  ---
|
| I think there are two things I am concerned about.
|
| 1.) Where the css sheet goes.  I mean, if I make a
| folder just for templates, then does it go there or in
| the cgi-bin?  Or, if I just keep all my .tmpl files in
| the the cgi-bin, then would it just go there?

That really just depends on how you prefer to organize your files. Our setup
is probably a little more complicated than you'll need, but I'll describe it
just to give an idea of the kind of thing you *could* do. We have a
templates folder containing separate folders for each site that uses H::T.
Each one of those contains a folder for includes, which is where we put our
css files for that site (we might have a separate folder just for css files
if we used more than one or two per site, but mostly we don't). Our
preference is to separate the code from the templates, and it's probably a
good idea unless you have a really good reason not to, but you don't have
to, just make sure you tell H::T where it's supposed to look for your
templates, and it'll find them. (In that vein, you may want to check out the
excellent documentation regarding the HTML_TEMPLATE_ROOT environment
variable and the 'path' option to the new() method).

| 2.)  I thought that in the scripts it is common
| practice to have the header generated by the script,
| like this:
|
| print->$CGI->header();
|
| or,
|
| print "Content-Type: text/html\n\n";
|
| I would prefer to use the latter, however, I am not
| sure how either would necessarily affect the head
| tags, which is where the style sheet would go.  The
| latter print statement doesnt seem like it would
| include the head tags at all, and so it would seem I
| should just include the head tags in the template.  IS
| that right?

Yes, but that's only part of it. Both will actually work just fine; we use
them both in different contexts. The 'header' is not the 'head'. The header
just tells the server that you're about to send it some stuff, and it's
stuff of the 'text/html' sort (pardon the oversimplification). This
information doesn't go in your template. The <head> tag is part of the html,
and goes in your template.

| I had a similar questions about using meta tags in the
| templates too, so this answer may kill two birds with
| one stone.  But, again, I've heard some search engines
| wont reference CGI pages, but anyway...  that's going
| off topic a bit...

Meta tags can go in your templates, though for tags that are the same across
an entire site, you might find it easier to maintain the code by putting
them into an include, then just including that file into all your templates.

Kenny Smith posted an excellent solution involving mod_rewrite on 8/19 (this
year) to the problem of search engines ignoring CGI pages. If you can wrap
your head around that sort of voodoo, you'll be set, and you'll be able to
do all sorts of crazy things you never knew were possible. There are some
slightly less crazy workarounds, but the mod_rewrite solution is by far the
most solid, and coolest solution. (Thanks Kenny)

| Thanks for the help,
|
| Will
|
|

Have fun,

Brian McCain
PageMasters Internet Group



-------------------------------------------------------
This SF.NET email is sponsored by: AMD - Your access to the experts
on Hammer Technology! Open Source & Linux Developers, register now
for the AMD Developer Symposium. Code: EX8664
http://www.developwithamd.com/developerlab
_______________________________________________
Html-template-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/html-template-users

Reply via email to