Re: multiple instances of a CSS link due to server-side file inclusion and tools requirements

Hello:

Thanks for your response to my post:

in article 15049b6f-094b-4a3a-bbe4-4d2011503415@xxxxxxxxxxxxxxxxxxxxxxxxxxx,
mikael b at micke.bystrom@xxxxxxxxx wrote on 11/22/08 3:51 AM:

On Nov 18, 6:03 am, henry <henry.zzzab...@xxxxxxxxx> wrote:


Question 1: What's the best way of describing this design, in which the
index page determines the basic site appearance, and specific "inner"
content is selected by a computation at load time? (Sorry, I'm self-taught
and working alone, and I don't always get the terminology right.)

Note that linkage to the site-wide CSS file occurs in all files. Why? At
least in the authoring environment I'm using, Dreamweaver CS3, that's the
only way to make the site-wide styles available to all pages.


Please: I've heard "Don't use DreamWeaver!" too many times already, so
there is no need to repeat it.
Why wouldn't one use Dreamweaver? That's not a reason to work AGAINST
wweb standards.

I agree.


Wen index.php is loaded, one of the chunks will be included and client will
see two, (repeat, 2) identical css link tags. When I test the page,
Obviously, us PHP includes instead, or server side includes, for code
fragments.

Sorry, my point wasn't clear. My site design _is_ based on using PHP
includes.

Question 4: Am I missing something completely obvious that would achieve
the same result without all this trouble? Again, I'm self-taught and I
could be completely oblivious to better ways to do this.
Include just the code you need in fragments, Why one would include
comeplete HTML files is totally beyond me. There is NO reason for this
in Dreamweaver, or anywhere.

Ummm, I have a very weak excuse for attempting this.

But first, a review: I got started down that road because I was renovating
an existing site, in which all the content chunks _were_ complete HTML
files. I naively hoped that I could rebuild the site to use a PHP include
scheme while making minimal changes to the actual content.

That's the history, now here's the weak excuse: That attempt appeared to
work quite well. In admittedly limited testing, I never saw any bad effect
from multiple CSS links, or nested outer tags, either. The only trouble I
actually saw that was attributable to this scheme was that the pages failed
W3C validation.



Question 5: Is there a better place to post this question?
Well, a dreamweaver forum obviously. But I can tell you right now,
that using DW is no excuse to write standard-erroneus code. Work with
the standards in mind and use DW as the tool it is. Use your brain
instead of leaving everything to DW.

You could also look into the use of DW templates, but I think PHP
includes is also worth investigating.

I have looked into DW templates. I didn't find them very friendly. As I've
said, I _am_ using a PHP includes.


I can recommend you get the book "Mastering.CSS with Dreamweaver CS3"
by Stephanie Sullivan and Greg Rewis <http://www.amazon.com/Mastering-
Dreamweaver-Voices-That-Matter/dp/0321508971/ref=sr_1_1?
ie=UTF8&s=books&qid=1227354193&sr=1-1>, for one source of solid ideas
on how to work WITH web standard oriented designs in Dreamweaver.

Thanks for the recommendation, but I have learned I learn best by doing,
even if that means making large, embarrassing mistakes.

Besides that, most books I've tired quickly lost in the details of such
technologies, of which there are plenty. They generally don't help with the
big picture. When I first thought up the scheme, I really did look around
the Web quite a bit for guidance. I found a lot of pre-built templates,
free and for sale, but nothing that described the pros and cons of such a
design. Nor did I find anything specific about multiple instances of a CSS
link that would logically occur. Perhaps if I had tried one more search
term variation I would have found what I was looking for. Typical.

DW
is a powerful tool, but that power can be misused, mispent or used to
your advantage. The choice is yours.

I didn't set out to be a rule-breaker! I don't believe DW led me in one
direction or another in this respect.

Thanks,

Henry

.

Relevant Pages

  • Re: multiple instances of a CSS link due to server-side file inclusion and tools requirements
    ... What's the best way of describing this design, ... I've heard "Don't use DreamWeaver!" ... the standards in mind and use DW as the tool it is. ... is a powerful tool, but that power can be misused, mispent or used to ...
    (comp.infosystems.www.authoring.html)
  • Re: PHP Webbuilding
    ... But more in a Dreamweaver ... set it up also in design, ... > Just install Apache, PHP, and, if needed, a database server on ...
    (alt.php)
  • Re: multiple instances of a CSS link due to server-side file inclusion and tools requirements
    ... Why not use Dreamweaver? ... That's a characteristic of all "high-level" design ... be HTML fragments *not* complete HTML document. ...
    (comp.infosystems.www.authoring.html)
  • Re: word webpages
    ... Now I have to admit if I didn't have to maintain a website for an Association; I don't whether I would own DreamWeaver as it may be too expensive and complex for simple web pages. ... Dreamweaver can, and will, convert the Rich Text into decent HTML, without ... The design goal was to express a Word document in language a browser can ...
    (microsoft.public.mac.office.word)
  • Re: PHP as a secure language? PHP worms? [was: Re: new linux malware]
    ... supported applications than, say, the Windows community, if PHP were ... Linux community has less patience for design flaws that PHP's success ... driving PHP development, they are not the same community. ... to recognize that the overwhelming majority of security issues raised ...
    (Bugtraq)
Loading