What You'll Be Creating Documenting a project can be a nuisance, but it needn’t be. There are quite a few tools out there to get the job done–I often use Daux.io because of its flexibility. In this article I’ll show you why you should document, how you can get Daux.io and how you can start using it right now to make your projects much better. Why Documentation is Needed Writing documentation for your project could be the single most important decision you make. The reason this is often overlooked for web-based projects is that there isn’t that much at stake. Take a Boeing 787 for example. This product has an extensive body of documentation backing up every aspect from design to maintenance. There’s even a near 150 page manual documenting the 787 characteristics to take into account when planning airports. Why should an airplane have wide reaching documentation whilst a website doesn’t? I believe there are three main reasons: There is a lot more money involved Safety concerns Issues of scale Websites rarely have safety concerns, but as soon as scale or money rears its head you can be sure that documentation will pop up.
↧