Changes

Jump to navigation Jump to search
1,786 bytes added ,  13:41, 21 June 2017
This page is useful to those [[Writing Blog Posts]] at the McNair Center.
<onlyinclude>We have a step-by-step McNair Staff are expected to follow the [[Blog Writing Process]] that we expect McNair Staff to follow. Amendments to the process should be done only in consultation with the [[Blog Team]]. This process ensures that everyone creates a page for their blog post using [[Form:BlogPost]] so that everything we do can be efficiently tracked and stored, and so that we can all work together efficiently. Please see See the detailed instructions for [[Blog Writing Process#Creating a wiki page for your blog post| creating a wiki page for your blog post]].</onlyinclude>
==Step by Step==
Please follow the following Follow these stepsas you write your post. Remember to set your content status on your post's wiki page as your enter each stage:#'''Idea''': Before beginning a blog post, blog writers must get preliminary approval from Anne or Ed. To propose a blog post, sketch the idea in 2-3 sentences in a post on the #bloggers Slack Channel. Include links to at least three sources you would draw on to write the post. State the implications for public policy on entrepreneurship, innovation, or public policy in your proposal.#Once your an idea is approved, set up a wiki page for the blog post. Include (Blog Post) in the title and make the wiki page using [[Form:BlogPost]]. Follow the technical instructions Describe your idea in the section below carefully2-4 sentences. Include the 3-4 proposed references. Alert Anne and Ed to your proposalonce your Idea page is complete. #'''Outline''': Once your post idea is approved. Conduct further research and outline your proposed post on your wiki page. Include your proposed argument or thesis statement, 5-6 supporting points and references. Each supporting point must be back by evidence. References should be included for all sourcesof the supporting points. Let Anne know when you have finished your outline.#'''Draft''': Once your outline is approved, an editable draft your post. Include a link to the google doc, on your blog post's wiki page. Make sure that this link can be viewed by all rice.edu email addresses and can be edited by Anne. Use the [[Writing and any Style Rules]] to make sure your writing is consistent with other relevant informationMcNair Center posts.# Drafts are due one week after your idea '''Peer edit''': This step is approvedskipped during the summer. Once the draft is ready for review, tell Anne. She will assign you a peer editor. He Make sure that your peer reviewer's name is in the '''Notes''' field in [[Form:BlogPost]] and he or she will make suggestions and return the blog post has permission to the writeredit your google doc. The writer will revise the #'''Revision''': Revise your draft based on these the peer editor's suggestions#. Give the revised draft to Anne, who may require further revisions. If substantial revisions are required at this stage, the post may go through another round of peer review. completing the same process of suggestion and revision as with the peer editor in Step 1. If any large changes are made in this process, the writer will give the new draft to another available peer editor to check for grammar/content one last time before giving it to Ed. Put whether your post is waiting for or approved by Anne and Ed in the '''Notes''' field. This process may have to be repeated more than once if the blog needs further development.#Give the final draft Anne for approval. #'''In Wordpress''': Once Anne’s approval is given, the piece can be posted in the blog using Steps 5-6. See [[Working with Wordpress]] for detailed instructions. #'''Simultaneously with Steps 1-3:''' Select two or more graphics for the blog post (one as featured image, one for within the post itself), making sure that we are authorized to use the image and that we have the proper citations. Write a caption for the graphic. Give all of this to the Graphics Editor for approval.
#Once the graphics and content have been approved, the writer can post it all into WordPress. The writer needs to make the page visually appealing and set up the WordPress features- Use our [[Working with WordPress]] page for help (SEO, Readability, Tags, Hyperlinks). At this point, the blog post will be ready for publication, but should be labeled as a Visibility: "Private" within WordPress (not public yet).
#Notify During the academic year, notify the Online Editor (see our [[Blog Team]] page for details) that the post is completely ready to be published. The Online Editor checks that the post is at the quality we expect for publishing, looking at graphics, plugins, content, title, etc. The Online Editor can then publish it to the public in WordPressand set the status to '''Published'''.
===Due Dates and Expectations===
A During the academic year, a draft of a post will be expected for peer editing no later than one week after the idea is approved. Peer editors must complete their editing within one shift of being assigned to a post. Then the post should go to Anne. After Anne’s edits are received, a new draft is expected one shift later. Tighter timelines may be specified depending on circumstances.
===Assorted Things to Remember===
==Creating a wiki page for your blog post==
Use this page in conjunction with the [[Form:BlogPost]] to create your blog post's wiki page. This is mandatory. Using the form will create a template and make sure that your r blog post is tracked on the [[Writing Blog Posts]] page, as well as the [[All McNair blog posts]] page.
===Structuring your Wiki Page===
Check you page shows up by going to [[All McNair blog posts]]. If you can't see it there, do a NULL EDIT (i.e., edit and save the page without doing anything), and check again.
==Converting an existing wiki page to a blog post page== If you have a pre-existing wiki page that you need to convert to a blog post page you need to do the following: ===Remove an category tags, etc=== Remove any category assignments. They look like <nowiki>[[category:some category]]<nowiki>. Links to categories, which do not assign a page to a category, can stay. Category link tags look like <nowiki>[[:category: some category]]</nowiki>. Also remove any old code that is no longer needed. Examples include:  <nowiki> <includeonly>...</includeonly> <!-- flush --> </nowiki> ===Add and complete the blog post template=== Add a copy of [[Template:BlogPost]] manually to the top of your page. The resulting code should look like:  <nowiki>{{BlogPost|Has title=|Has author=|Part of series=|Has content status=|Has graphics status=|Blog image=|Had publication date=|Has processing notes=}} </nowiki>  ...but with each of the values filled out, as described in the section above. [[Category:McNair Admin]]

Navigation menu