An articulated content strategy helps content teams to identify a roadmap to follow.<\/p>\n
Step one: establish ownership and roles<\/h2>\n
Half of Extension faculty and staff can publish content, which is coordinated through content teams or web groups<\/a>.<\/p>\n Use the content overview tool<\/a> to search a content title and see what team or group a piece of content belongs to, and contact the team leader or group coordinator if you see questionable content. Your feedback can help them to see other perspectives and their response inform yours.<\/p>\n Roles and responsibilities<\/a>, outlined earlier in 2019, clarify how people fit into the content development cycle and their relationships to each other.<\/p>\n Among those roles, teams and groups need to discuss who controls the content quality, holding relevant content authors accountable to content guidelines, standards and policies that will be explored in the next steps.<\/p>\n Content may be written by author(s) but it is the content teams and program leaders that need to work together to plan, review, publish, and revise the content. It helps to share a common set of tools and expectations in this content process.<\/p>\n Statewide planning meetings can set the stage for a participatory process. Together you can review audience analytics and determine the content purpose, gaps to fill, and plans for the year. It can also help decide what content isn\u2019t needed based on strategic priorities. Set up a content planning spreadsheet<\/em> in Box to keep track of content to be created.<\/p>\n A peer review checkbox and name field<\/em> appears on all articles if your team wants to use this as part of the publishing process. It currently means at least one other colleague looked at it, but does not mean the same level of scrutiny as catalog and journal peer reviews. Content that is questionable can also be put \u201cin review<\/em>\u201d by the team or group to keep it from public view until the issue addressed.<\/p>\n A team needs to decide if they will independently upload articles, appoint an uploader on the team, or find program\/research assistants or students to support this. These people need to be aware of the guidelines, standards and policies discussed below. An editorial calendar<\/em> can help schedule content to be published at key times.<\/p>\n Many are familiar with the EESC directed process to review and update Extension catalog publications more than four years old. Content team leaders need to coordinate a similar process for their team\u2019s articles and educational documents; EESC can help by setting up automated notifications and maintenance reports<\/em> to use.<\/p>\n Ground rules for doing content right can help to address differences in opinions. EESC has outlined some key recommendations or requirements below. Content teams and groups can adapt and expand on these to establish what makes for \u201cquality\u201d content.<\/p>\n Guidelines that EESC provides and encourage you to use include:<\/p>\n Standards mean there\u2019s a correct way to do things, and an expectation this will be followed, such as:<\/p>\n Since these guidelines and standards can be a lot to learn, EESC will help by reviewing content after it is published and making minor changes or suggestions on how to improve. More information is in the content requirements and best practices<\/a> section of the web guide, or request a specific training.<\/p>\n Policies are critical to follow to be inclusive, ethical, or not put us at risk, this includes things such as:<\/p>\n Information about this is in the legal requirements<\/a> section of our web guide. Also OSU’s Web and Mobile Services is offering “Accessibility Basics for the Web<\/a>” trainings, including information about the OSU Policy on Information Technology Accessibility. Offered Oct. 3, Dec. 5, 2019 and Feb. 7, April 15 or June 4, 2020.<\/p>\n Teams and groups need to keep a pulse on what is going on with their online content and scrutinize not only if it is accurate but also if the overall quality meets our expectations.<\/p>\n Keep those discussions going, work with EESC to set up some shared tools and communicate the guidelines, standards and policies to group members working on the website. Then before you know it, you will have arrived at a functional content strategy.<\/p>\n You can now see all featured questions<\/a> on a single page.<\/p>\n The “seasonal” tagging field now allows multiple options to be selected for a piece of content.<\/p>\n Minor fixes have been made in the display of phone and email on county landing pages.<\/p>\n Collections now have the formatting options: standard teaser (thumbnail image, title, short description), grid format (3 card size images and descriptions next to each other), and plain list without images. After adding a “collection section” see the settings tab.<\/p>\n Thanks to Joseph Phillips, Content Strategist for the Examined Web, for ideas from his article \u201cA four step roadmap to good content governance<\/a>\u201d for this blog post. <\/em><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":" The website brought a lot of content together from all different parts of Extension, created for different purposes, at different times and sometimes published by non-Extension faculty. Everyone has come across an article or two where they wonder \u201cIs this content accurate, useful information for Extension\u2019s audiences?\u201d Content teams, along with the program area leaders,… Continue reading ![\"\"](\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/2760\/files\/2019\/09\/Screen-Shot-2019-09-30-at-4.17.16-PM.png\")
<\/p>\nStep two: design and document content processes<\/h2>\n
Plan<\/h3>\n
Review<\/h3>\n
Publish<\/h3>\n
Revise<\/h3>\n
Step three: produce supporting documents and tools<\/h2>\n
\n
\n
\n
Destination<\/h2>\n
\nExtension website updates<\/strong><\/h2>\n
![\"\"](\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/2760\/files\/2019\/10\/Screen-Shot-2019-10-01-at-8.33.24-AM.png\")
<\/p>\n