To reflect on your experiences working on the RAW website, please write a paper (single-spaced, doesn’t have to be super-formal) that addresses the following:
How would you contextualize/define/explain the work you did (individually, in your small groups, within the whole class structure) within the scholarship of the class (i.e., what we’ve read), within the Publishing sequence program, and to a future internship coordinator or employer? Here are some more distinct questions, to get you started: How did the role you play help/hinder you in completing this project? What did you learn about the process of creating companion websites that relates to the processes of digital publishing as a whole (based on your readings, or our discussions in class)? What did you wish you could do in/for this project that you didn’t get to finish, didn’t know how to do, etc.? What do you think you will take away from this project and be able to apply to your next one (about copy- and design-editing digital media scholarhip) for this class? And, then, to print publishing?
Feel free to address anything else needed. This is a lot to cover; I suspect they’ll be around 3-5 pages ss, but just do a first (readable) draft. I’m more interested in your fleshed out thoughts than in the perfection of how they are presented. Oh, and email these to me when you’re done. They’re due by start of class on the 24th.
Let me know if you have questions.
Hey all, I changed the schedule, adding a week to the RAW project. That means your readings for this week have changed. FYI.
— upload assignments teachers had created
— discussion forum (a way to communicate with other readers; easy to set up but who moderation?
— short author bios: other items published that might be of interest; links to other work they had done (short enough to show credibility).
— something on the home page that takes visual advantage of “new media” (to what extent? and who?)
— coherent theme related to the book design!! (same theme, design, color, etc.)
— no book trailer!!
— limit links to useful/rhetorical ones
— how to accommodate all the modes? maybe each chapter has their own page with bios and media? (possibly like NWC TOC as a visual): we like nonlinear
— link back to home (using a graphic)
— use scenes and transitions (maybe in drop-downs) as the main menu instead of chapters
— keep the menu the same on every page
— copyright info and how to cite this page
— where to purchase the book
— book reviews//class discussions
— description of the book, goals, purpose
— mention of filetypes used
— short summaries of each chapter
— website as separate entity from book (thus no sample chapters) (assume aud already has the book; not for selling the book)
— keep media consistent
- author liaison – ?
- blog/upload expert
- usability expert
- layout editor
- blog designer
- graphic designer
- technical writers
- content manager
- project manager (consistency checker) — timeline maker and keeper
- link/archive editor
QUESTION: Based on the features above and how you believe they might correspond with the roles above, what are your top three choices for roles in developing the RAW website? Comment on this post with your ranked list and include a brief description of what you think each of your roles would cover. Due by 8am next Wednesday. Let me know if you have questions.
(Also, continue to tweet me, or post on the ning, which I’ll open on Sunday or Monday with instructions, questions you have about the readings. I’ll be able to answer in more depth online once we have the ning set up, which will give us more time to work on the project in class.)
As a follow-up homework assignment to your small-group analysis of companion websites to scholarly/academic books, please research the publishing company of your book/website and leave a group comment in response to this post that summarizes the histories, disciplines (thus audiences), economies, and publishing missions/scope (based on key ideas from our readings so far) that can help contextualize why the companion sites were designed or produced with the features (and flaws) you noted from last week’s analyses. These responses should be more formally written than the previous week’s posts and should be approximately 5-6 paragraphs in length. Post one comment for each group. Due 8am next Wednesday.
I thought about
- starting a ning to discuss the readings, but it was too much work for one week and an extra URL,
- embedding a discussion forum into this blog, but none of the plug-ins seemed to work with this version of WordPress
- asking you to tweet your responses, but 140 characters isn’t really enough,
so instead I’m just going to ask you to respond to this post with your questions/comments, etc., about the readings last week and I will respond.
Below is the list of companion websites that you’ll analyze to figure out what features and technological needs and wants we might have for the RAW website. You should create your own criteria for analyzing the site based on needs and wants in relation to the “companion website” genre for these books. We will use these analyses to create a baseline list of features to implement in the RAW website next week in class. From there, we will form groups to take on different aspects of the website project. Post your group response (i.e., one analysis per group of two students) as a comment to this post. Remember that your comments will be live on the Internet and that authors could find your comments by searching their names/book titles, so write the analysis appropriately. Analyses are due by 8am next Wednesday. Make sure to put both your names in the post.
Read the About and Policies pages. Respond to them by putting a Comment to this post. You should discuss your reaction and response to the course goals, projects, what you expected from this class, what you think it’s going to be about, what you value as a student, what you hope to gain from this class, what ideas you might already have for presentation topics, and anything else you find relevant for me to know from the outset.
Your post serves as recognition that you have read and understood the course syllabus (i.e., this blog) and also helps me gauge what you expect from me and this class. This post should be 3-4 paragraphs, and is due by 8am next Wednesday, January 20.
Let me know if you have questions!
This is the class blog. It is the syllabus and may (will) change to accommodate learning styles and needs. The main navigation for the site is in the red menu above. It includes the following:
- HOME: New posts that I make with information, tips, small homework assignments, etc., will be posted here on this “Home” page, as blog posts. You can set up an RSS feed to get these updates in your email or through an RSS Feed Reader. Besides homework, which will be posted during or after class, I may only post 1-2 items here per week. It is your responsibility to keep up with these postings. Sometimes they include last-minute changes to the homework, if I’ve realized an assignment is wonky, a technology isn’t available, etc. You can always get back to the Home page from within this blog by clicking on the course title above or on the Home link in the red navigation menu above.
- ABOUT: This page contains the course description, required texts, and a brief run-down of the major assignments.
- POLICIES: This page contains goals (learning outcomes), expectations and values of student and teacher behavior, and the grading system.
- RESOURCES: This page contains a list of links, handouts, etc., that we may use in class. If you have suggestions for the Resources page, please let me know.
- SCHEDULE: The schedule includes our week-by-week meetings, readings, and homework listings.
If you have questions at any time about how this blog works, please let me know. I’m looking forward to this semester!