>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #337079. --> Reported by: [HansBKK](https://www.drupal.org/user/149289) >>> <p>The IRC meeting just wrapped, summary to be posted to g.d.o. by addi soon.</p> <p>I feel like a salmon swimming upstream on this, but I feel the need to try one more pitch.</p> <p>Regarding the creation of a D6-specific Getting Started guide - <strong>please</strong> don't.</p> <p>From the official <a href="https://www.drupal.org/documentation-writers-guide">Doc writer's guide</a> (currently under review):</p> <blockquote><p> Versions: There is only one set of documentation handbooks, since many pages apply to all versions of Drupal; since there are insufficient resources to maintain different sets of handbooks for different versions of Drupal; since inconsistencies would develop between parallel versions due to only one book being corrected when the problem affects both; and since guidance on the only available version is often useful to the reader who has a different version.<br> Information for different Drupal versions can be kept together on one page or separated on different pages. It is generally preferred to cover information for all the versions on a single page, but if instructions for the different Drupal versions differ substantially, separate pages are appropriate. Use the "Drupal version" drop-down menu and select which version(s) the page applies to.</p> <p>If each version is dealt with on a separate page:</p> <p> * Organize the pages on the same hierarchical level.<br> * Include the version number at the end of the title, so that one page is titled "Example topic, v. 5.x" and the next is "Example topic, v. 4.7." </p> <p>If multiple versions are dealt with on one page:</p> <p> * Select all the versions which the page applies to in the "Drupal version" drop-down menu.<br> * Information on the page should be listed from newest to oldest version.<br> * Mark the sub-sections for each version very clearly.<br> * If there are no separate subsections for the different versions because the entire page applies to all versions selected in the "Drupal version" drop-down menu, state so early in the page, so that readers don't wonder which sub-sections apply to their version. </p></blockquote> <p>----------------</p> <p>Addi's reasoning for forking the GS guide was that it's quicker and easier (it's needed now) and that the HTML shouldnt' get out of sync with the PDF.</p> <p>My case:</p> <p>I don't see how doing it this way: </p><ul> <li>bulk copy D5 GS to a new D6 GS</li> <li>-start editing new D6 GS</li> </ul> <p>is any quicker than this way:</p> <ul> <li>rename D5 GS to Drupal GS</li> <li>start editing new Drupal GS</li> <ul> <li>Stuff that applies to both D5 and D6 (IMO most of it) stays in<br> pages along the "main spine"</li> <li>Stuff that only applies to D5 gets moved to sub-pages labeled "for D5"</li> <li>New sub-pages get created and marked "for D6"</li> </ul> </ul> <p>And I think the PDF should just be an output medium for the master content on d.o.</p> <p>IMO the advantages of having one non-version-specific GS doc greatly outweigh the little bit of complexity added.</p> <p>Advantage of not forking the doc - further edits, improvements and<br> re-organizations benefit users of both versions.</p> <p>Disadvantage of forking - edits improvements and re-organizations in<br> one book should be reflected in both books separately, but as this<br> doubles the work it doesn't happen. Information that may be useful to<br> users of version X only shows up in the other version's book.</p> <p>If we go ahead with this, can we please make it the <strong>only </strong> handbook exception?</p> <p>Or change the guidelines for doc writers (-1000 from me)</p> <p>Obviously this whole issue stems from the fact that we're using Book, which only allows a node to have one parent in a single navigation hierarchy.</p> <p>If at some point we have automated filter-the-view-by-version or something similar to the automatically-generated API docs, that will fix the problem in a much better way.</p> <p>/end rantish soapbox</p>