# Creating, installing, and updating product pages and version pages

Publican-generated product pages and version pages are the localizable pages that provide a general overview of a product or version respectively. Visitors access these pages by clicking on a product or version in the navigation menu. The pages are structured as DocBook `<article>`s with an extra `web_type: product` or `web_type: version` parameter in their `publican.cfg` files. In their structure and presentation, product pages and version pages are the same as any other article that you produce with Publican. To create a product page or version page:

1. Change into a convenient directory and run the following $ `publican create` command:

       $ publican create --type Article --name page_name

   For example, a product page might be:

       $ publican create --type Article --name FooMaster

   or a version page might be:

       $ publican create --type Article --name FooMaster_3

2. Change into the article directory:

       $ cd page_name

   For example:

       $ cd FooMaster

3. Unlink the `Article_Info.xml` file from your root XML file.

   Little of the content of the `Article_Info.xml` file is likely to be useful for product pages or version pages. Therefore, edit the root XML file of your page to remove the `<xi:include>` tag that links to `Article_Info.xml`. Publican still uses the information in `Article_Info.xml` for packaging, but does not include it on the page itself.

4. Edit the `publican.cfg` file.

   At the very least, you must add the `web_type` parameter and set it to `product` or `version`:

       web_type: product

   or

       web_type: version

   The `web_type` parameter instructs Publican to process this document differently from product documentation. This is the only mandatory change to the `publican.cfg` file. Other optional changes to the `publican.cfg` file that are frequently useful for product pages or version pages include:

   `brand`

     To style your home page to match your documents, add:

         brand: name_of_brand

   `docname`
   `product`

     If the `<title>` or the `<product>` that you set in the `Article_Info` file included anything other than basic, unaccented Latin characters, set the `docname` and `product` as necessary.

5. Edit the content of the `page_name.xml` file (for example, `FooMaster.xml`) as you would any other DocBook document.

   If you remove the `<xi:include>` that links to `Article_Info.xml`, specify a title for your page in the following format:

       <title role="producttitle">FooMaster Documentation</title>

6. If you publish documentation in more than one language, create a set of POT files and a set of PO files for each language with the $ `publican update_pot` and `publican update_po` commands.

7. Build the product page or version page in single-page HTML format with the `--embedtoc` option and install it in your website structure. For example:

       $ publican build --publish --formats html-single --embedtoc --langs all
       $ publican install_book --site_config ~/docsite/foomaster.cfg --lang Language_Code

   Note that you can build all languages at the same time, but must install the product page or version page for each language with a separate $ `publican install_book` command.