Current Issue

The Kairos Style Guide

Design Requirements

All webtexts go through a design-edit to ensure they are ready for publication. The design edit consists of checking for readability, accessibility, usability, and sustainability. Design-editing, just like copy-editing, is a practice in negotiation with the author's design-voice. Authors of HTML-based webtexts (e.g., everything except wiki webtexts) are required to follow these design and coding requirements.

Rhetorical Considerations

  • All media and design elements should be non-gratuitous and facilitate or enact the rhetorical and aesthetic argument of the webtext.
  • All links should contribute to the possible meanings and readings of the texts. Linking for the sake of linking is discouraged (e.g., external links in-text to outside sources is usually discouraged in favor of links in the works cited; internal linking to the works cited is discouraged unless a text specfically requires it, and then back-navigation must also be provided).
  • Authors should attempt to make clear where links are going so that readers may make informed navigational decisions. This can often be done by linking from descriptive phrases rather than individual words.
  • Links to external nodes should point, to the best of the author's knowledge, to stable sites and resources. Since back issues of Kairos will be available in our archives, we must strive to make all links as current and accurate as possible. Authors might consider contacting the authors of pages they link to in hopes of determining such stability.
  • Care should be given in linking to commercial sites in order to avoid promoting any particular companies or their products. If links must be made to commercial sites for the purposes of the webtext, they should be made to informational documents rather than sales pages when possible.
  • Offsite/external links should open in a new browser window.
  • Links to other Kairos webtexts should open in the same window.
  • Do not link terminal punctuation.

Accessibility

  • Use alt-tags with every image and embedded media element to provide a clear and concise description of the image and improve accessibility; alt tags should describe the image, title tags should explain the rhetorical use of the image.
  • All submissions that include audio or video multimedia files must also include transcripts.
  • Sceenshots that primarily contain text should not be placed as images in a webtext (transcribe the text and style it with CSS).
  • If using proprietary presentation software (e.g., Flash, Quicktime, .wav, PDFs, etc.), please provide alternate versions of your text as external XML and/or multimodal transcripts to increase readabilty and accessibility of your webtext. In addition, you may be asked to submit the editable version (.fla, .doc, .aup, etc.) for editing by the staff once a piece has been accepted for publication.
  • Use WAVE (http://wave.webaim.org/) to review your webtext for accessibility issues, including code requirements and design considerations such as making sure text elements are presented with sufficient background-foreground contrast.
  • Upon acceptance, any text files or transcripts (usually Word or PDF files) that are linked to the webtext must be supplied for archiving on our server.

Usability

  • All non-wiki submissions require an HTML page (e.g. for a video or audio text, there must be an HTML page container for the media elements).
  • The home page for all non-wiki webtexts should be "index.html"
  • All HTML-based filenames and folders must be lowercase and include no spaces or non-Web characters.
  • All webpages in non-wiki webtexts should have titles that follow Kairos's page-title conventions (e.g. Authorlastname, Short Webtext Title - PageTitle). See current issue for examples.
  • Double-check to make sure all internal and external links work.
  • All images should reside in an /images/ folder (or /media/ folder, as appropriate).
  • HTML-based webtexts should demonstrate cross-browser compatibility (i.e., Internet Explorer 6+, Firefox 1.0+, Safari 1.0+, Opera 8+) and degrade gracefully when elements such as JavaScript are not enabled by a user's browser or when images/CSS fail to load.

Sustainability

  • We need to be able to archive everything we publish, so we cannot accept webtexts hosted on third-party sites (like WIX and Weebly).
  • We strongly encourage authors to use standard, non-proprietary formats (HTML 5, CSS, etc.) rather than Flash or other embedded proprietary media or template engines.
  • Upon acceptance, we will need copies of all embedded media files, and all 3rd-party sites that host files must be shared with the journal in order to facilitate editing and archiving.

Code Requirements

Upon submission, all webtexts will be reviewed for adherence to the basic standards of valid markup. The simplest approach is to code properly from the outset, rather than attempting to correct errors at the end of the editorial process. This primarily requires a few simple steps to ensure that your code will validate. (Tip: You can use http://validator.w3.org/ for HTML and http://jigsaw.w3.org/css-validator/ for CSS to review your code at any time during the development process.)

The following is a short list of requirements that published webtexts will be expected to meet prior to final publication:

  • External style sheets are required to facilitate the editing process. Please do not use inline styles.
  • All element and attribute names must be lowercase (e.g. use alt, not ALT; p not P, etc.)
  • Attribute values must always be quoted (e.g. width="75" not width=75)
  • All non-empty elements that have an opening tag must have a matching closing tag. For example:
    a break must be coded as <br />, list items must end in </li>, and img tags require a closing /
  • Please use character entities for ampersands (&amp;), em-dashes (&mdash;), and en-dashes (&ndash;).
  • We strongly prefer HTML 5 as the coding standard for Kairos webtexts; XHTML is also acceptable.
  • If you are using XHTML, the following lines should appear at the top of each HTML page (you can copy and past the code below if it is not already in the file):

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
    <head>

  • If you are using HTML 5, the following lines should appear at the top of each HTML page (you can copy and past the code below if it is not already in the file):

    <!DOCTYPE html >
    <html lang="en">
    <head>
    <meta charset="utf-8">

Modified APA Citation Style

Kairos follows a modified version of APA, 6th edition. This in-house style is modified to include authors' and editors' full names in all reference lists and full names when the author(s) or editor(s) are mentioned in in-text citations for the first time in each lexia. The in-house style also includes the Retrieved on dates for website citations (which was present in earlier versions of APA).

General Format for In-Text Citations in APA Style for Kairos

In-text citations selected from Who's Writing?: Aristotelian Ethos and the Author Position in Digital Poetics by Kristie S. Fleckenstein:

  • Elaine Scarry (1999) in On Beauty connected aesthetics to justice, reminding us that aesthetics and ethics are intertwined in complex ways.
  • Brian Lennon (2000) hypothesized digital visual poetics as a "zona inexplorada of a never wholly discovered, validated, or otherwise bounded networld field" (p. 68).
  • John Kirby (1990) argued that the great works of classical Greek literature were characterized by what he called the great triangle of peitho (persuasion), eros (desire), and bia (force or strength).

Many Kairos webtexts are submitted by authors more familiar with MLA style. With that in mind, what follows are some of the most common changes authors will have to make to be sure a webtext follows APA style for in-text citations:

  • A citation should include the name(s) of the author(s), publication date, and page number (when applicable).
    For example, "A new paradigm built around complexity could produce a post-dialectical understanding of contemporary pedagogies of invention for the emerging scene produced by digital technology" (Hawk, 2007, p. 7).
  • When the author name is used in a signal statement, the publication year follows the author name, and the page information appears at the end of the citation.
    Byron Hawk (2007) argued, "A new paradigm built around complexity could produce a post-dialectical understanding of contemporary pedagogies of invention for the emerging scene produced by digital technology" (p. 7).
  • APA uses past tense for author signal statements. Example: "Hawk (2006) argued...."
  • Use an ampersand between the names of multiple authors or editors in parenthetical citations and reference lists (Selfe & Hawisher, 2004, p. 38).
  • Use block quotation format when including citations of 40 or more words. Start the block quotation on a new line with a blockquote indentation and omit quotation marks:
    Accordingly, the NCTE Executive Committee adopted a definition of 21st Century Literacies in 2008:
    Literacy has always been a collection of cultural and communicative practices shared among members of particular groups. As society and technology change, so does literacy. Because technology has increased the intensity and complexity of literate environments, the twenty-first century demands that a literate person possess a wide range of abilities and competencies, many literacies. These literacies—from reading online newspapers to participating in virtual classrooms—are multiple, dynamic, and malleable.

General Format for References Page in APA Style for Kairos

References page citations selected from Constructing a Tool for Assessing Scholarly Webtexts by Allison Warner:

  • Crowley, Sharon. (1994). Ancient rhetorics for contemporary students. New York, NY: Macmillan.
  • Kalmbach, James. (2006). Reading the archives: Ten years of nonlinear (Kairos) history. Kairos: A Journal of Rhetoric, Technology, Pedagogy, 11(1). Retrieved November 12, 2006, from http://kairos.technorhetoric.net/11.1/binder.html?topoi/kalmbach/index.html
  • Ong, Walter. (1982). Orality and literacy: The technologizing of the word. New York, NY: Routledge.

Additional references page citation examples:

Many Kairos webtexts are submitted by authors more familiar with MLA style. With that in mind, what follows are some of the most common differences authors will have to make to be sure a webtext follows APA style for a final references page:

  • The final listing of sources in APA is called a “References” page, not “Works Cited” or “Bibliography.”
  • The date is usually in second position (right behind author(s) or titles) and included within parentheses followed by a period.
  • Capitalize only the first letter of article/book titles and the first letter after a colon if there’s one in the title (with the exception of proper nouns and acronyms):
    Selfe, Richard. (2004). Sustainable computer environments: Cultures of support in English studies and language arts. Cresskill, NJ: Hampton Press.
  • (However, do use capital letters for titles for in-text references)
  • Article titles are not italicized and not put in quotation marks:
    DeVoss, Dànielle Nicole, Cushman, Ellen, & Grabill, Jeffrey T. (2005). Infrastructure and composing: The when of new-media writing. College Composition and Communication, 57(1), 14–44.
  • Use “&” instead of “and” when listing multiple author or editor names:
    Selfe, Cynthia L., & Hawisher, Gail E. (Eds.). (2004). Literate lives in the information age: Narratives of literacy from the United States. New York, NY: Routledge.
  • Multiple publications by the same author should be listed in chronological order, with names spelled out in all instances. If publications occur in the same year by a single author (or co-authors), add letters to the year of publication and list the entries in alphabetical order by title. Include the letters—e.g., (Wysocki, 2004a) or (Wysocki, 2004b)—when making in-text references.
    Wysocki, Anne Frances. (2004a). Learning from Fatty Bear: Calling forth gender in children’s interactive multimedia. In Brian Huot, Charles Bazerman, & Elizabeth Stroble (Eds.), Multiliteracies for the twenty-first century (pp. 227–252). Cresskill, NJ: Hampton Press.

    Wysocki, Anne Frances. (2004b). Openings and justifications. In Anne Frances Wysocki, Johndan Johnson-Eilola, Cynthia L. Selfe, & Geoffrey Sirc, Writing new media: Theory and applications for expanding the teaching of composition (pp. 1–24). Logan, UT: Utah State University Press.
  • Italicize journal titles and issue numbers (e.g., Computers and Composition, 20, 415–426.)
  • University press names are spelled out:
    Labov, William. (1972). Sociolinguistic patterns. Philadelphia, PA: University of Pennsylvania Press.
  • For electronic references, there is no final punctuation and the URL should be linked to open in a new browser window unless it’s linked to another Kairos webtext, in which case it should not open in a new window:
    WIDE Research Center Collective. (2005). Why teach digital writing? Kairos: A Journal of Rhetoric, Technology, Pedagogy, 10(1). Retrieved February 8, 2006, from http://kairos.technorhetoric.net/10.1/binder2.html?coverweb/wide/index.html

Common Grammar, Style, and Usage Errors

  • When referring to the Kairos text itself, refer to it as a webtext (not an article or an essay) unless there's a PDF or other accompaniment being referred to.
  • Abbreviations: spell out entire name on the first use and include abbreviation in parenthesis after (e.g., short–term memory (STM)). The abbreviation can be used thereafter, but must be redefined on every node. Note that APA allows for some terms that have their own Webster's Dictionary entries to be listed alone, such as IQ.
  • Ampersands: use character entities (&amp;). These should only be used in References lists or in names that are trademarked with & (e.g., Computers and Composition is trademarked as is, not with an ampersand).
  • Capitalization: in text, do not capitalize field names (e.g., Rhetoric should be rhetoric) unless it is a proper noun (e.g., English should be English). Similarly, do not capitalize job titles (e.g., Associate Professor) or units (e.g., Writing Center) unless it precedes the person's name or is used as a proper noun (e.g., the writing center is the hub of all activity; The Sweetland Center for Writing is the pre-eminent...). In the References list, book titles, article titles, and chapter titles should only have the first word, proper nouns and acronyms, and words directly following a colon capitalized. All other words in book titles, article titles, and chapter titles should be lowercase.
  • Commas around years: set off year in exact dates (e.g., April 25, 2011, was the correct date) but not month only (e.g., April 2011).
  • –em dashes: use character entities (&mdash;), and there should be no spaces around them.
  • –en dashes: use character entities (&ndash;), and there should be no spaces around them. The –en dash is frequently used when there are sets of pages, and character entities should be used in text and in the References list.
  • Hyphenation: do not use hyphens with "non–" words, unless meaning would be confused without the hyphen.
  • In–text citations: in APA style, writers only need to repeat the author and year citation within a single paragraph when a second citation has been inserted in between two citations for the previous author and year.
  • Parentheses: (When a complete sentence is enclosed in parentheses, place punctuation in the sentence inside the parentheses, like this.) If only part of a sentence is enclosed in parentheses (like this), place punctuation outside the parenthesis (like this).
  • Serial comma: use a comma between elements in a series of three or more items (e.g., height, width, and depth).
  • Sets of page numbers: when including a set of page numbers, all numerals should be included (e.g., pp. 119–157 instead of pp. 119–57).