# 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 and are packaged the same way.

1. On a workstation, create a product or version page using the procedure described in .

2. In the directory in which you created the product page or version page, run:

       $ publican package --binary

   Publican builds an RPM package and places it in the `/tmp/rpms/noarch/` directory of the product page or version page. By default, Publican builds the RPM package for the operating system within which you are running Publican. To build an RPM package to install on a server that runs a different operating system, set the `os_ver` parameter in the `publican.cfg` file of the product page or version page.

3. Either upload the package to the webserver and install it with the `rpm -i` or `yum localinstall` command, or place the package in a repository and configure the webserver to install from that repository when you run `yum install`.

To update the product page or version page, build a new package with a higher `<edition>` number or `<pubsnumber>` in the `Article_Info.xml`. Publican uses these values to set the version and release numbers for the RPM package. When you install this package on your webserver, yum can replace the old version with the new when you run `yum localinstall` for a local package, or `yum update` for a package fetched from a repository.