[jboss-cvs] jboss-profiler/docbook/docbook-support/docs/guide/en ...

[Clebert Suconic]

  User: csuconic
  Date: 06/11/10 12:40:23

  Added:       docbook/docbook-support/docs/guide/en  master.xml
  Log:
  Adding docbook under jboss-profiler tree
  
  Revision  Changes    Path
  1.1      date: 2006/11/10 17:40:23;  author: csuconic;  state: Exp;jboss-profiler/docbook/docbook-support/docs/guide/en/master.xml
  
  Index: master.xml
  ===================================================================
  <?xml version='1.0' encoding="iso-8859-1"?>
  <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
                        "../../../../docbook-support/support/docbook-dtd/docbookx.dtd"
  [
  <!ENTITY introduction          SYSTEM "modules/introduction.xml">
  <!ENTITY howto                 SYSTEM "modules/howto.xml">
  <!ENTITY styles                SYSTEM "modules/styles.xml">
  ]>
  <book lang="en">
      <bookinfo>
          <title>How to use the JBoss DocBook system</title>
          <subtitle>A guide for content developers</subtitle>
          <releaseinfo>1.0</releaseinfo>
      </bookinfo>
      
      <toc/>
      
      <preface id="target" revision="1">
          <title>Target Audience</title>
          <para> All JBoss documentation content developers and style developers
              should read this document. You should also read this if you want to
              build JBoss DocBooks from the public CVS tree. </para>
      </preface>
      
      <preface id="preface" revision="1">
          <title>Preface</title>
          <para> This document introduces the new unified DocBook system for JBoss
              documentation in the public CVS tree. There are a couple of reasons
              why we did this. </para>
          <itemizedlist>
              <listitem> It provides a unified set of styles to make sure that all
                  JBoss DocBooks have a consistent look and feel. </listitem>
              <listitem> The styles can be managed from a central location. We can
                  design new styles or fix bugs without worrying about
                  "deployment" issues. </listitem>
              <listitem> The libraries and build scripts can also be managed from
                  a central location. </listitem>
              <listitem> The build process is simplified and standardized. Just
                  follow the simple instructions in this guide to setup your docs
                  directory and copy a very simple <literal>build.xml</literal>
                  file. </listitem>
              <listitem> Last but not least, we can reduce the duplication of
                  style sheets, XSLs and libraries in the system. </listitem>
          </itemizedlist>
          
          <para> If you have questions, please feel free to contact Michael Yuan
              or Norman Richards for more information. </para>
      </preface> 
  
  &introduction; 
  
  &howto; 
  
  &styles;
  
  </book>