Difference between revisions of "News Editors"
m (→TEI-L: adding an 'r' to wide) |
m (→Checking Your Article on the TEI Website) |
||
| (11 intermediate revisions by 3 users not shown) | |||
| Line 6: | Line 6: | ||
Looking at the TEI [http://www.tei-c.org/News/ News] page will give you a good idea of the kinds of items to post. Basically, we want to post ''all'' formal announcements that go out to the TEI community, normally via the TEI-L list, related to activities of the TEI Consortium (Members Meetings, Guidelines and tools releases, calls for papers, Access TEI, and so on). In addition, we want to publish a reasonable ''selection'' of other TEI-related news. See [[News_Editors#Selecting_a_Category|Selecting a Category]] for more examples. | Looking at the TEI [http://www.tei-c.org/News/ News] page will give you a good idea of the kinds of items to post. Basically, we want to post ''all'' formal announcements that go out to the TEI community, normally via the TEI-L list, related to activities of the TEI Consortium (Members Meetings, Guidelines and tools releases, calls for papers, Access TEI, and so on). In addition, we want to publish a reasonable ''selection'' of other TEI-related news. See [[News_Editors#Selecting_a_Category|Selecting a Category]] for more examples. | ||
| − | We want a regular flow of news items but not a deluge. A reasonable target would be an article or two per day on average. | + | We want a regular flow of news items but not a deluge. A reasonable target would be an article or two in total added to the news feed per day on average. |
= Sources for Articles = | = Sources for Articles = | ||
== TEI-L == | == TEI-L == | ||
| − | This is the major source. Monitor TEI-L for formal announcements. As these are intended to be shared with the wider TEI community and they are stored in open archives of TEI-L, it is appropriate to repost them with proper credit to the author. | + | This is the major source. Monitor [[TEI-L]] for formal announcements. As these are intended to be shared with the wider TEI community and they are stored in open archives of TEI-L, it is appropriate to repost them with proper credit to the author. |
== Other TEI email lists == | == Other TEI email lists == | ||
| Line 19: | Line 19: | ||
== Other Sources == | == Other Sources == | ||
| − | + | There are any number of other sources that might contain news postings of interest to the TEI community. Other mailing lists like Humanist, Digital Medievalist, or Digital Classicist are one possible source. Press releases from standards bodies like the W3C are another possible source. Interesting news posts on related blogs might also be appropriate if relevant. | |
| + | <!-- Need to update with links to all these things. --> | ||
= How to Post an Article = | = How to Post an Article = | ||
| − | == Check for Originality == | + | == Check for Originality and Relevance == |
| − | Before doing anything, make sure the item hasn't already been posted to the WordPress blog. | + | Before doing anything, make sure the item hasn't already been posted to the WordPress blog. Also attempt to ensure that the item's content is likely to be of interest to a large segment of the TEI community. Obviously anything on TEI-related matters is acceptable, as is interesting news concerning markup or related standards or software. While TEI-L doesn't have a policy against commercial postings (e.g. notifications of new releases of the oXygen XML editor are welcomed) the News Feed should not become saturated with advertising. |
== Claiming == | == Claiming == | ||
Before starting to post an article, you should "claim" it if it is from one of these sources: | Before starting to post an article, you should "claim" it if it is from one of these sources: | ||
| − | + | * TEI-L | |
| − | + | * email to news@tei-c.org | |
Claim it by sending a brief note to the news alias (news@tei-c.org) to say "I will post this item". Please claim an article only if you intend to post it right away; one reason for having multiple news volunteers is to get items online as soon as possible. | Claim it by sending a brief note to the news alias (news@tei-c.org) to say "I will post this item". Please claim an article only if you intend to post it right away; one reason for having multiple news volunteers is to get items online as soon as possible. | ||
| Line 47: | Line 48: | ||
### ''from text:'' Line breaks in your source text will be preserved in the WordPress article, so if possible pre-format the text of your post by consolidating each paragraph into a single line. (If you're good with an editor like vi or Emacs you'll probably find they are good tools for doing this quickly.) Then either use the WYSIWYG icons to add formatting and links, or go into HTML mode to tag them as code. | ### ''from text:'' Line breaks in your source text will be preserved in the WordPress article, so if possible pre-format the text of your post by consolidating each paragraph into a single line. (If you're good with an editor like vi or Emacs you'll probably find they are good tools for doing this quickly.) Then either use the WYSIWYG icons to add formatting and links, or go into HTML mode to tag them as code. | ||
## '''Composing from scratch''': in Visual mode, typing a carriage return starts a new paragraph. In HTML mode, put a blank line between paragraphs (no need to use the <p> tag). | ## '''Composing from scratch''': in Visual mode, typing a carriage return starts a new paragraph. In HTML mode, put a blank line between paragraphs (no need to use the <p> tag). | ||
| + | |||
| + | In both cases checking the visual editor's rendering of the article is probably a good idea. If the resulting HTML is not well-formed, proper nesting, things like & and < escaped correctly if necessary. | ||
| + | |||
| + | You may include images, as long as you upload them using the 'Visual' editor. | ||
== Check Links == | == Check Links == | ||
| Line 62: | Line 67: | ||
== Selecting a Category == | == Selecting a Category == | ||
| − | The one additional thing you | + | The one additional thing you _must_ do before publishing the post is to select a category. The category names are used to divide the News sidebar on www.tei-c.org into '''TEI-C News''' versus '''Other News'''. |
| − | * Select category '''News'' for TEI Consortium news. This would be anything officially related to the activities of the TEI Consortium: announcements about the Member's Meeting, the ''Journal of the TEI'', calls for nominations to Council or Board, announcements related to the Guidelines, Access TEI, the SIGs, TEI tools like Sebastian Rahtz's stylesheets, etc. As a rule of thumb, if it's connected with something you can find listed under the top menu selections on the TEI website, it's "Consortium news". | + | * Select category '''News''' for TEI Consortium news. This would be anything officially related to the activities of the TEI Consortium: announcements about the Member's Meeting, the ''Journal of the TEI'', calls for nominations to Council or Board, announcements related to the Guidelines, Access TEI, the SIGs, TEI tools like Sebastian Rahtz's stylesheets, etc. As a rule of thumb, if it's connected with something you can find listed under the top menu selections on the TEI website, it's "Consortium news". |
* Select category '''Other''' for any other TEI-related items: conferences like Balisage or Digital Humanities, workshop announcements, new projects that use TEI, standards related to TEI (EPUB, XML in general, etc.), tools like oXygen. If in doubt about category, choose "Other". | * Select category '''Other''' for any other TEI-related items: conferences like Balisage or Digital Humanities, workshop announcements, new projects that use TEI, standards related to TEI (EPUB, XML in general, etc.), tools like oXygen. If in doubt about category, choose "Other". | ||
| + | |||
| + | If you don't put it in one of these categories it will '''not''' appear on the list of news headlines on the TEI-C front page. | ||
Click the '''Publish''' button to publish your article to the blog. | Click the '''Publish''' button to publish your article to the blog. | ||
| Line 76: | Line 83: | ||
Articles from the SourceForge blog are dynamically pulled onto the TEI website every 15 minutes. So don't panic if you don't see yours right away! But within 15 minutes, you should see its title on the home page news sidebar, and see the article itself on the [http://www.tei-c.org/News/ News] page. | Articles from the SourceForge blog are dynamically pulled onto the TEI website every 15 minutes. So don't panic if you don't see yours right away! But within 15 minutes, you should see its title on the home page news sidebar, and see the article itself on the [http://www.tei-c.org/News/ News] page. | ||
| + | |||
| + | There are several tests employed in checking the news articles they are: | ||
| + | |||
| + | * Is the Atom feed identical to the existing one? | ||
| + | * Is the Atom feed not well-formed XML? | ||
| + | * Does it at least have one Atom <entry> in it? | ||
| + | * Is the generated news headlines or news body well-formed XHTML? | ||
| + | |||
| + | The last of these is potentially a problem. Ensure in your writing setup (Setup -> Writing) that "WordPress should correct invalidly nested XHTML automatically" is checked. Though this may only take effect in the 'visual' editor. If your post is successfully published on the Sourceforge blog, but doesn't appear on the TEI-C website, even when you refresh your browser, after 30 minutes, email the news@tei-c.org account and alert people that there might be a problem with this article. | ||
| + | |||
| + | Another possible problem is that a single non-well-formed section might get dropped from the article. In this case edit it, possibly in the visual editor, to try and make this section well-formed. | ||
| + | |||
| + | == Twitter == | ||
| + | |||
| + | The articles that appear in the sourceforge feed are eventually posted to http://twitter.com/TEIconsortium | ||
= List of News Editors = | = List of News Editors = | ||
Latest revision as of 19:46, 23 August 2010
TEI news editors are volunteers from the TEI community who post news items to our SourceForge WordPress blog. From there they generate Atom XML feeds that are pulled into the news sidebar on the TEI website home page, and the TEI News page.
This page documents the procedures for news editors to follow.
Contents
Criteria for Article Selection
Looking at the TEI News page will give you a good idea of the kinds of items to post. Basically, we want to post all formal announcements that go out to the TEI community, normally via the TEI-L list, related to activities of the TEI Consortium (Members Meetings, Guidelines and tools releases, calls for papers, Access TEI, and so on). In addition, we want to publish a reasonable selection of other TEI-related news. See Selecting a Category for more examples.
We want a regular flow of news items but not a deluge. A reasonable target would be an article or two in total added to the news feed per day on average.
Sources for Articles
TEI-L
This is the major source. Monitor TEI-L for formal announcements. As these are intended to be shared with the wider TEI community and they are stored in open archives of TEI-L, it is appropriate to repost them with proper credit to the author.
Other TEI email lists
Items posted to the TEI SIG lists, for example, if not duplicated on TEI-L and intended for general distribution, may be appropriate news items.
Emailed Submissions
Individuals may email items they would like posted to our email address, news@tei-c.org. If they seem appropriate they may be posted, with light editing for style if necessary.
Other Sources
There are any number of other sources that might contain news postings of interest to the TEI community. Other mailing lists like Humanist, Digital Medievalist, or Digital Classicist are one possible source. Press releases from standards bodies like the W3C are another possible source. Interesting news posts on related blogs might also be appropriate if relevant.
How to Post an Article
Check for Originality and Relevance
Before doing anything, make sure the item hasn't already been posted to the WordPress blog. Also attempt to ensure that the item's content is likely to be of interest to a large segment of the TEI community. Obviously anything on TEI-related matters is acceptable, as is interesting news concerning markup or related standards or software. While TEI-L doesn't have a policy against commercial postings (e.g. notifications of new releases of the oXygen XML editor are welcomed) the News Feed should not become saturated with advertising.
Claiming
Before starting to post an article, you should "claim" it if it is from one of these sources:
- TEI-L
- email to news@tei-c.org
Claim it by sending a brief note to the news alias (news@tei-c.org) to say "I will post this item". Please claim an article only if you intend to post it right away; one reason for having multiple news volunteers is to get items online as soon as possible.
For items from other sources, claiming is optional; but for sources you suspect other news editors read (HUMANIST or W3C announcements, for example), it wouldn't hurt, as it will prevent duplication of effort.
Composing
Before you first post a live article, go through the following steps with a couple of test items but stop short just before the "Publish" stage, to practice using the WordPress interface.
- Go to the TEI Sourceforge WordPress blog and log in (link at top of page) with your Sourceforge ID.
- In the right-hand sidebar under "Meta", click "Site Admin"
- In the left-hand sidebar under "Posts", click "Add New". This should put you into the "Add New Post" page, with your cursor in the title line for the post.
- Add a brief descriptive title for your post. Past articles on the WordPress blog will give you a sense of appropriate length and content.
- From this point, how you proceed will depend on whether you are composing an article from scratch or copying and pasting, and whether you prefer to work in WYSIWYG or raw HTML mode.
- Copying and pasting
- from HTML: Click on the HTML tab at the top of the editing window. You can probably just copy your source HTML and paste directly into WordPress successfully, but as WordPress won't necessarily render 100% of HTML as your source did, check the entry in the Visual tab.
- from text: Line breaks in your source text will be preserved in the WordPress article, so if possible pre-format the text of your post by consolidating each paragraph into a single line. (If you're good with an editor like vi or Emacs you'll probably find they are good tools for doing this quickly.) Then either use the WYSIWYG icons to add formatting and links, or go into HTML mode to tag them as code.
- Composing from scratch: in Visual mode, typing a carriage return starts a new paragraph. In HTML mode, put a blank line between paragraphs (no need to use the <p> tag).
- Copying and pasting
In both cases checking the visual editor's rendering of the article is probably a good idea. If the resulting HTML is not well-formed, proper nesting, things like & and < escaped correctly if necessary.
You may include images, as long as you upload them using the 'Visual' editor.
Check Links
Especially if you copy-and-paste from HTML (for example, from an HTML version of posts to TEI-L), it's common for the content of an HTML hyperlink (a/@href) to contain errors--typically, extra punctuation in the URL that will make the link fail. Check links by clicking on them or at least mousing over from the Preview page.
Previewing and Saving
Under the top-right "Publish" rubric, clicking the Preview button will show a version of the article as it will appear in WordPress.
Clicking Save Draft allows you to save your work for later editing.
The (Not so) Terrible 'Save Draft'/'Publish' Bug
When you click Save Draft or Publish, you may (will?) get an error page saying Your attempt to edit this post: “[Title of Post]” has failed. If you click on Please try again you see, oh horror, a blank post. Not to worry: click on the "Posts" menu bar just under "Dashboard" in the left-hand column and you will see a list of posts with your saved draft at the top. Mouse over its title to edit. If you tried to publish it but its status has not been changed to "Publish", click the Publish button again.
This is a bug in SourceForge's installation of WordPress as of 19 August 2010, reported months ago but not yet fixed.
Selecting a Category
The one additional thing you _must_ do before publishing the post is to select a category. The category names are used to divide the News sidebar on www.tei-c.org into TEI-C News versus Other News.
- Select category News for TEI Consortium news. This would be anything officially related to the activities of the TEI Consortium: announcements about the Member's Meeting, the Journal of the TEI, calls for nominations to Council or Board, announcements related to the Guidelines, Access TEI, the SIGs, TEI tools like Sebastian Rahtz's stylesheets, etc. As a rule of thumb, if it's connected with something you can find listed under the top menu selections on the TEI website, it's "Consortium news".
- Select category Other for any other TEI-related items: conferences like Balisage or Digital Humanities, workshop announcements, new projects that use TEI, standards related to TEI (EPUB, XML in general, etc.), tools like oXygen. If in doubt about category, choose "Other".
If you don't put it in one of these categories it will not appear on the list of news headlines on the TEI-C front page.
Click the Publish button to publish your article to the blog.
Editing or Deleting a published article
Click on the Posts dashboard button. Mouse over your article title and choose the appropriate action. Note that after you Publish an article you can usually keep it from showing up on the TEI website by deleting it right away (see next section)
Checking Your Article on the TEI Website
Articles from the SourceForge blog are dynamically pulled onto the TEI website every 15 minutes. So don't panic if you don't see yours right away! But within 15 minutes, you should see its title on the home page news sidebar, and see the article itself on the News page.
There are several tests employed in checking the news articles they are:
- Is the Atom feed identical to the existing one?
- Is the Atom feed not well-formed XML?
- Does it at least have one Atom <entry> in it?
- Is the generated news headlines or news body well-formed XHTML?
The last of these is potentially a problem. Ensure in your writing setup (Setup -> Writing) that "WordPress should correct invalidly nested XHTML automatically" is checked. Though this may only take effect in the 'visual' editor. If your post is successfully published on the Sourceforge blog, but doesn't appear on the TEI-C website, even when you refresh your browser, after 30 minutes, email the news@tei-c.org account and alert people that there might be a problem with this article.
Another possible problem is that a single non-well-formed section might get dropped from the article. In this case edit it, possibly in the visual editor, to try and make this section well-formed.
The articles that appear in the sourceforge feed are eventually posted to http://twitter.com/TEIconsortium
List of News Editors
