Writing and publishing with Joomla

Hi All,

A few years ago, I built a publishing platform with Joomla for a technical writing department. While it was short lived (the system was up and running for about a year), I thought it was a great tool. I recently published an ebook on Scribd that explains how I installed Joomla and configured it as a publishing platform, which you can read for free at the following address: http://www.scribd.com/doc/45365813/Joomla-for-Professional-Writers

Please keep the following in mind:

  • This is a big book (500+ pages with lots of graphics) and it can take a minute or more to display in Scribd. In addition, Scribd’s iPaper viewer doesn’t render the PDF file very well. Consider downloading it (also free) for easier reading.
  • The first two parts explain the technical tasks required to install the software and prepare the publishing environment. After¬†reading the introduction, consider skipping to Part III, “Writing and Publishing with Joomla,” or skim the table of contents, to get an idea of the writing and publishing tasks you can perform with it.
  • I wrote and edited it as a side project (I’m a tech writer in my day job). I don’t claim to be the best writer in town, but I did my best to proof it for errors. Don’t beat me up too much if you encounter a few typos ūüôā¬†
  • The current version explains how to use Joomla 1.5. However, not long after publishing it, the Joomla development team released version 1.6. There is one substantial difference between the two versions, which I explain before the introduction.

If nothing else, I hope this book gives you food for thought on using Joomla as a writing and publishing platform.

Comments

  1. Profile photo of Matt Majeske
    Matt Majeske Post author

    Sure, I’d be happy to. This¬†was a Joomla-based intranet site I built for a technical documentation team. We wrote and published technical manuals on the site.

    Our product implementation team, which performed software installations for our customers (necessary because of our complex, multi-server systems), and support teams were the primary audience. But, it was accessible to the entire product development organization. Our QA department used the manuals when setting up their testing environments, and developers often referred to the manuals when building development environments.

  2. Profile photo of Matt Majeske
    Matt Majeske Post author

    Sure, I’d be happy to. This¬†was a Joomla-based intranet site I built for a technical documentation team. We wrote and published technical manuals on the site.

    Our product implementation team, which performed software installations for our customers (necessary because of our complex, multi-server systems), and support teams were the primary audience. But, it was accessible to the entire product development organization. Our QA department used the manuals when setting up their testing environments, and developers often referred to the manuals when building development environments.

Your email address will not be published. Required fields are marked *