[documentation] the documentation site is too broken and lacks formatting and writing style

[puregin]

On 12-Jan-2006, at 10:12 PM, Charlie Lowe wrote:

>
> puregin wrote:
>>     Hence whether a heading on a page/screen
>> comes from an  embedded heading, or is a
>> structural title,  is of  interest only to authors/editors.
>>     If given content is not *presented* in a
>> way that is useful to the reader, that is another
>> matter, but again, it does not have to do with
>> how headings and structure are represented.
>
> I do understand what you are saying, and have understood this. The  
> main issue that needs to be addressed is how to represent the  
> visual headings within a handbook page. This is the point where the  
> conversation always stops. You are concerned about the structure of  
> the book. That's fine. But I am equally if not more concerned about  
> the structure of individual pages--how visual headings can be used  
> within a page. Here's an example:
>
> http://cyberdash.com/files/misc/heading-example.png
>
> In this page, I do not want to break this into multiple pages (for  
> the reasons mentioned about hyperlinks and wanting the reader to be  
> able to scan the text). The structure of the book is already  
> defined for this text. Headings here are used being used within an  
> individual page for structuring as visual cues that would not be  
> better served breaking it up into multiple pages.
>

     You are confusing pages (as seen on the screen) with nodes.