diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..68c771a
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,176 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
diff --git a/README.md b/README.md
index 00844e3..1ce278c 100644
--- a/README.md
+++ b/README.md
@@ -1,2 +1,14 @@
-# master_template
-This repository is for the development and maintenance of the Docbook common files and template used for OPF Workgroup documents
+# Master Template Document Project for OpenPOWER Foundation Documentation
+This repository hold the source for the master document template for
+OpenPOWER Foundation. The PDF and HTML generated from the doc/template/
+directory build a document that both describes how to build a new
+document and contains examples and directions on how to do it.
+
+The online version of the document can be found in the OpenPOWER Foundation
+Document library at [TBD](http://openpowerfoundation.org/docs)
+
+The project which control the look and feel of the document is the
+[Docs-Maven-Plugin project](https://github.com/OpenPOWERFoundation/Docs-Maven-Plugin).
+
+To contribute to the OpenPOWER Foundation template document project, contact Jeff Scheel \([scheel@us.ibm.com](mailto://scheel@us.ibm.com)\) or
+Jeff Brown \([jeffdb@us.ibm.com](mailto://jeffdb@us.ibm.com)\).
diff --git a/doc/common/app_foundation.xml b/doc/common/app_foundation.xml
new file mode 100644
index 0000000..149283b
--- /dev/null
+++ b/doc/common/app_foundation.xml
@@ -0,0 +1,136 @@
+
+
+
+ OpenPOWER Foundation overview
+
+ The OpenPOWER Foundation was founded in 2013 as an open technical membership organization
+ that will enable data centers to rethink their approach to technology. Member companies
+ are enabled to customize POWER CPU processors and system platforms for optimization and
+ innovation for their business needs. These innovations include custom systems for large
+ or warehouse scale data centers, workload acceleration through GPU, FPGA or advanced I/O,
+ platform optimization for SW appliances, or advanced hardware technology exploitation.
+ OpenPOWER members are actively pursing all of these innovations and more and welcome
+ all parties to join in moving the state of the art of OpenPOWER systems design forward.
+
+
+ To learn more about the OpenPOWER Foundation, visit the organization website at
+ openpowerfoundation.org.
+
+
+
+ Foundation documentation
+ Key foundation documents include:
+
+
+
+
+ Bylaws of OpenPOWER Foundation
+
+
+
+
+
+ OpenPOWER Foundation Intellectual Property Rights (IPR) Policy
+
+
+
+
+
+ OpenPOWER Foundation Membership Agreement
+
+
+
+
+
+ OpenPOWER Anti-Trust Guidelines (link TBD)
+
+
+
+
+ More information about the foundation governance can be found at
+ openpowerfoundation.org/about-us/governance.
+
+
+
+
+ Technical resources
+ Development resouces fall into the following general categories:
+
+
+
+
+ Foundation work groups
+
+
+
+
+ Remote development environments (VMs)
+
+
+
+
+ Development systems
+
+
+
+
+ Technical specifications
+
+
+
+
+ Software
+
+
+
+
+ Developer tools
+
+
+
+ The complete list of technical resources are maintained on the foundation
+ Technical Resources web page.
+
+
+
+
+ Contact the foundation
+ To learn more about the OpenPOWER Foundation, please use the following contact points:
+
+
+ General information -- info@openpowerfoundation.org
+
+
+
+ Membership -- membership@openpowerfoundation.org
+
+
+
+ Technical Work Groups and projects -- Jeff Brown, TSC Chair, tsc-chair@openpowerfoundation.org
+
+
+
+ Events and other activities -- Michelle Hunt, OpenPOWER ED, m.hunt@ieee.org
+
+
+
+ Press/Analysts -- press@openpowerfoundation.org
+
+
+
+
+
+ More contact information the foundation governance can be found at
+ openpowerfoundation.org/get-involved/contact-us.
+
+
+
+
diff --git a/doc/common/app_support.xml b/doc/common/app_support.xml
new file mode 100644
index 0000000..590d924
--- /dev/null
+++ b/doc/common/app_support.xml
@@ -0,0 +1,437 @@
+
+
+
+ Community support
+ The following resources are available to help you run and use
+ OpenStack. The OpenStack community constantly improves and
+ adds to the main features of OpenStack, but if you have
+ any questions, do not hesitate to ask. Use the
+ following resources to get OpenStack support,
+ and troubleshoot your installations.
+
+ Documentation
+ For the available OpenStack documentation, see docs.openstack.org.
+ To provide feedback on documentation, join and use the
+ openstack-docs@lists.openstack.org
+ mailing list at OpenStack Documentation Mailing List, or report a bug.
+ The following books explain how to install an OpenStack
+ cloud and its associated components:
+
+
+
+
+ Installation Guide for Debian
+ 7.0
+
+
+
+
+
+ Installation Guide for openSUSE and
+ SUSE Linux Enterprise Server
+
+
+
+
+
+ Installation Guide for Red Hat
+ Enterprise Linux, CentOS, and
+ Fedora
+
+
+
+
+
+ Installation Guide for Ubuntu 14.04
+ (LTS)
+
+
+
+ The following books explain how to configure and run an
+ OpenStack cloud:
+
+
+ Architecture Design
+ Guide
+
+
+
+ Cloud Administrator
+ Guide
+
+
+ Configuration
+ Reference
+
+
+ Operations
+ Guide
+
+
+ High Availability
+ Guide
+
+
+ Security
+ Guide
+
+
+ Virtual Machine Image
+ Guide
+
+
+ The following books explain how to use the OpenStack
+ dashboard and command-line clients:
+
+
+
+ API Quick
+ Start
+
+
+
+ End User
+ Guide
+
+
+
+ Admin User
+ Guide
+
+
+
+ Command-Line Interface
+ Reference
+
+
+ The following documentation provides reference and
+ guidance information for the OpenStack APIs:
+
+
+ OpenStack API Complete
+ Reference (HTML)
+
+
+ API Complete Reference (PDF)
+
+
+ OpenStack Block Storage
+ Service API v2
+ Reference
+
+
+ OpenStack Compute API v2 and
+ Extensions
+ Reference
+
+
+ OpenStack Identity Service API
+ v2.0 Reference
+
+
+ OpenStack Image Service API v2
+ Reference
+
+
+ OpenStack Networking API v2.0
+ Reference
+
+
+ OpenStack Object Storage API
+ v1 Reference
+
+
+ The Training Guides
+ offer software training for cloud administration and
+ management.
+
+
+ ask.openstack.org
+ During the set up or testing of OpenStack, you might
+ have questions about how a specific task is completed or
+ be in a situation where a feature does not work correctly.
+ Use the ask.openstack.org site to ask questions and
+ get answers. When you visit the http://ask.openstack.org site, scan the
+ recently asked questions to see whether your question has
+ already been answered. If not, ask a new question. Be sure
+ to give a clear, concise summary in the title and provide
+ as much detail as possible in the description. Paste in
+ your command output or stack traces, links to screen
+ shots, and any other information which
+ might be useful.
+
+
+ OpenStack mailing lists
+ A great way to get answers and insights is to post your
+ question or problematic scenario to the OpenStack mailing
+ list. You can learn from and help others who might have
+ similar issues. To subscribe or view the archives, go to
+ http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack.
+ You might be interested in the other mailing lists for
+ specific projects or development, which you can find on
+ the wiki. A description of all mailing lists is
+ available at http://wiki.openstack.org/MailingLists.
+
+
+ The OpenStack wiki
+ The OpenStack
+ wiki contains a broad range of topics but some of the
+ information can be difficult to find or is a few pages deep.
+ Fortunately, the wiki search feature enables you to search by title
+ or content. If you search for specific information, such as about
+ networking or nova, you can find a large amount of relevant
+ material. More is being added all the time, so be sure to check back
+ often. You can find the search box in the upper-right corner of any
+ OpenStack wiki page.
+
+
+ The Launchpad Bugs area
+ The OpenStack community values your set up and testing efforts and
+ wants your feedback. To log a bug, you must sign up for a Launchpad
+ account at https://launchpad.net/+login. You can view existing bugs
+ and report bugs in the Launchpad Bugs area. Use the search feature
+ to determine whether the bug has already been reported or already
+ been fixed. If it still seems like your bug is unreported, fill out
+ a bug report.
+ Some tips:
+
+
+ Give a clear, concise summary.
+
+
+ Provide as much detail as possible in the
+ description. Paste in your command output or stack
+ traces, links to screen shots, and any
+ other information which might be useful.
+
+
+ Be sure to include the software and package
+ versions that you are using, especially if you are
+ using a development branch, such as,
+ "Juno release" vs git commit
+ bc79c3ecc55929bac585d04a03475b72e06a3208.
+
+
+ Any deployment-specific information is helpful, such as
+ whether you are using Ubuntu 14.04 or are performing a
+ multi-node installation.
+
+
+ The following Launchpad Bugs areas are available:
+
+
+
+ Bugs: OpenStack Block Storage
+ (cinder)
+
+
+ Bugs: OpenStack Compute (nova)
+
+
+ Bugs: OpenStack Dashboard
+ (horizon)
+
+
+ Bugs: OpenStack Identity
+ (keystone)
+
+
+ Bugs: OpenStack Image Service
+ (glance)
+
+
+ Bugs: OpenStack Networking
+ (neutron)
+
+
+ Bugs: OpenStack Object Storage
+ (swift)
+
+
+
+ Bugs: Bare Metal (ironic)
+
+
+ Bugs: Data Processing Service
+ (sahara)
+
+
+ Bugs: Database Service (trove)
+
+
+ Bugs: Orchestration (heat)
+
+
+ Bugs: Telemetry (ceilometer)
+
+
+ Bugs: Queue Service (marconi)
+
+
+
+ Bugs: OpenStack API Documentation
+ (developer.openstack.org)
+
+
+ Bugs: OpenStack Documentation
+ (docs.openstack.org)
+
+
+
+
+ The OpenStack IRC channel
+ The OpenStack community lives in the #openstack IRC channel on the
+ Freenode network. You can hang out, ask questions, or get immediate
+ feedback for urgent and pressing issues. To install an IRC client or
+ use a browser-based client, go to http://webchat.freenode.net/. You can also use Colloquy
+ (Mac OS X, http://colloquy.info/), mIRC (Windows, http://www.mirc.com/),
+ or XChat (Linux). When you are in the IRC channel and want to share
+ code or command output, the generally accepted method is to use a
+ Paste Bin. The OpenStack project has one at http://paste.openstack.org. Just paste your longer
+ amounts of text or logs in the web form and you get a URL that you
+ can paste into the channel. The OpenStack IRC channel is
+ #openstack on
+ irc.freenode.net. You can find a list of all
+ OpenStack IRC channels at https://wiki.openstack.org/wiki/IRC.
+
+
+ Documentation feedback
+ To provide feedback on documentation, join and use the
+ openstack-docs@lists.openstack.org mailing list at
+ OpenStack
+ Documentation Mailing List, or report a bug.
+
+
+ OpenStack distribution packages
+ The following Linux distributions provide
+ community-supported packages for OpenStack:
+
+
+ Debian:
+ http://wiki.debian.org/OpenStack
+
+
+ CentOS, Fedora, and Red
+ Hat Enterprise Linux:
+ http://openstack.redhat.com/
+
+
+ openSUSE and SUSE Linux
+ Enterprise Server:
+ http://en.opensuse.org/Portal:OpenStack
+
+
+ Ubuntu:
+ https://wiki.ubuntu.com/ServerTeam/CloudArchive
+
+
+
+
diff --git a/doc/common/ch_preface.xml b/doc/common/ch_preface.xml
new file mode 100644
index 0000000..1b01521
--- /dev/null
+++ b/doc/common/ch_preface.xml
@@ -0,0 +1,12 @@
+
+
+ Preface
+
+
+
+
+
diff --git a/doc/common/sec_conventions.xml b/doc/common/sec_conventions.xml
new file mode 100644
index 0000000..4a02019
--- /dev/null
+++ b/doc/common/sec_conventions.xml
@@ -0,0 +1,40 @@
+
+
+
+ Conventions
+ The OpenPOWER Foundation documentation uses several typesetting conventions.
+
+ Notices
+ Notices take these forms:
+
+ A handy tip or reminder.
+
+
+ Something you must be aware of before proceeding.
+
+
+ Critical information about the risk of data loss or security issues.
+
+
+
+ Command prompts
+
+
+ $ prompt
+
+ Any user, including the root user, can run commands that are
+ prefixed with the $ prompt.
+
+
+
+ # prompt
+
+ The root user must run commands that are prefixed with the
+ # prompt. You can also prefix these commands with the
+ sudo command, if available, to run them.
+
+
+
+
+
diff --git a/doc/common/sec_dochistory.xml b/doc/common/sec_dochistory.xml
new file mode 100644
index 0000000..8ece017
--- /dev/null
+++ b/doc/common/sec_dochistory.xml
@@ -0,0 +1,13 @@
+
+
+ Document change history
+
+ This version of the guide replaces and obsoletes all earlier versions.
+ The following table describes the most recent changes:
+
+
+
diff --git a/doc/pom.xml b/doc/pom.xml
new file mode 100644
index 0000000..c3e9c42
--- /dev/null
+++ b/doc/pom.xml
@@ -0,0 +1,51 @@
+
+
+ 4.0.0
+
+ org.openpowerfoundation.docs
+
+ parent-pom
+ 1.0.0-SNAPSHOT
+ pom
+
+
+ template
+
+
+
+ OpenPOWER Foundation Repositories
+
+ true
+
+
+
+ openpower-foundation
+ OpenPOWER Foundation Repository
+ http://rchgsa.ibm.com/gsa/rchgsa/home/s/c/scheel/web/public/repo.openpowerfoundation.org/
+
+
+
+
+
+ openpower-foundation
+ OpenPOWER Foundation Repository
+ http://rchgsa.ibm.com/gsa/rchgsa/home/s/c/scheel/web/public/repo.openpowerfoundation.org/
+
+
+
+
+
+
+
+
+
+ org.openpowerfoundation.docs
+
+ openpowerdocs-maven-plugin
+ 1.0.1
+
+
+
+
diff --git a/doc/template/app_template.xml b/doc/template/app_template.xml
new file mode 100644
index 0000000..3dcf89e
--- /dev/null
+++ b/doc/template/app_template.xml
@@ -0,0 +1,14 @@
+
+
+
+ Appendix template
+ This is the first paragraph of a new appendix...
+
+ Section title
+ Section text...
+
+
diff --git a/doc/template/bk_main.xml b/doc/template/bk_main.xml
new file mode 100644
index 0000000..2482fbf
--- /dev/null
+++ b/doc/template/bk_main.xml
@@ -0,0 +1,88 @@
+
+
+
+
+
+
+ Template Guide
+
+ A quick start template
+
+
+
+
+
+ Firstname
+ Lastname
+
+
+ Email@domain
+
+
+ Company
+
+
+
+
+ 2015
+ OpenPOWER Foundation
+
+
+ Revision 0.9
+ OpenPOWER
+
+
+
+
+
+
+
+ Copyright details are filled in by the template.
+
+
+
+
+
+
+
+
+ 2014-09-03
+
+
+
+ Creation based on OpenStack documentation
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/template/ch_example.xml b/doc/template/ch_example.xml
new file mode 100644
index 0000000..6d1ec47
--- /dev/null
+++ b/doc/template/ch_example.xml
@@ -0,0 +1,202 @@
+
+
+
+ Documentation examples
+
+
+
+ Section Title goes here
+ This Section covers something of interest to a limited number of people and shows a 1st level section
+
+
+ Example Itemized List
+
+ Here's an example of an itemized list
+
+
+
+ Item you don't care about
+
+
+
+ Item you might care about
+
+
+
+ Item you do care about
+
+
+
+
+ Example ordered list
+
+ All good documents need ordered lists.
+
+
+ First item
+
+
+ Second item
+
+
+ first indented item
+
+
+ second indented item
+
+
+
+
+ Third item
+
+
+
+
+
+ Example figure with embedded graphic
+
+ Here is how you embed a graphic.
+
+ Example figure
+
+
+
+
+
+
+
+
+
+ Example table
+ Of course all good documents need tables. Here's how you build a basic table.
+
+
+ Example Table Title
+
+
+
+
+
+
+
+
+
+ 1st Column Heading
+
+
+
+
+ 2nd Column Heading
+
+
+
+
+ 3rd Column Heading
+
+
+
+
+ 4th Column Heading
+
+
+
+
+
+
+
+ Yes
+
+
+ Red
+ Green
+ Blue
+ Custom (Amber)
+
+
+ MAIN_Junk
+
+
+ More_Junk
+
+
+
+
+ merged cells horizontal
+
+
+ cell_stuff
+
+
+
+
+ Merge cells vertical
+
+
+ filler
+
+
+ merge cells both ways
+
+
+
+
+ filler 2
+
+
+
+
+ How about we put a list in the table cell
+
+
+ item 1
+
+
+ item 2
+
+
+ item 2
+
+
+
+
+ Another Cell
+
+
+ Yet Another Cell
+
+
+ Finally the last cell
+
+
+
+
+
+
+
+ Example of crossreferences and footnotes
+ To reference another section or table is pretty easy. For example: see for how tables look.
+ Lists are shown in and if you need to make a footnote
+ The footnote text goes here and can reference something like for additional explanation.
+ For clarification that is easy. Of course you might want an additional reference to the footnote which can also be done easily.
+ Lastly you probably want to mark text by making it italic text example or Bold Text Example.
+
+
+ Example of code citations and user input
+ When showing user input, you want a nice sceen-looking layout, a prompt, monospace text, and a way to differentiate input from output. Here's an example:
+ $echo "Hello world"
+Hello world
+$
+
+ Docbook also allows for formatting and display of common languages, allowing for whitespace
+ and line returns just as they are written. Here's a sample snippet of C code with line numbering enabled:
+main()
+{
+ printf("Hello world\n");
+}]]>
+ If code formatting is not quite what you need, simply displaying text "literally" may suffice as follows: This is my literal
+text. It ignores whitespace.
+
+
+
+
diff --git a/doc/template/ch_template_overview.xml b/doc/template/ch_template_overview.xml
new file mode 100644
index 0000000..a2e357b
--- /dev/null
+++ b/doc/template/ch_template_overview.xml
@@ -0,0 +1,55 @@
+
+
+ Template document overview
+
+ The OpenPOWER Foundation documentation template provides a framework for OpenPOWER public and private
+ documentation. The goal of the template and this writeup is to promote community contributions
+ to OpenPOWER documenation and to enable new contributions within a common look and feel.
+
+ The major sections of this document addresses the following topics:
+
+
+ Getting started: This section details tools and commands used to contribute to OpenPOWER documentation.
+ All users who are new to OpenPOWER Foundation documentation should start here.
+
+
+ Creating a new document: This section provides step-by-step instructions on how to create a new document
+ from scratch. Use this section to start a new documentation project.
+
+
+ Modifying an existing document: This section highlights common steps in editing an existing OpenPOWER
+ Foundation document. Use this section as a guideline for contributing to an existing document.
+
+
+ Debugging build failures: This section provides examples of the two most common types of build failures
+ and helps users find the relevant failure information.
+
+
+ Policies and conventions: This secion contains
+ the generally accepted guidelines for creating OpenPOWER documentation. Use this section as a reference
+ for documentation style beyond template provided features.
+
+
+ Frequently asked questions: This section answers common questions. Use this section when the other sections
+ do not answer your questions.
+
+
+ Where to find more information: This section provides pointers to on-line information about XML, Docbook,
+ Maven, and other relevant references.
+
+
+
+ In addition to OpenPOWER Foundation specific topics,
+ provides examples of common documenation constructs in XML.
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/template/figures/example_graphic.bmp b/doc/template/figures/example_graphic.bmp
new file mode 100644
index 0000000..296b4ea
Binary files /dev/null and b/doc/template/figures/example_graphic.bmp differ
diff --git a/doc/template/figures/example_graphic.odg b/doc/template/figures/example_graphic.odg
new file mode 100644
index 0000000..9a0a43e
Binary files /dev/null and b/doc/template/figures/example_graphic.odg differ
diff --git a/doc/template/pom.xml b/doc/template/pom.xml
new file mode 100644
index 0000000..c98dd60
--- /dev/null
+++ b/doc/template/pom.xml
@@ -0,0 +1,128 @@
+
+
+
+
+ org.openpowerfoundation.docs
+ parent-pom
+ 1.0.0-SNAPSHOT
+ ../pom.xml
+
+ 4.0.0
+
+
+ openpower-template-guide
+
+ jar
+
+
+ OpenPOWER Template Guide
+
+
+
+
+ 0
+
+
+
+
+
+
+
+
+ org.openpowerfoundation.docs
+
+ openpowerdocs-maven-plugin
+
+
+
+ generate-webhelp
+
+ generate-webhelp
+
+ generate-sources
+
+
+ ${comments.enabled}
+ openpower-template-guide
+ 1
+ UA-17511903-1
+
+ appendix toc,title
+ article/appendix nop
+ article toc,title
+ book toc,title,figure,table,example,equation
+ book/appendix nop
+ book/chapter nop
+ chapter toc,title
+ chapter/section nop
+ section toc
+ part toc,title
+ qandadiv toc
+ qandaset toc
+ reference toc,title
+ set toc,title
+
+
+ 1
+ 1
+ 1
+
+
+ template-guide
+
+
+ template-guide
+
+
+ review
+
+
+
+
+
+
+ workgroupNotes
+
+
+
+
+
+
+
+
+
+ true
+ .
+
+
+ bk_main.xml
+
+
+
+
+ ${basedir}/../glossary/glossary-terms.xml
+ 1
+ www.openpowerfoundation.org
+
+
+
+
+
diff --git a/doc/template/sec_template_debugging.xml b/doc/template/sec_template_debugging.xml
new file mode 100644
index 0000000..ed252c6
--- /dev/null
+++ b/doc/template/sec_template_debugging.xml
@@ -0,0 +1,66 @@
+
+
+ Debugging build failures
+ Maven/docbkx failures generally fall into one of two categories, validation errors or build failures. Correcting the document begins with understanding which type of failure has occurred and understanding where to look in your document source.
+ Validation errors are generally indicated in the build output with text like the following:
+...
+@@@@@@@@@@@@@@@@@@@@@@
+!!!VALIDATION ERRORS!!
+!!!!!!!!!!!!!!!!!!!!!!
+
+Note: Open the temporary file:
+
+file:/home/user1/openpower-foundation-docbkx-framework/doc/template/target//bk_main.xml-invalid.xml
+
+to see all the errors in context.
+You must correct the errors in the original
+source DocBook or wadl files however.
+
+You can control whether build fails or not by
+setting failOnValidationError to no in your pom.
+
+lineNumber: 272; columnNumber: 70; text not allowed here; expected element "address", ...
+
+ This error message contains three key pieces of information:
+
+
+ The full path and filename that contains the context for the failure. In the message above, this is
+/home/user1/openpower-foundation-docbkx-framework/doc/template/target//bk_main.xml-invalid.xml.
+
+
+ The location within the file of the syntax error. For the above example, the key information is "lineNumber: 272; columnNumber: 70.
+
+
+ An explanation of the failure. This information in the above error reads, "text not allowed here; expected element "address", ...".
+
+
+ Build errors are easily identified as well. Below is an example:
+...
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD FAILURE
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 4.827s
+[INFO] Finished at: Wed Jul 29 14:55:33 CDT 2015
+[INFO] Final Memory: 17M/171M
+[INFO] ------------------------------------------------------------------------
+[ERROR] Failed to execute goal org.openpowerfoundation.docs:openpowerdocs-maven-plugin:1.0.0:generate-webhelp (generate-webhelp) on project openpower-template-guide: Execution generate-webhelp of goal org.openpowerfoundation.docs:openpowerdocs-maven-plugin:1.0.0:generate-webhelp failed: XInclude resource error (sec_template_new_document.xml) and no fallback provided. XProc error err:XD0011: org.xml.sax.SAXParseException; systemId: file:/home/user1/openpower-foundation-docbkx-framework/doc/template/sec_template_new_document.xml; lineNumber: 55; columnNumber: 17; The element type "para" must be terminated by the matching end-tag "</para>". -> [Help 1]...
+
+ Like validation errors, three key pieces of information are again provided:
+
+
+ The full path and filename of our failure is
+/home/user1/openpower-foundation-docbkx-framework/doc/template/sec_template_new_document.xml.
+
+
+ The location within the file of the error is "lineNumber: 55; columnNumber: 17.
+
+
+ An explanation of the failure begins with the text, "The element type "para" must be terminated by the matching end-tag "</para>."
+
+
+ With these details in hand for either error, one simply locates the offending syntax and makes the appropriate correction. Online resources such as those listed in may be helpful.
+
+
+
+
diff --git a/doc/template/sec_template_existing_document.xml b/doc/template/sec_template_existing_document.xml
new file mode 100644
index 0000000..04365b4
--- /dev/null
+++ b/doc/template/sec_template_existing_document.xml
@@ -0,0 +1,54 @@
+
+
+ Modifying an existing document
+ To obtain a copy of the existing template document framework and all public documents from the
+ public OpenPOWER git repository, simply clone the project using this command:$git clone https://github.com/open-power/openpower-foundation-docbkx-framework.git
+Cloning into 'openpower-foundation-docbkx-framework'...
+remote: Counting objects: 288, done.
+remote: Compressing objects: 100% (157/157), done.
+remote: Total 288 (delta 121), reused 288 (delta 121)
+Receiving objects: 100% (288/288), 12.41 MiB | 8.04 MiB/s, done.
+Resolving deltas: 100% (121/121), done.
+Checking connectivity... done.
+~$
+
+ To build a document such as the template guide, follow these steps from the directory where you just cloned:$cd openpower-foundation-docbkx-framework/doc/template
+$mvn clean
+[INFO] Scanning for projects...
+[INFO]
+[INFO] ------------------------------------------------------------------------
+[INFO] Building OpenPOWER Template Guide 1.0.0-SNAPSHOT
+[INFO] ------------------------------------------------------------------------
+[INFO]
+[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ openpower-template-guide ---
+[INFO] Deleting ~/openpower-foundation-docbkx-framework/doc/template/target
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESS
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 0.353s
+[INFO] Finished at: Wed Feb 25 12:54:47 CST 2015
+[INFO] Final Memory: 3M/7M
+[INFO] ------------------------------------------------------------------------
+$mvn generate-sources
+[INFO] Scanning for projects...
+[INFO]
+[INFO] ------------------------------------------------------------------------
+[INFO] Building OpenPOWER Template Guide 1.0.0-SNAPSHOT
+[INFO] ------------------------------------------------------------------------
+[INFO]
+[INFO] --- openpowerdocs-maven-plugin:1.0.0:generate-webhelp (generate-webhelp) @ openpower-template-guide ---
+[INFO] Processing input file: bk_main.xml
+...
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESS
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 20.361s
+[INFO] Finished at: Wed Feb 25 12:55:15 CDT 2015
+[INFO] Final Memory: 30M/390M
+[INFO] ------------------------------------------------------------------------
+$
+ If all goes well, the generated pdf should be available in ~/openpower-foundation-docbkx-framework/doc/template/target/docbkx/webhelp/template-guide/.
+
+
+
diff --git a/doc/template/sec_template_faq.xml b/doc/template/sec_template_faq.xml
new file mode 100644
index 0000000..30b4640
--- /dev/null
+++ b/doc/template/sec_template_faq.xml
@@ -0,0 +1,18 @@
+
+
+ Frequently asked questions
+ The list of questions and answers may be helpful to first time document writers:
+
+
+ Do I have to follow the guidelines in of this guide?
+ No. HOWEVER, doing so makes it simpler for all community members to participate in maintaining your document.
+
+
+ Question 2...
+ Answer 2...
+
+
+
+
+
diff --git a/doc/template/sec_template_getting_started.xml b/doc/template/sec_template_getting_started.xml
new file mode 100644
index 0000000..721c042
--- /dev/null
+++ b/doc/template/sec_template_getting_started.xml
@@ -0,0 +1,61 @@
+
+
+ Getting started
+ To begin contributing to the OpenPOWER Foundation documentation, the following steps must be completed:
+
+
+ Install tools
+
+
+ Create accounts
+
+
+
+
+ Once complete, you can proceed to either or
+ as needed.
+
+
+ Installing tools
+ Only two tools are required to update documentation, git and maven. Git manages the documentation
+ source and maven provides the build framework to create the published content in PDF and html form.
+ Installation steps for these tools varies by operating system.
+ On Debian-based Linux operating systems (Ubuntu and Debian), install maven and git as follows:
+ $sudo apt-get install git
+$sudo apt-get install maven
+ On RPM-based Linux operating systems (Fedora, RHEL, openSUSE, SLES), install maven and git as follows:
+ $sudo yum install git
+$sudo yum install maven
+ On Mac OS X, use Macports to install maven and git as follows:
+ $sudo port install git
+$sudo port install maven3
+ or use Homebrew to install maven and git as follows:
+ $brew install git
+$brew install maven
+ For information on how to setup the environment on Windows, see the following websites:
+
+
+ git for Windows - http://msysgit.github.io/
+
+
+ Maven on Windows -
+ http://maven.apache.org/guides/getting-started/windows-prerequisites.html
+
+
+
+
+
+
+ Creating accounts
+ All OpenPOWER project documentation is maintained in GitHub trees, public and private. To join the GitHub community,
+ apply at https://github.com/join.
+ If you will be participating in private OpenPOWER Foundation trees, you will need to visit the OpenPOWER Foundation Members
+ Area wiki to find administrators for the appropriate git tree.
+ To learn more about using git, see the online article in GitHub Help, "Good Resources for Learning Git and GitHub." at
+
+ https://help.github.com/articles/good-resources-for-learning-git-and-github/.
+
+
+
+
diff --git a/doc/template/sec_template_new_document.xml b/doc/template/sec_template_new_document.xml
new file mode 100644
index 0000000..5203f93
--- /dev/null
+++ b/doc/template/sec_template_new_document.xml
@@ -0,0 +1,122 @@
+
+
+ Creating a new document
+ Creating a new document from scratch follows four simple steps:
+
+
+ Clone the appropriate template document framework.
+
+
+ Copy the template directory into a new project directory.
+
+
+ Modify core project files.
+
+
+ Begin adding document content, either from scratch or from another document.
+
+
+
+
+ Cloning the base document framework
+ All new projects need to begin by cloning the appropriate documentation template. The template document project resides at https://github.com/open-power/openpower-foundation-docbkx-framework.git. This template should be used for both private and public OpenPOWER Foundation documents.
+ To clone the existing template document framework use the clone git command:$git clone https://github.com/open-power/openpower-foundation-docbkx-framework.git
+Cloning into 'openpower-foundation-docbkx-framework'...
+remote: Counting objects: 288, done.
+remote: Compressing objects: 100% (157/157), done.
+remote: Total 288 (delta 121), reused 288 (delta 121)
+Receiving objects: 100% (288/288), 12.41 MiB | 8.04 MiB/s, done.
+Resolving deltas: 100% (121/121), done.
+Checking connectivity... done.
+$
+ This command clones the head of the git tree into your current working directory. If successful, the contents of the current directory should now include a new openpower-foundation-docbkx-framework directory.
+
+
+
+ Copying the template directory into a new project directory
+ To create a new document directory, follow these steps:
+
+
+ Navigate down to the doc sub-directory. On Linux and Mac OS command lines, this can be achieved using the cd command:
+$cd /openpower-foundation-docbkx-framework/doc
+$
+ This directory should contain at least two directories, one named doc and another template, as well as a pom.xml file.
+
+
+ To create a new project directory, simply create a new directory and copy the contents of the template directory. If creating a new project named my_proj via a command line in Linux or Mac OS, the command sequence would look like this:
+$mkdir my_proj
+$cp -r template/* my_proj
+$
+
+
+ Finally, make sure to add the new directory to the git repository.
+$git add my_proj
+
+
+
+
+
+ Modifying core project files
+ The first step to customizing a new project is to modify two core project files--pom.xml and bk_main.xml. Within these two files are XML comment tags that begin "<!-- TODO:" to identify places which need customization. The surrounding comments will provide guidance on what needs to change and how it may be changed. Simply work through each item, making updates as requested.
+ Be sure to remember two key values you used in the pom.xml file, <webhelpDirname> and <pdfFilenameBase>, as these will be used to locate your generated document.
+ When complete, be sure to build your new document using standard maven commands like this:$cd openpower-foundation-docbkx-framework/doc/template
+$mvn clean
+[INFO] Scanning for projects...
+[INFO]
+[INFO] ------------------------------------------------------------------------
+[INFO] Building OpenPOWER Template Guide 1.0.0-SNAPSHOT
+[INFO] ------------------------------------------------------------------------
+[INFO]
+[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ openpower-template-guide ---
+[INFO] Deleting ~/openpower-foundation-docbkx-framework/doc/my_proj/target
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESS
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 0.353s
+[INFO] Finished at: Wed Feb 25 12:54:47 CST 2015
+[INFO] Final Memory: 3M/7M
+[INFO] ------------------------------------------------------------------------
+$mvn generate-sources
+[INFO] Scanning for projects...
+[INFO]
+[INFO] ------------------------------------------------------------------------
+[INFO] Building OpenPOWER Template Guide 1.0.0-SNAPSHOT
+[INFO] ------------------------------------------------------------------------
+[INFO]
+[INFO] --- openpowerdocs-maven-plugin:1.0.0:generate-webhelp (generate-webhelp) @ openpower-template-guide ---
+[INFO] Processing input file: bk_main.xml
+...
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESS
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 20.361s
+[INFO] Finished at: Wed Feb 25 12:55:15 CDT 2015
+[INFO] Final Memory: 30M/390M
+[INFO] ------------------------------------------------------------------------
+$
+ If all goes well, the new generated pdf should be available in target/docbkx/webhelp/<webhelpDirname>/<pdfFilenameBase>.pdf.
+
+
+
+ Adding new content
+ The starting point for book content is the bk_main.xml file (or whatever to which it was renamed in the previous step). Removal and additions of the main chapter files files will be controlled by entries near the end of that file which appear as follows:
+
+
+
+
+
+
+
+
+
+
+
+
+]]>
+ Copying and modifying existing files from the template or other documents is a great way to get started. When creating whole new chapter or appendix files from scratch, the ch_example.xml and app_template.xml files may serve as excellent starting points. For XML examples of various document structures, please see and its supporting source files in this document. Online resources such as those listed in may also be helpful.
+ When creating new files for the project, remember to use the git add <file name> command to add new files to the git tree.
+
+
+
+
diff --git a/doc/template/sec_template_policies.xml b/doc/template/sec_template_policies.xml
new file mode 100644
index 0000000..102ecb6
--- /dev/null
+++ b/doc/template/sec_template_policies.xml
@@ -0,0 +1,30 @@
+
+
+ Policies and conventions
+ Most document style policies are established simply by using the template documentation framework. However, by applying some conventions to the document source structure, community members will be able to work across more documentation projects.
+ The recommended documentation structure guidelines are as follows:
+
+
+ The head book file should be named with the prefix "bk_".
+
+
+ The document versioning as defined by the releaseinfo tag in the main book file bk_xxx should be named "Revision N.N", not "Version N.N" or simply "N.N"
+
+
+ Chapters files should be named with the prefix "ch_".
+
+
+ Section and sub-section files should be named with the prefix "sec_".
+
+
+ Appendix files should be named with the prefix "app_".
+
+
+ Figures source and images should be placed in the figures sub-directory for the document.
+
+
+
+
+
+
diff --git a/doc/template/sec_template_references.xml b/doc/template/sec_template_references.xml
new file mode 100644
index 0000000..472afc6
--- /dev/null
+++ b/doc/template/sec_template_references.xml
@@ -0,0 +1,22 @@
+
+
+ Where to find more information
+ The following lists of references may be helpful in learning about XML, Docbook, and/or Maven:
+
+
+ XML In a Nutshell by Elliotte Rusy Harold and W. Scott Means. Online at http://docstore.mik.ua/orelly/xml/xmlnut/index.htm.
+
+
+ DocBook 5: The Definitive Guide by Normal Walsh. Online at https://www.safaribooksonline.com/library/view/docbook-5-the/9781449380243/.
+
+
+ DocBook XSL: The Complete Guide by Bob Stayton. Online at http://www.sagehill.net/docbookxsl/.
+
+
+ Maven: The Complete Reference by Tim O'Brien, Manfred Moser, John Casey, Brian Fox, Jason Van Zyl, Eric Redmond, and Larry Shatzer. Online at http://books.sonatype.com/mvnref-book/reference/index.html.
+
+
+
+
+