Best option for sharing projects?

Dec 22, 2011

Hi. in short we are trying to work out a plan of action for projects to be taken over by others, especially in the lovely so-called 'hit by a bus' scenario. So in the case that something happens to one of our elearning designers, another designer can jump in and take over a project from their own computer without having to be up to speed with all the design details of the project.

We were hoping that the Articulate Package option would be the best solution to this scenario. However, on further investigation it seems that packaging a project does not includes all the elements of the project - while a package includes inserted media like flash, it does not include things like:

  • custom skins
  • custom fonts 
  • and custom language, for example  

So at this stage it looks like we are going to have to develop a comprehensive form of some kind that has to be completed by the elearning designer during a project, one that lists all the details of the project – not ideal. That way another individual can pick up a project from their own computer without having to worry about custom elements etc. 

However, it would be great if a designer could just pick up a project and jump in without having to worry about all this. Is the package the only option, are there any other options/suggestions or are we packaging projects incorrectly?

thanks

Gav

4 Replies
Melanie Sobie

Does your team have a shared network drive? If so, you could create a "Resources" folder, with sub-folders for "Fonts", "Skins", "Images", etc. Then each time a team member creates a new custom element or installs a new font, they just put a second copy in the applicable Resources folder so it is available to others if needed.

Where I work there are only two full time instructional designers.  However, we have a shared network "Projects" folder for each module we are working on that contains all the original source materials, project plan, images, videos, etc.. Only the PPT, PPTA, engage interactions, quizmaker files are kept on the c:drive, and then we create a zip package periodically throughout development with the date and put the zip file in the applicable project folder in the network project folder for backup purposes should anyone need it in an emergency, and also in case the computer's hard drive fails.

I'd be interested in what others have done to ensure shared access to project files, etc.

This discussion is closed. You can start a new discussion or contact Articulate Support.