generic-poky/documentation
Scott Rifenbark c576556033 yocto-project-qs, mega-manual: Conformed to YP book set
I discovered some artifacts and inconsistencies with how the YP
Quick Start was made.  I made the following changes:

1. Changed the structure of the QS from "article" to "book"
   as it is a separate book.  This change doesn't fix anything
   but it does bring the XML file closer to passing validation.

2. Removed the <abstract></abstract> tag.  This tag was in place
   simply to display the PNG file for the Yocto logo in the upper
   right part of the first page.  After turning the QS into a
   book from an article, the title could be displayed as a PNG
   file similar to the other books.  This change solved two issues:
   1) removed the empty "abstract" element from being displayed in
   both the mega-manual and the PDF version, and 2), brought the
   author and look of the first page into line with other YP
   manuals.

3. Removed the old PNG file used to display the Yocto logo at
   the top of the QS.  This file was removed from both the
   yocto-project-qs and mega-manual "figures" directories.

4. Added a new "yocto-project-qs-title.png" file to both the
   yocto-project-qs and mega-manual "figures" directories.

5. Updated the "qs-style.css" file's .authorgroup element to
   match and behave like the other YP manuals.  This effectively
   correctly displays the title PNG file for the QS.

6. Updated the Makefile area where the TAR files are made for
   both the yocto-project-qs and the mega-manual.  I had to
   substitute in the new PNG file for the QS one and had to
   add the title PNG to the mega-manual part.

(From yocto-docs rev: 914c482bd89071ab34b3381e3bd8065f871cc047)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-19 22:36:14 +00:00
..
adt-manual documentation: Updated the manual revision history tables. 2014-11-04 10:28:30 +00:00
bsp-guide bsp-guide: Fixed ambiguous sentence. 2014-12-09 15:09:06 +00:00
dev-manual dev-manual: Added link to ptest wiki page into Ptest section. 2014-12-09 15:09:06 +00:00
kernel-dev documentation: Updated the manual revision history tables. 2014-11-04 10:28:30 +00:00
mega-manual yocto-project-qs, mega-manual: Conformed to YP book set 2014-12-19 22:36:14 +00:00
profile-manual profile-manual: Updates to the LTTng Documentation section. 2014-11-08 11:15:12 +00:00
ref-manual ref-manual: Created form for context images for variables 2014-12-09 15:09:06 +00:00
template ref-manual, template: Permalinks for QA errors and warnings 2014-10-10 16:44:34 +01:00
tools mega-manual.sed: Updated to support the 1.8 release. 2014-11-04 10:28:30 +00:00
yocto-project-qs yocto-project-qs, mega-manual: Conformed to YP book set 2014-12-19 22:36:14 +00:00
Makefile yocto-project-qs, mega-manual: Conformed to YP book set 2014-12-19 22:36:14 +00:00
README README: Updated the file to reflect current state of documentation 2013-08-13 13:18:36 +01:00
poky.ent poky-ent: Updated variables to support the 1.8 release. 2014-11-04 10:27:13 +00:00

README

documentation
=============

This is the directory that contains the Yocto Project documentation.  The Yocto
Project source repositories at http://git.yoctoproject.org/cgit.cgi have two
instances of the "documentation" directory.  You should understand each of
these instances.

  poky/documentation - The directory within the poky Git repository containing
                       the set of Yocto Project manuals.  When you clone the
                       poky Git repository, the documentation directory
                       contains the manuals.  The state of the manuals in this
                       directory is guaranteed to reflect the latest Yocto
                       Project release.  The manuals at the tip of this
                       directory will also likely contain most manual
                       development changes.

  yocto-docs/documentation - The Git repository for the Yocto Project manuals.
                             This repository is where manual development
                             occurs.  If you plan on contributing back to the
                             Yocto Project documentation, you should set up
                             a local Git repository based on this upstream
                             repository as follows:

                               git clone git://git.yoctoproject.org/yocto-docs

                             Changes and patches are first pushed to the
                             yocto-docs Git repository.  Later, they make it
                             into the poky Git repository found at
                             git://git.yoctoproject.org/poky.

Manual Organization
===================

Folders exist for individual manuals as follows:

* adt-manual       - The Yocto Project Application Developer's Guide.
* bsp-guide        - The Yocto Project Board Support Package (BSP) Developer's Guide
* dev-manual       - The Yocto Project Development Manual
* kernel-dev       - The Yocto Project Linux Kernel Development Manual
* ref-manual       - The Yocto Project Reference Manual
* yocto-project-qs - The Yocto Project Quick Start
* mega-manual      - An aggregated manual comprised of all YP manuals and guides
* profile-manual   - The Yocto Project Profile and Tracing Manual

Each folder is self-contained regarding content and figures.  Note that there
is a sed file needed to process the links of the mega-manual.  The sed file
is located in the tools directory.  Also note that the figures folder in the
mega-manual directory contains duplicates of all the figures in the YP folders
directories for all YP manuals and guides.

If you want to find HTML versions of the Yocto Project manuals on the web,
go to http://www.yoctoproject.org and click on the "Documentation" tab.  From
there you have access to archived documentation from previous releases, current
documentation for the latest release, and "Docs in Progress" for the release
currently being developed.

In general, the Yocto Project site (http://www.yoctoproject.org) is a great
reference for both information and downloads.

Makefile
========

The Makefile processes manual directories to create HTML, PDF,
tarballs, etc.  Details on how the Makefile work are documented
inside the Makefile.  See that file for more information.

To build a manual, you run the make command and pass it the name
of the folder containing the manual's contents.
For example, the following command run from the documentation directory
creates an HTML and a PDF version of the ADT manual.
The DOC variable specifies the manual you are making:

     $ make DOC=adt-manual

poky.ent
========

This file defines variables used for documentation production.  The variables
are used to define release pathnames, URLs for the published manuals, etc.

template
========
Contains various templates, fonts, and some old PNG files.

tools
=====
Contains a tool to convert the DocBook files to PDF format.  This folder also
contains the mega-manual.sed file, which is used by Makefile to process
cross-references from within the manual that normally go to an external
manual.