Index: head/en_US.ISO8859-1/books/fdp-primer/book.xml
===================================================================
--- head/en_US.ISO8859-1/books/fdp-primer/book.xml (revision 54255)
+++ head/en_US.ISO8859-1/books/fdp-primer/book.xml (revision 54256)
@@ -1,278 +1,281 @@
%chapters;
]>
FreeBSD Documentation Project Primer for New
ContributorsThe FreeBSD Documentation Project19981999200020012002200320042005200620072008200920102011201220132014201520162017
+ 2018
+ 2019
+ 2020DocEng
&legalnotice;
Thank you for becoming a part of the FreeBSD Documentation
Project. Your contribution is extremely valuable, and we
appreciate it.This primer covers details needed
to start contributing to the FreeBSD Documentation
Project, or FDP, including tools, software,
and the philosophy behind the
Documentation Project.This is a work in progress. Corrections and
additions are always welcome.PrefaceShell PromptsThis table shows the default system prompt and
superuser prompt. The examples use these prompts to
indicate which type of user is running the example.UserPromptNormal user&prompt.user;root&prompt.root;Typographic ConventionsThis table describes the typographic conventions
used in this book.MeaningExamplesThe names of commands.Use ls -l to list all
files.The names of files.Edit .login.On-screen computer output.You have mail.What the user types, contrasted with on-screen
computer output.&prompt.user; date +"The time is %H:%M"
The time is 09:18Manual page references.Use &man.su.1; to change user identity.User and group names.Only root can do
this.Emphasis.The user must do
this.Text that the user is expected to replace with
the actual text.To search for a keyword in the manual pages, type
man -k
keywordEnvironment variables.$HOME is set to the user's home
directory.Notes, Tips, Important Information, Warnings, and
ExamplesNotes, warnings, and examples appear within the
text.Notes are represented like this, and contain information
to take note of, as it may affect what the user
does.Tips are represented like this, and contain information
helpful to the user, like showing an easier way to do
something.Important information is represented like this.
Typically, these show extra steps the user may need to
take.Warnings are represented like this, and contain
information warning about possible damage if the
instructions are not followed. This damage may be physical,
to the hardware or the user, or it may be non-physical, such
as the inadvertent deletion of important files.A Sample ExampleExamples are represented like this, and typically
contain examples showing a walkthrough, or
the results of a particular action.AcknowledgmentsMy thanks to Sue Blake, Patrick Durusau, Jon Hamilton,
Peter Flynn, and Christopher Maden, who took the time to read
early drafts of this document and offer many valuable comments
and criticisms.
&chap.overview;
&chap.tools;
&chap.working-copy;
&chap.structure;
&chap.doc-build;
&chap.the-website;
&chap.xml-primer;
&chap.xhtml-markup;
&chap.docbook-markup;
&chap.stylesheets;
&chap.translations;
&chap.po-translations;
&chap.manpages;
&chap.writing-style;
&chap.editor-config;
&chap.see-also;
&app.examples;
Index: head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml
===================================================================
--- head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml (revision 54255)
+++ head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml (revision 54256)
@@ -1,264 +1,273 @@
OverviewWelcome to the &os; Documentation Project
(FDP). Quality documentation is crucial
to the success of &os;, and we value your contributions very
highly.This document describes how the FDP is
organized, how to write and submit documentation, and how to
effectively use the available tools.Everyone is welcome to contribute to the
FDP. Willingness to contribute is the only
membership requirement.This primer shows how to:Identify which parts of &os; are maintained by the
FDP.Install the required documentation tools and files.Make changes to the documentation.Submit changes back for review and inclusion in the &os;
documentation.Quick StartSome preparatory steps must be taken before editing the &os;
documentation. First, subscribe to the &a.doc;. Some team
members also interact on the #bsddocs
IRC channel on
EFnet. These
people can help with questions or problems involving the
documentation.Install the
textproc/docproj meta-package
and Subversion.
This meta-package installs all of the software needed to
edit and build &os; documentation. The
Subversion package is needed to
obtain a working copy of the documentation and generate
patches with.&prompt.root; pkg install docproj subversion
+ Optional: to generate PDF documentation, install the
+ textproc/fop package as it is not
+ installed by default by textproc/docproj.
+
+
+ &prompt.root; pkg install fop
+
+
+ Install a local working copy of the documentation from
the &os; repository in
~/doc (see
).&prompt.user; svn checkout https://svn.FreeBSD.org/doc/head ~/docConfigure the text editor:Word wrap set to 70 characters.Tab stops set to 2.Replace each group of 8 leading spaces with a
single tab.Specific editor configurations are listed in
.Update the local working copy:&prompt.user; svn up ~/docEdit the documentation files that require changes. If a
file needs major changes, consult the mailing list for
input.References to tag and entity usage can be found in
and
.After editing, check for problems by running:&prompt.user; igor -R filename.xml | less -RSReview the output and edit the file to fix any problems
shown, then rerun the command to find any remaining
problems. Repeat until all of the errors are
resolved.Always build-test changes before
submitting them. Running make in the
top-level directory of the documentation being edited will
generate that documentation in split HTML format. For
example, to build the English version of the Handbook in
HTML, run make in the
en_US.ISO8859-1/books/handbook/
directory.When changes are complete and tested, generate a
diff file:&prompt.user; cd ~/doc
&prompt.user; svn diff > bsdinstall.diff.txtGive the diff file a descriptive name. In the example
above, changes have been made to the
bsdinstall portion of
the Handbook.Submit the diff file using the web-based Problem
Report system. If using the web form, enter a
Summary of [patch] short description
of problem. Select the
Component Documentation. In the
Description field, enter a short description of the changes
and any important details about them. Use the
[ Add an attachment ]
button to attach the diff file. Finally, use the
[ Submit Bug ] button to
submit your diff to the problem report system.The &os; Documentation SetThe FDP is responsible for four
categories of &os; documentation.Handbook: The Handbook is the
comprehensive online resource and reference for &os;
users.FAQ: The FAQ
uses a short question and answer format to address questions
that are frequently asked on the various mailing lists and
forums devoted to &os;. This format does not permit long
and comprehensive answers.Manual pages: The English language
system manual pages are usually not written by the
FDP, as they are part of the base system.
However, the FDP can reword parts of
existing manual pages to make them clearer or to correct
inaccuracies.Web site: This is the main &os;
presence on the web, visible at
https://www.FreeBSD.org/
and many mirrors around the world. The web site is
typically a new user's first exposure to &os;.Translation teams are responsible for translating the
Handbook and web site into different languages. Manual pages
are not translated at present.Documentation source for the &os; web site, Handbook, and
FAQ is available in the documentation
repository at
https://svn.FreeBSD.org/doc/.Source for manual pages is available in a separate
source repository located at
https://svn.FreeBSD.org/base/.Documentation commit messages are visible with
svn log. Commit messages are also
archived at
&a.svn-doc-all.url;.Web frontends to both of these repositories are available
at
and .Many people have written tutorials or how-to articles about
&os;. Some are stored as part of the FDP
files. In other cases, the author has decided to keep the
documentation separate. The FDP endeavors to
provide links to as much of this external documentation as
possible.