Computer Architecture Today

Informing the broad computing community about current activities, advances and future directions in computer architecture.

Author Guidelines and Policies

SIGARCH is concerned with the design and evaluation of computing systems across all scales (subatomic particles to data centers). Blog posts should be related to computer architecture, systems or address issues relevant to the community, and this connection should be clear.

Guidelines:

  • Blog posts should be short (300-1300 words) and to the point on a specific topic.
  • Posts are meant to be informal, not formal like a conference or journal paper.
  • Embed links to papers if you cite something, not as citations/bibliography as in papers.
  • Posts are meant to cover the topic broadly, so please refrain from many self-citations.
  • The title should be concise and descriptive of the post.
  • Use (sub) headings as needed to make the content easy to read.
  • Figures and videos are encouraged if available and appropriate.
  • Permission must be obtained for any content that does not belong to the author.
  • Links to externally published items are encouraged.
  • Pre-formatted text (e.g., code) or equations should be in a jpeg/SVG format and embedded in the post so that it scales correctly in the email blast and across devices.

Logistics and blog post process:

  1. The blog editors will create an account for you on the wordpress website so that you may directly enter your post in the website and perform the formatting as you see fit.
  2. Notify the editors (via email) that the article is ready for “review”.
  3. The editors review the article, suggest any modifications and possibly perform light editing.
  4. Select an image to use from adobestock.com or the editors can choose an image. Send the editors the link, and they will add the image to the post as the featured image. The editors have a subscription and will download the licensed version of the image for use in the blog.
  5. Provide a short one or two sentence bio for inclusion at the end of the post.

Contact us for questions, advice or any input: