API Network Corp

But we have a thick folder full of documentation. So what's the problem?

The problem is that you do not need lots of pages in multiple 3 ring binders — you need good, usable, and easy to access/searchable documentation.  Documentation written in the first stages of design and development is useful for that strict stage — it brings a clear understanding of what is going to be built.   It's for the builders.   When the system is in place, the importance of these documents dramatically fades away.   It now becomes very important to know how the system is developed and why that specific course of action has been taken.      The builders are gone, the maintainers remain.

Software reliability

The non-IT person's conception of a software product (Joomla or any other CMS) is very simple: once the software can run correctly, it will do it forever.  The initial logic the system was built upon, if determined to be correct today, it will invariably be correct tomorrow. Even if a physical presence that powers your system, software never ages or erodes.

Here are some details that one should consider before adopting such an optimistic view:

The logic of the system may be unmistakable, but the hardware on which it runs may encounter real problems. These will draw the necessity to intimately master the functionality and requirements of the software too.  Systems can and will become obsolete. The need for additions or improvements turns into periodic concerns. Some simple changes in some lines of codes can bring about disasters if the system internal relationships are not clearly documented and known.

Do We Really Need Documentation?

Sooner or later, every company that develops in-house software, whether it's a Joomla website or Joomla extensions, will reach a point where discussions about IP (intellectual property) documentation will be ignited.   In case the IT department of such a company will lack consistent and real IT leadership, well-versed in the field of software design, development and especially management, the discussions will end up going nowhere.

Without documentation, there are good chances that the software will have a similar fate.

We had been offline for a good month, but we're back as of today.    If you are a Joomla webmaster, we believe every site you build should include a copy of Dingo task manager.   Why?   Because every Joomla website, regardless of complexity, has a list of things that need doing,  usually by different people.   That's exactly why we created Dingo, because we know first-hand, tasks need to be listed, prioritized, assigned and made visible else you should plan to run into some serious delivery speedbumps.     Try the Dingo Demo or read more about why you would want Dingo in your business.