We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 32942
    • 141 Posts
    Basic Information everyone should know, but many don’t apply correctly.

    Before you start, you should know that the XHTML Standard defines that all tags and attributes have to be in lowercase.
    It’s the good old disscussion:
    "Strict" or "Transitional" or even XHTML 1.1?
    Activating the Right Layout Mode Using the Doctype Declaration.


    To give you a good start, please read following:
    http://24ways.org/advent/transitional-vs-strict-markup
    http://www.zvon.org/xxl/xhtmlReference/Output/comparison.html
    http://hsivonen.iki.fi/doctype/
    http://www.hixie.ch/advocacy/xhtml very dry, but informative

    A recommendable approach, which may need adjustments to fit your local recommendations, is the following:

    Write a descriptive heading for the entire document and use H1 element with ALIGN=CENTER* attribute for it.
    Divide the document into major parts (sections), write suitable titles for them, using H1 with ALIGN=LEFT*. In this and further divisions, try to avoid having more than seven parts.
    If necessary, divide each major part into smaller parts with H2 headings, and if needed divide each of these subsections into subsubsections with H3 headings. Avoid using H4 headings and especially H5 and H6 headings, both because they are often rendered with a very small font and because more than three levels of structure tends to make the document hard to read. (If you still feel tempted to use H4, consider dividing the entire document into smaller documents.)
    If you have a section with, say, H2 heading and containing H3 headings, avoid inserting text between the H2 heading and the first H3 heading. Such "homeless" text can be acceptable if it only contains very short notes such as general orientation, some remarks about the section, or a motto. Long homeless texts confuse the reader who does not see your good intentions; therefore, use a subsection with a heading of the appropriate level and with text like Introductory remarks, Generalities or Summary.
    Divide the smallest parts of the above-mentioned structure into paragraphs or paragraph-like blocks (namely lists or tables). as described below. Notice that in HTML you must explicitly indicate paragraph division by HTML elements; leaving just an empty line does not cause a paragraph break.
    Within paragraphs, use text level markup, normally phrase markup, to distinguish special text segments from normal text, e.g. to indicate quotations of computer output or to emphasize key words.
    Add links and, if applicable, images or other illustrations.
    As regards to the paragraph level, there are quite a few alternatives. The following list is intended to give some practical guidelines for selecting a suitable alternative:
    For normal text paragraphs, use the P element.
    However, if the text of the entire paragraph is literally quoted from some source, use the BLOCKQUOTE element or, if it is program code, computer output or some other text that shall be presented exactly honoring the division into lines, use the PRE element. In the latter case, if monospaced font is not suitable (e.g. the text is a poem), use BLOCKQUOTE and append a BR element to each line.
    As a special case, if the paragraph is intended for providing information about the author (that’s you), use the ADDRESS element.
    For itemized information, which logically consists of separate cases or items, use various elements as follows:
    For list of items where the order is not significant, such as a list of ingredients in a recipe, use the UL element, or the MENU element (for a list of rather small items), or the DIR element (for a large list of small items, suitable for presentation in multi-column format). However, since most browsers do not present MENU and DIR in the manner suggested in the specifications but as identical to UL, you may wish to consider other possibilities as well, such as using tables to represent menus. - Notice that e.g. in an alphabetical list the order is usually not significant in the relevant sense; if the order is so explicit, there is hardly any need to make it more explicit e.g. by using numbering.
    For list of items where the order is significant and this significance needs to be made explicit, such as a sequence of instructions to be obeyed in that particular order, use the OL element.
    For a list of items with short titles or tags, such as a list of definitions for terms or abbreviations, use the DL element. However, you may like to consider using a TABLE element to present a definition list as an alternative.
    Notice that in a typical implementation MENU and DIR elements are rendered similar to UL elements. Moreover, DL element rendering can be awkward, too. Please browse a separate file Examples of various list elements in HTML to see what renderings of lists look like in your implementation. - The UL, MENU, DIR, OL, and DL elements are "plain lists" with no such structural feature as the CAPTION in a TABLE element. It is usually desirable to have some sort of heading or explanation before the list, but from the HTML viewpoint it is a separate paragraph.
    For tabular information, normally use the TABLE element, but consider the possibilities provided by PRE and DL elements, which may be suitable in special cases.
    List can be nested in the sense that an item in a list, i.e. an LI (or DD) element, may in turn contain a list element.

    Notice that the basic paragraph element P is not nestable, i.e. you cannot have P elements within a P element to create subparagraphs. However, the various list elements effectively provide an itemization structure which essentially corresponds to subparagraph division. Moreover, the list elements are nestable.

    * (better use css for this)
      • 28373
      • 204 Posts
      Quote from: Xsss4hell at Mar 24, 2007, 03:39 PM

      @Starbuck
      I mentioned that.
      Real-life shows us, that most web-devs don’t respect browsers lower than <5.5. You decide.

      Real life stats show very few people using <=5.5 - and there’s plenty of sites out there that don’t render correctly in older browsers. But it’s hardly an issue for people to lose any sleep over, that horse bolted a long time ago. And I don’t think it’s a matter of respect in most cases, I’m sure failing browser tests isn’t a grade professional web developers want on their report card. Plus, there are many design scenario’s that require a great deal of time and skill to code to render correctly in ’just’ modern browsers. And sometimes client’s budgets don’t stretch far enough to reach absolutely every visitor to a site. Sometimes client’s issue directive’s for a site to work on all modern browsers so they can take advantage of all the latest bell’s & whistles. They believe the web evolves so quick, any rendering issues in older browsers gets remedied, to a greater extent, over a narrow passage of time. And sometimes a developer can end up with code soup trying to fix things that aren’t worth the effort, or, distracted by theory over practicality resulting in projects exceeding an agreed budget.

      But ... there may be a handful who don’t respect older browsers, and without any particular browser in mind - justifiably so.

      Quote from: Xsss4hell at Mar 24, 2007, 03:39 PM

      I’d like to see a statistic which shows ie. blindreader users and "normal" users.

      Perhaps you could pull those from one of your own sites, I’d love to see them too.

      Quote from: Xsss4hell at Mar 24, 2007, 03:39 PM

      I’m actually (still) coding a site that redefines a html template.

      Why not produce original code?

      Quote from: Xsss4hell at Mar 24, 2007, 03:39 PM

      But friendly web-devs code crossbrowser friendly, no matter which browser and version is used.

      Again I don’t think it’s a matter of being "friendly", if developers had unlimited budgets, or too much time on their hands, then quite possibly a site they produce works in every single browser, and on every single platform. And I’ve perhaps seen a handful of simple ugly sites that can lay claim to that. Simple/ugly, isn’t a great selling point these days. Besides, if it’s tableless, and marked up correctly, developers can add a simple script to display the site as text only, like - styles off in Firefox that works in every browser. Something like this

      Head code

      <link rel="stylesheet" href="style.css" type="text/css" media="screen" title="modernbrowsers" />
      <link rel="alternate stylesheet" href="redundantbrowsers.css" type="text/css" title="redundantbrowsers" /> 
      
      <script type="text/javascript">
      var Stil = "modernbrowsers";
      function switchStyle(s) {
      if (!document.getElementsByTagName) return;
      var el = document.getElementsByTagName("link");
      for (var i = 0; i < el.length; i++ ) {
      if (el[i].getAttribute("rel").indexOf("style")!= -1 && el[i].getAttribute("title")) {
      el[i].disabled = true;
      if (el[i].getAttribute("title") == s) el[i].disabled = false;
      }}}
      function setStyle(s) {
      if (s!= Stil) {
      switchStyle(s);
      Stil = s;
      }} 
      </script>
      


      Body code
      <div id="styleoff"><a href="javascript:setStyle('redundantbrowsers')">Text View</a></div>
      


      Quote from: Xsss4hell at Mar 24, 2007, 03:39 PM

      Divide the document into major parts (sections), write suitable titles for them, using H1 with ALIGN=LEFT

      Why left? and do you mean

      h1 {
      text-align: left;
      }

      And how about

      h1 span {
      display: none;
      }

      
      <h1><span>It doesn't really matter where I'm put, or how I'm aligned, spiders can still see me</span></h1>
      


      Your posts are pretty big, I’ll get to the rest later. Just out of curiosity, is the content in your posts original and drawn from your own experience ?
        • 32942
        • 141 Posts
        The content of my posts is original and based on my experience.
        Only the last post "Reply #10" is a mashup of information I found in the net that is very useful for beginners (sry I don’t remember the sources).

        @Starbuck
        Xsss4hell: I’m actually (still) coding a site that redefines a html template.
        Starbuck: Why not produce original code?
        What do you mean, with original code?

        The reason why I want to see a blindreader and other "unknown clientsoftware" user is, that my statistics don’t show them.

        Stats from 1th January 2007 till now:
        1 Internet Explorer 6.0    31.39%
        2 Firefox 2.0    5.11%
        3 Firefox 1.5    4.76%
        4 Internet Explorer 7.0    4.41%
        5 Mozilla 5  2.29%
        6 Internet Explorer 5.0    1.23%
        7 Safari    1.06%
        8 Internet Explorer 5.5    0.71%
        9 Firefox 1.0    0.53%
        10 Opera 9.0    0.35%
        11 Mozilla    0.18%
        12 Netscape    0.18%

        1th January - 31th December 2006 Stats:
        1 Internet Explorer 6.0    42.63%
        2 Firefox 1.5    7.43%
        3 Internet Explorer 7.0    2.11%
        4 Opera 9.0    2.11%
        5 Firefox 1.0    1.29%
        6 Safari    0.94%
        7 Internet Explorer 5.0    0.82%
        8 Firefox 2.0    0.64%
        9 Internet Explorer 5.5    0.58%
        10 Opera 8.5    0.53%
        11 Mozilla    0.47%
        12 Mozilla 5    0.47%
        13 Konqueror 3.4    0.23%
        14 Konqueror 3.3    0.12%
        15 Netscape    0.12%
        16 Internet Explorer 5.2    0.06%
        17 Java 1.4    0.06%

        Stats excluding massive Robot visits.
        You can see that more users have IE7 and Mozilla 2 now, but IE6 is dominating them all the time.

        Here is an external market statistic from:
        http://marketshare.hitslink.com/report.aspx?qprid=0&qptimeframe=M&qpsp=97&qpmr=15&qpdt=1&qpct=6

        For Blog Coders:
        Comment-Showcase
        I like the mad4milk.net comment styling most.
          • 1379
          • 22 Posts
          hey man this is a really nice tool but the thing is this is not for free. i have used the trial version and i think it is great. thanks for the nice tol. really it is very difficult for web designer to know how his website will look at all browsers and reso. so this is wise tool for them. incluiding me
            Regards
            Amitav Roy
            Web Designer
            Website: http://www.pixelgroups.com
            Portal: http://www.creativeporta.com
            • 32942
            • 141 Posts
            sorry I need to learn, howto use short sentences and posts.


            Starbuck brought me to an idea. Something that webdevs would benefit from.
            Oh yes, commercially and in bussiness it is not acceppted to spent so much time for one layout.
            But aren’t we free (at least in the internet) and doing this for sake of perfecionism only, isn’t it fun?


            Many failed with the attempt to find the "holy-grail" of css based layouts.
            But we learned from the past, we’re experienced now.
            So, why not create an other attempt to find "THE LAYOUT"??
            I know there are alot of other multicolumn layouts and free ones, but none is flexible enough to suit everybodys needs. Right?
            What we need is something that defines our experience into one smart layout. But our layout ain’t smart, what can we do?
            A long time ago, I remember when I first saw divs.
            I thought they were made for layout, but my teacher got angry and told me to use tables instead..hmm I did (in the past the teacher was always right, yes? hehe times change).
            Oh boi, things have changed and the web is not the same as it was years ago, good so!

            Before we start we should not do the same fault as the 1.gen webdevs:
            They used the easiest way but encountered problems years later, when blinds could "see" webpages...

            NOW, have in mind the we’ve the power of MODx!
            We’re really able to create a smart layout now.


            I think you know what our requierements for a layout are.
            It must be HYBRID and SMART, be EASY to manage and BEATY to see.
            That’s all a layout must be.

            So we want to keep every option enabled for our endusers, but make it look easy and straight.
            It must be fast and reliable, even if one technique fails (->Fallbacks). Validity is just another check which our layout gonna pass easily.
            SMART management means, that ressource hungry "modules" are replaced and our better alternatives are only used if neccessary (->AJAX).
            We need techniques that replace other (old or ugly) techniques if supported.
            If supported means, we’re giving proggressively design enhancements for using better (newer) browsers (Something like giving you a cake, if you are a good boy;-)).

            Think of different user scenarios, this is one reason why you do not use any template but a solution fitting your needs.

            As you see this gonna be complex to develop for us only, but very very easy to use and deploy for you.
            Meaning we need good: creatives/developers/designers and community helping to make this real.

            The question is: Do you want one Template similar to CSS ZenGarden, but exclusively for MODx?
            Something that makes others jealous at us. And that means having a "magically cool" and totally customizable standard layout.
            Too bad I can’t embed votes.

            BUT VOTE YES FOR A SMART MODX COMMUNITY LAYOUT!
            OR VOTE NO, WE HAVE NO TIME OR SOMETHING LIKE THAT!

            how about a name?
            what do you think of: SCT - Smart Community Template.. It’s your turn.
              • 22303 MODX Staff
              • 10,725 Posts
              Quote from: Xsss4hell at Apr 03, 2007, 03:59 PM

              Many failed with the attempt to find the "holy-grail" of css based layouts.
              ...
              So, why not create an other attempt to find "THE LAYOUT"??
              I know there are alot of other multicolumn layouts and free ones, but none is flexible enough to suit everybodys needs. Right?
              What we need is something that defines our experience into one smart layout. But our layout ain’t smart, what can we do?
              ...
              BUT VOTE YES FOR A SMART MODX COMMUNITY LAYOUT!
              OR VOTE NO, WE HAVE NO TIME OR SOMETHING LIKE THAT!

              MAN IN CASTLE: "Well, I’ll ask him but I don’t think he’ll be very keen. You see we already have one."
              KING ARTHUR: "What?"
              SIR GALAHAD: He says they’ve already got one.
              They are stunned
              ARTHUR: Are you sure he’s got one?
              MAN (to ARTHUR): Oh yes. It’s very nice.
              MAN (turns to others in the CASTLE): I told them we already got one.
              They all giggle.
                • 28373
                • 204 Posts
                We’re getting this new blog skin for release ... "STOP PRESS" ... it doesn’t work in NN1

                http://www.modxhost.com/index.php?q=24.html

                But, it is RRI (reasonably resolution independent) and WOMMB (works on most modern browsers, so far *lol*)

                Tableless dioramic css web design, home brewed for modXcms smiley
                  • 32942
                  • 141 Posts
                  ^^« MODx Parse Error »