|Revision 0.07||2001-08-01||Revised by: aeg|
|Changed license to GFDL|
|Revision 0.06||2001-01-08||Revised by: gjf|
|Changed date format (YYYY-MM-DD)|
This is a fully working template for big HOWTOs. The source contains fully described slots to make a convenient framework for you to fill in for making your own HOWTO; suggesting some names, conventions and contents for the chapters.
SGML source for this document is available and should be consulted while reading.
For various reasons this brand new release is codenamed the release release.
New code names will appear as per industry standard guidelines to emphasize the state-of-the-art-ness of this document.
This document was written when I read a feedback asking for a template to fill in to make new HOWTOs. This template was initially made by extracting the skeletal structure of the Multi Disk HOWTO which is a rather large HOWTO. It then went through extensive editing.
Stating the background is a simple way to getting started writing the intro.
First of all we need a bit of legalese. Recent development shows it is quite important.
This document is Copyright © 2000 Stein Gjoen. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found in Appendix Appendix A. Replace with your name, or supply a new license, when you use this template for a new HOWTO.
If you have any questions, please contact <email@example.com>
No liability for the contents of this documents can be accepted. Use the concepts, examples and other content at your own risk. As this is a new edition of this document, there may be errors and inaccuracies, that may of course be damaging to your system. Proceed with caution, and although this is highly unlikely, the author(s) do not take any responsibility for that.
All copyrights are held by their by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark.
Naming of particular products or brands should not be seen as endorsements.
You are strongly recommended to take a backup of your system before major installation and backups at regular intervals.
This is where you make a summary of what is new. When a HOWTO exceeds 20 pages it takes more than a casual read to find the updates. This is where you help your readers with that, alerting them to specific and important updates to the document.
Tell people where the document home page is so the very newest release could be found in case of problems with the main Linux Documentation Project homepage.
The following is a sample from the Multi Disk HOWTO:
The latest version number of this document can be gleaned from my plan entry if you finger my Nyx account.
If you have the capability, it would be nice to make the HOWTO available in a number of formats.
The newest version of this HOWTO will always be made available on my website, in a variety of formats:
Note that paper sizes vary in the world, A4 and US letter differ significantly. You might also wish to consider using the universal format (8.27x11in; 210x279mm).
It is always nice to acknowledge people who help you with input; it is also regarded by many as important in the Linux world new economy.
In this version I have the pleasure of acknowledging:
Please scramble the addresses so email harvesters cannot get addresses from your HOWTO and then spam people. That has happened in the past.
Somecompany is acknowledged for sending me documentation on their gizmos as well as permission to quote from the material. These quotes have been approved before appearing here and will be clearly labeled.
Feedback is most certainly welcome for this document. Without your submissions and input, this document wouldn't exist. Please send your additions, comments and criticisms to the following email address : <firstname.lastname@example.org>.