To submit an article idea, provide a headline, abstract, or synopsis of the story you would like to write (along with your full name and contact information). If the document already exists, please still follow this step first.

We cannot commit to a publication schedule without the above, and as a rule we do not have the bandwidth to review whole unsolicited manuscripts. You may submit by e-mailing the editors, or by using the developerWorks submissions database (please include the words "Power Architecture newsletter" in your subject line).

Once your submission has been approved, please follow these writer guidelines:

Article and diagram guidelines

• Format:
  Plain text or XML (we will provide an XML template upon request)
  Office formats may be acceptable, but please ask first.
• Length:
  700-1000 words (or about 3 pages of text, along with at least 2 block diagrams, if appropriate. A good rule of thumb on this is, if you cannot refer to a table or figure from your text, it might not be of great use.)
• Graphics:
  Resolution = 72 dpi. No wider than 600 pixels. JPEGs or GIFs are preferred. developerWorks employs a professional graphics staff, which will most likely be redrawing the graphic to match our style, so legibility is more important than beauty.

Please note: ALL headings, sub-headings, column headings, and so on, including labels used in block diagrams or charts, should use sentence-style capitalization; do not initial-cap headings.

Article focus

Contributed articles to the Power Architecture Community Newsletter should focus on technical know-how around Power Architecture technology-based solutions and products. They should provide the community of engineers and developers with useful information that would allow them to easily use and create Power Architecture technology-based solutions and products.

Author credit
Immediately following the article title, please indicate the name, title, and company of the author(s) you would like to receive credit for writing the article.

Schedule

A due date will be assigned when the submission is accepted. Once the article is submitted, you can expect to receive confirmation of receipt within 48-hours, and an edit cycle for that article within three days. A typical edit cycle may involve:

1. Day 1. Article submitted
2. Day 2. Receipt confirmed
3. Day 4. Edit schedule for this article is sent to author
4. Day 7. Comments for revision are sent to author
5. Day 10. Author revises and returns article
6. Steps 3 and 4 may repeat, if necessary.
7. Article goes through production edit and is scheduled for publication
8. Final, post-production "galley" copy is sent to author as PDF
9. Article is published

Basic style guidelines

When writing and/or reviewing your article, please adhere to the following basic style guidelines:

• Use sentence-style headings (for example, "A new microchip development" and NOT "A New Microchip Development"). This also applies to headings used in tables, charts, or graphic images.
• Spell out acronyms the first time you use them and then, use the acronym in the remainder of the text (for example, "local area network (LAN)").
• If you happen to know that a term is an IBM trademark, mark it. Do not mark other companies' trademarks even if you are a non-IBM author and want to mark your own company's trademarks. You can find the trademarks list at ibm.com/legal/copytrade.shtml. It is sufficient to mark the trademark the first time only that it appears in the body text.
• Use trademarks adjectivally, which means that the trademark needs to be followed by a descriptive noun (for example, "the Power Architecture™ technology").
• Try to avoid Latin in text (for example, instead of i.e. use "that is," instead of e.g. use "for example," instead of via use "through" or "using").
• Do not attack competitors, nor overly praise yourself or partners: avoid superlatives and wording like "industry-leading," "fastest processor on the market," or "without peers." Do not make claims that you cannot back up with independent, third-party research, comparison testing, or benchmarking.
• Be careful about making promises about planned products, features, or product availability dates. If the product is scheduled for availability in the 4Q 2005, tell the reader exactly that: "The chip is scheduled for general availability (planned to be available) in the 4Q 2005" NOT "The chip will be available in the 4Q 2005."
• Because we're writing for an international audience with varying English skills, avoid U.S.-English idioms or slang. For example, do not use "ballpark figure," or an American holiday as a time reference (as in "This chip is scheduled for general availability after Thanksgiving."). Use Merriam-Webster's (www.m-w.com) for spelling, and for grammar questions, use the Chicago Manual of Style.
• Use the active voice. Prefer second person to first person.
• If you use a table, ensure there is an overall table heading. Every column must include a header describing the column below it.
• If possible, have someone who does not work on the same technology or in the same field read the article to test readability.

Your adherence to these guidelines will result in a much faster turnaround when your article is submitted for approval and editing.

Click to read the latest edition of the Power Architecture Community Newsletter. If you have any questions, please do not hesitate to contact the Power Architecture editors.

About the author

Comments (Undergoing maintenance)

Back to top

Trademarks  |  My developerWorks terms and conditions

Table of contents

• About the author
• Comments

Local resources

• IBM Innovation Center - Austin, TX
• IBM Innovation Center - Chicago, IL
• IBM Innovation Center - Dallas, TX
• IBM Innovation Center - San Mateo, CA
• IBM Innovation Center - Waltham, MA
• Technical Briefings in North America

My developerWorks community

Dig deeper into Multicore acceleration on developerWorks

Special offers