in reply to Web forum markup language and the Monastery

What have you learned (regarding the markup) from the past 5 years here ?

That tables sucks for design, because they make the entire page wider if only one node is wide. And that demerphq doesn't like users to use structured HTML with h1 and h2, but wants them to start with h4 instead, because PM itself uses h3 for the title. (I disagree and think PM should be fixed, because that can be done much more easily (with CSS, for example).)

Is the list of approved HTML tags the Monks have a good list ? Are there HTML tags that would make life easier ?

It's good now. Although some complain that images cannot be used, I think this is a good thing. Images are slow and, for Win32 users with MSIE, dangerous :)

How do you like the system of the shortcuts ?

I like it a lot, but I still don't understand why // is needed. [id:422484] instead of [id://422484] would be nice. The double slash has a specific meaning according to RFC 1738, and PM breaks this. // is a promise that //<user>:<password>@<host>:<port>/<url-path> (the common internet scheme syntax) can be used.

Would it make more sense to disallow the submission of bad markup or that of not approved HTML tags ?

Yes and no. I don't think this is a big deal. It would be nice if a simple HTML parser were used to close open tags, or to avoid tags being closed without ever having been opened.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

Replies are listed 'Best First'.
Re^2: Web forum markup language and the Monastery
by demerphq (Chancellor) on Jan 15, 2005 at 12:13 UTC

    And that demerphq doesn't like users to use structured HTML with h1 and h2, but wants them to start with h4 instead, because PM itself uses h3 for the title. (I disagree and think PM should be fixed, because that can be done much more easily (with CSS, for example).)

    Well, i agree with your diagreement, but until it is changed I do have more or less that opinion. OTOH since I've only ever considered a node about it once (which was yours) and that the community didn't agree with me when I did, I pretty much recognize that moaning about it is a lost cause. :-) (And by inference im not really sure why you brought it up, my opinion in things like this is no more relevent that anyone elses.)

    ---
    demerphq

[reply]

      im not really sure why you brought it up

      To answer the question. I had always learned that h1, h2, etc were for structuring, but your POV appears to be that the number in there is to indicate the size of the heading. This demonstrates that even something with a spec, like HTML, is open to multiple interpretations. For the OP, it is a hint to define these things, or at least think of a way to handle them.

      I pretty much recognize that moaning about it is a lost cause. :-)

      I am not convinced that it is. If you feel this is important, we should still seek a way to fix it. Either through CSS (just define font-size in the right contexts) or by disallowing the "big" (or, from my point of view: higher level) headings. There was no clear concensus on the consideration, but there were in fact more people who voted edit than who voted keep, and this proves that you're not the only one who dislikes the current state of things.

      About the headings being too big: I agree, even.

      Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

[reply]

        I think its more a question of how you view nodes in context. I tend to stay away from H1 in nodes because normally people view the nodes in context of a section or thread. This means that the node you post is actually a subnode of a preexisting structure. I find it annoying to have a section like Perlmonks Discussion have an H1 and then inside nodes that are displayed also have H1 tags. Had you posted your doc to tutorials in that format I wouldn't have minded as in that case your node would truely be top level and thus the section breakouts you were using wouldnt conflict with the page layout as a whole.

        Update:Oh, also in the situation of your node, iirc it was front paged, which is a section of many sections so the headings you chose "broke" the way the nodes of different sections were deliniated. Im really not sure how to address this situation properly. Im not really sure its worth that much effort to do so either as such nodes are only a temporary irritation as people seem to avoid H tags generally and thus push those posts that do off of the section list eventually.

        ---
        demerphq

[reply]

In Section Meditations