development team

Development Team Wrap-Up

Submitted by YKK on Sat, 04/30/2016 - 03:52

I think we all agreed that with the creation of the PubHackers website, we would leave off with our challenge recommendations. In particular, we would have liked to have seen the one about 'What to do in a crisis' (for authors, publishers, and self-publishers) get done, but perhaps that can be a topic that others address in the future.

3/31/16 Development Team Project Log

Submitted by kms on Thu, 03/31/2016 - 22:20

Stylesheet to reference when revising your four articles:

Approximate image sizes for articles in "Chirp" theme:  344 x 227 pixels (So try to ensure that your image has these approximate dimensions.)

Maximum of two images per post, each captioned

At least one screen shot

Length of article:  approx. 150-250 words (if it's longer than than, you can split your article into multiple topics)

Chicago Style

Include tags

 

4 Potential Topic Areas:

Dev Team Project Log 3/24/2016

Submitted by jared on Thu, 03/24/2016 - 22:59

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.

Development Team Project Log: 3/3/16

Submitted by kms on Fri, 03/04/2016 - 00:47

3/3/16

  • 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)

Development Team: 2/18 Project Log

Submitted by kms on Fri, 02/19/2016 - 00:38

2/18/16

  • 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

Development Team: Week of 2/11/16- 2/18/16 Project Log

Submitted by kms on Thu, 02/18/2016 - 22:04

(2/11/16) Team Meeting – things we talked about, things to think about

  • In charge of content, design, and techne challenges

  • Audience is for self-publishers (think publishers and authors) or start publishing companies – ask him to clarify the audience

  • Research what the audience needs

  • Formatting is for the design team

  • We pick which ones go in it