The editorial team has collected the top four posts from each of our peers, and we have shared the Google Sheet containing those responses with Dr. Blakesley. We have color-coded edited blog posts by editor (green for Jack, purple for Kellie, and blue for Kara) to make it easier to check for consistency and to show which posts still need editing. As of now, we have edited 32 of 44 posts.
Tonight we divided our peers' submissions to determine who will edit which posts. We will look for overall trends, ensure consistency, read for comprehension, check links, and evaluate pictures and screen captures. We plan to have the posts edited for next week.
The project has changed formats from a print publication to a website/blog. For this week, we needed to discuss what the dev team’s new role will be now that this new format has been selected. As we see it, the following responsibilities will be maintained by the dev team:
1) We will continue to consider and suggest new topics for discussion and challenges
2) To continue to develop the different focus areas for all site content
3) To continue to liaise with Dr. Blakesley to solidify the new direction of the project and create a game plan for execution.
As we will be producing content for the web (initially, at least), a few things will change for the editorial team.
First, it will be easier to work with links (which we'll still need to ensure aren't broken), images, and notes.
Narrowing topics/making section names
Production of the Book (InDesign articles, Time Savers, Quality Enhancers)
Challenge on considering where the book will end up (what kind of paper, color, dimensions, platforms)
Launching the Book/Sharing Your Work (Marketing/Promotion)
Need more challenges (pricing)
This week we did some research on potential copyright issues raised by the use of screenshots in our book. We didn't find anything concrete pointing to whether this is something to avoid. Some resources said that the use of screenshots does constitute copyright infringement but that most companies/organizations don't pursue any legal action (in part because it isn't worth the cost and in part because it doesn't make sense to sue someone for promoting your product for free).
Audience: Authors who are composing and trying to publish, and other publishers
Following format of Pogue’s Basics
Potential content areas: Social Networks, Publishing Platforms (iBookstore, Smashwords, CreateSpace), “Softwares for Composition” or some name that includes InDesign/Photoshop/Premiere/Animatron/Animoto tips, Crisis Management
1 or 2 challenges for each area
Proposed Marketing Strategy:
Three weeks before the Collaborative Book is to be “published,” our group will initiate its marketing strategy. Our marketing strategy will be predominantly on social media platforms, include some or part of the following:
- Video Promo
- Post/Publish on different feeds –
- English department blog
- MAPC facebook page
- Blog about the process of writing the book?
- Pinterest boards and pins J
The editorial team has settled on a modified Chicago style of editing for the book. We have selected a method of listing notes (rather than using footnotes and/or endnotes) and handling citation styles. We have it on our radar that some people may have varied their audiences when writing posts, so we will need to review posts for audience consistency. We deliberated whether we should set a tip number limit for posts/topics, but we haven't come to a conclusion on this yet.
- Social Media Strategies
- Platforms: Facebook, Twitter, Blog, Instagram? Choose 2-3
- What accounts are we using? Do we need to create accounts or can we use existing accounts like English, MAPC, etc.
- Picmonkey for making some posts?
- Possible sources to inform our practices:
- Herding cats: a strategic approach to social media marketing by Andrew Rohm and Michael Weiss
- Still searching for more sources
- Create timeline for when we’ll start posting and what we’ll post
- When should we start?