For this project, you'll work with three or more peers on an extended book project using either the DPS or Atlas platforms. The project will involve the development, production, and publication of content across a variety of book-related media. You'll be asked to use Creative Cloud tools and spaces to manage the content of your project (e.g., share files, progress notes, and so on). Throughout the semester, you'll be asked to present progress reports in class. Some components of the project may involve field work or attendance at special events on campus. At least one group will work with Atlas and be led by a graduate student. The other groups will work with Adobe DPS as the publishing platform. (25% of course grade.)
We'll break up into five teams, each with its unique responsibilities, to be decided by the group. Throughout the process, everyone will share in assembling assets for the DPS App or Atlas book. Students will be able to choose which project teams to join at the start of the project, and everyone is expected to contribute equally and consistently throughout all stages of the App or book development.
Weekly Project Log: Each week (by Friday at midnight), your project team should post a project log in which you identify what you've accomplished thus far, set goals and milestones, and report on discussions with other project teams. Only the team needs to post a project log (not each member of the team). (Tags: project log, team name, and any others you'd like.)
Identify Your Deliverables: because of the nature of this project, each team should determine all of its deliverables at the start of the project and then set deadlines for collecting and preparing them for publication.
The DPS App teams will need to identity at the start all of the books to be included in their App, then collect existing assets (InDesign files, book descriptions) from Dr. Blakesley. The App will include all the Parlor Press books that have been published as open access content, which includes all books in the Reference Guides to Rhetoric and Composition series, the Perspectives on Writing series, and other standalone books with a CC license. One goal will be to have most of the content ready to assemble in early November. Some teams will play more prominent roles in the latter stages of the production process.
The Atlas team will create its contents from existing resources on writing across the curriculum provided by Dr. Blakesley. Some of the content will need to be revised or shaped for publication on the Atlas platform. Some of the content will also be drawn from student blog posts that are relevant and revised for publication. The Atlas team will lead this process of collecting content from peers.
Case Study: One major associated project will be to document the book publishing process, so each team will contribute to a Case Study that will tell the story of this book project from beginning to end in an interesting way to a public audience, involving video, interviews, photographs, and documentation. A separate handout will describe the Cast Study project in detail.
Prototypes of each assembled book project (DPS App or Atlas) will need to be ready for testing during the second week of April.
Your collaborative project is worth 25% of your course grade. Your work will be evaluated for the quality of the deliverables, your contribution to the team effort, whether you met all milestones in a timely way, and the consistency of your engagement with the project over the course of the semester. You will need to complete all the steps in the process to earn credit for the project, including presentation of the book at the end of the semester. It won't be possible to complete the collaborative book project successfully if you don't work at it regularly, meet all (self-imposed) deadlines, and create high quality deliverables on time. Each team member will be required to submit independently a collaborative project evaluation form.