I suggest to change "Welcome to Portage" to "emerge command, the key to Portage" I don't like this style: Documentation Resources ======================= The Great All-Unifying Documentation Folder =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= General gentoo-related documentation project = = = = = = = = = = = = = = = = = = = = = = = The Documentation ----------------- Greetings ......... Introduction . . . . . . 1.1.1.1.1.1.1 Welcome to the introduction, this is the documentation! We congratulate you that you were so brave to dig through all our meaningless titles headings, categories and paragraphs up to here. If you think you will be able to get any useful information from this website, then relax. No way, dude. We put meaningless titles, introductions and welcomes to all the places people look first. 1.1.1.1.1.1.2 About this documentation Anyway, this is the beginning of the documentation. In the first two chapters we will slowly accustome you to the fact that this is the documentation and the introduction is slowly beginning. After that we will repeat this to make sure you won't forget it. And then once more, for the individuals with weak heart of hypertension to make sure they don't get a heart attack or stroke from the sudden surprise when the actual informations comes. 1.1.1.1.1.1.3 The most important information (for us) is that this website is under CC licence (but not whole, so you actually don't get any useful information from reading this sentence). And - yes we forgot - we also wanted to tell you that the whole document is comprised of sentences, they are composed of words and the words of letters. Just for the case you didn't know. And look - the background is white! What a surprise. Did you expect a black one? 1.1.1.1.1.1.4 The second most important information is that we are proud of this website. We made it with pride and it was us who made it and not anyone else! "Welcome to the Portage" are just empty headlines wasting time and distracting the reader. Do you wonder why people don't bother reading the doc before they report a bug on the program which is actually their own problem? Because the doc is often a >>> SHIT! <<< To make a good doc (and not a shit) you have to constantly think about the purpose of the doc - to give information easily, quickly and relevantly to the user, and not to masturbate the writer's ego.
(In reply to comment #0) > Do you wonder why people don't bother reading the doc before they > report a bug on the program which is actually their own problem? Because the > doc > is often a > >>> SHIT! <<< > > To make a good doc (and not a shit) you have to constantly think about the > purpose of the doc - to give information easily, quickly and relevantly to the > user, and not to masturbate the writer's ego. > I suggest that insulting hard-working GDP people and filing useless bugs is a complete waste of time.
