Parag R's blog

On Tuesday (April 17), I continued to work on my EPUB version of my document. I tested it on Sigil, and it came up with a few text errors that were quite easy to fix. When I tried to reverify it, more errors popped up regarding my table of contents. I figured out it was because when I exported my file, I used the wrong table of contents format. So I re-exported the file, and re-fixed the text errors, and finally, the “No Problems Found!” message appeared. I looked at my document on the ipad, and it looks good for the most part.

This week, I missed class on Tuesday because I had to present at the Creative Inquiry Poster Symposium. So on Thursday, I got assigned my document that needs to be converted into an eBook. I went through the steps to format it correctly in InDesign, including putting in a title picture and making sure all image and tables were properly inserted. I also exported the file to ePub but that's all I got to today. Next week I will work on testing and validating it.

On Tuesday, I finished up the final version of the Collaborative Documentation Project by putting the HTML version into the dropbox folder. I also sent in the peer evaluation document by emailing it to Dr. Blakesley.

This week, we conducted user-tests. On Tuesday, Devin and I got together with Ben and Courtney. We traded off testing the document for each other and provided suggestions for improvement. While one group sat and tested the document silently, the creators of the document watched the users to see if there were any parts where the users seemed confused. Afterwards, we all talked changes that would help the documents be more easily used. For our project, we had to make a few changes. I misused the word "tab" and replaced it with "toolbar," and then made a few grammatical changes.

This week, I finalized my part of the Collaborative Documentation Project and put it together with Devin's part. My part was basically writing the steps for using the Style ribbon on Microsoft Word. After looking on the internet, I found some helpful sites that helped me understand exactly what the Style ribbon was before actually writing about it. I also added the images/screenshots into the document. Today in class, I worked on converting our word document into HTML. This was harder than I thought it would be because the formatting kept getting messed up.

On Tuesday, March 6th, Devin and I split up the areas needed to be covered in our document. Devin has the first two points, I have the second two points, and the last few are split amongst us as we sit fit while writing our sections.

On Tuesday, February 28, 2012, we got assigned the Collaborative Documentation project. I worked with my partner, Devin, and we decided on our topic: working with document styles and fonts.

On Tuesday, February 21, 2012, Michael and I put the finishing touches on our technical editing project and submitted the documents via drop box. In class, I worked on the submission notes for the technical editing project. In order to complete the questions, I looked back on the documents I edited for this project and it was interesting to see the types of edits and the challenges faced during the editing process.

1. What was the most challenging aspect of your work on this project?
The most challenging aspect overall on this project was being concise. I have a lot of information on my resume, and it was very difficult to format all three versions of my resume so that they didn't look overloaded, but at the same time consisted of pertinent information for the purpose of the resume itself.

1. Usernames of Editors (including yours): Parag R & mbwoote

2. Author and Title of KB Journal article edited: Divination and Mysticism as Rhetoric in the Choral Space by Grace Veach

3. Chapter or Section Edited in Richardson Manuscript: Chapter 4-Nothing but the effects of those instances of saying