Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

TOC is a good idea on this one; since I wrote the original, I edit, 7 Nov 17 will try to free up time, soonest, to add one. offer TOC draft sample for comment and review.

FOR COMMENT: seems like a TOC with both a few keywords for each topic AND the markup needed would be appropriate... but a big PITA.

Update, 7 Nov 17 It was! The PITA is finding an appropriate, very brief description for the various parts of the TOC (and, in this case, deciding which elements of the main text to include to best serve users!

FWIW: Others have written technical approaches, using clever code to identify elements that may need to be included in a TOC. I went "manual" to deal with the issue I perceive (at least in the case of Markup in the Monastery; namely, that the so-called "Chapter...." headings are not, themselves, informative for someone seeking (for example) to know how to create a list. Also, when I created "Markup" originally, the various <Hn> tags were for formatting only, without due regard to nesting (I don't know of any commonly-used browser, even today, that cares) or syntactical relevance. Call me a dinosaur, but I still don't worry about that: even today, itelligibility of content trumps sytactical correctness.

Quis custodiet ipsos custodes. Juvenal, Satires


In reply to Re: TOCs and deeplinks for our house rules by ww
in thread TOCs and deeplinks for our house rules by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others avoiding work at the Monastery: (None)
    As of 2024-04-25 04:00 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      No recent polls found