Skip to content →

WRIT 3152 Week Eleven: Content team rosters, roles, and resources

As announced, I launched content teams yesterday on Discord!

I’ll use this post to collect those resources and some extra ones as content teams begin setting their first meetings. First some links, which I’ll also share into the #important-documents channel:

Rosters and roles for content teams

Resource folder for content teams
(including story formatting guidelines)

Everyone should make themselves familiar with what’s in these folders: one document that explains the layout guidelines for a story along with a suggested flow of events/meetings and another one that is our “style sheet” so that writers and editors have a common understanding of tone and mechanics in the writing.

Here are a couple things for each role on the team to remember:

  • Project Managers: When you meet with your team, figure out two weekly times for meetings that work for everyone in the group. Consider mornings and evenings. Space your two meetings apart by a couple of days. Knowing when people are free will make scheduling future meetings much easier.
  • Researchers: The team is depending on you for two things — good ideas in research briefs and being on top of news about the General Assembly. You should regularly be reading AJC stories, listening to some Politically Georgia (daily) or Gold Dome Scramble (weekly) podcasts, watching #gapol for good digital stakeholders, and researching for academic articles (KSU library database) that are useful for stories.
  • Content Devs: You can do some/all of the “in the background” research that the Researcher is doing (mentioned above). More than anything, it will be important for you to clear a 48 hour window after the first meeting in every story cycle so that you can spend 2-4 hours writing your story. You will often have to look up new sources to keep up with where the story goes or how it changes.
  • Designer/Editor: It’s your job to find a good picture, to lay out the post, to come up with a good title, and to lay out the post with the right kinds of artifact formats (embedded media or pull quotes). You need to be very familiar with the Style Guide (see the resource folder link above). You should communicate with the Content Dev whether you want the story delivered to you in a Word Doc or in a WordPress post; everyone on the team should be able to look at the story while you’re editing it. Your editing time should be as quick as possible. Fix what you easily can yourself; only send it back to the Content Dev if the story needs significant revision or several new sources.

I’ve corrected some mistakes/changes from the Week Ten post, but here is . . .

Our schedule for next week:

  • Between now and Monday 3/25: PMs organize the first team meeting (please see my document in the source folder on what to address if your first meeting of a story cycle). All team members bring their research brief to discuss during that meeting (research brief is outlined in the Week Ten post).
  • Class, Monday, 3/25: Attendance is optional; Pete and MEs will meet during class (our regular room, 3:30-4:30); teams or team members are free meet with us and send questions to us via #help since we will all be there together.
  • By Tuesday, 3/26: PMs should communicate what bill/issue will be focus of their teams’ story this week in the “Cycle One” thread of the #claiming-story-topics channel. Be sure that you’re not choosing the same idea as another team.
  • Between Tuesday, 3/26, and Friday, 3/29: PMs organize the second team meeting to discuss where they are with the story. While Content Dev and Editor are involved in completing the story, PM and Researcher are engaged in discussions about possible ideas for the next story; Researcher will need to have two research briefs developed by the first meeting of the next cycle.
  • Class, Wednesday, 3/27: No class meeting; Pete is out of town.
  • Friday, 3/29: Finished draft of story is due for Pete/ME review in WordPress with “REVIEW:” in the title. All team members must confirm in a message on their channel that they have submitted and that they have read the draft (include an @ to me in that message).

Published in writ3152

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php