One planning task that is commonly overlooked is defining a folder structure for a project prior to development kickoff. If a structure isn't initially set up and defined, it can grow organically based on individual decisions by team members. The most likely outcome of such actions is an inconsistent folder hierarchy, which can result in a disorganized project. With a good upfront structure in place, developers can follow a defined pattern, creating organization and removing any doubt of where a project's assets should reside.
For WorkflowLab, the structure includes specified areas for images, configuration files, CSS, code package structure, built-in workflows, and static XML files such as the Adobe and custom tools XML files (see Figure 1).
Figure 1 WorkflowLab's project structure.