Archiving

When work is complete on any project it is archived for future reference. So be sure to have access privileges to the shared folder Archive before you commence work.

Archiving is achieved predominantly on a per task basis. When you're ready to move onto the next task, archive your workfiles of the previous task in the Archive folder.

Folder name

Each archive needs to be named with certain keywords, so it can be discoverable in more than one ways...

This is the recipe for the folder name

[(I/S/M/V/G)YYMMDD-{{suffix}}] {{PROJECT NAME}} - {{TASK}}

Analysing on the different parts:

• ID:...
• Title:...

Ultimately what you're looking at is something like this

[I140512-19356679208] Havenbase - Dashboard UI

To aid in the creation of the ID you may use this web tool:

http://code.kdi.co/tools/taskid/

Archive structure

The structure of any achieved task folder should be consistent, so discovery at a future date is reasonably possible.

An archive folder of a task may contain the following sub-folders:

|- administration
|- development
|- production
|- promotion
|- research
|- resources

Not all of the folders are necessary for every task so just use the ones that are relevant to your task. Here is an explanation of what each folder may contain:

• administration: ...

The structure in each one of these folders is more fluid and left at the developer's best judgement. There are additional conventions you must be aware of.

Other conventions

• Outdated work files are not deleted, rather placed in a history folder under development/_old