The K/S Slash Convention returns to your computer!

2025 KiScon Zine – Writers’ Guide

from your trusty zine editors, 1lostone and Alice West

Beta readers

Before you submit your work, we ask that each fictional piece be read by someone you trust. A “beta” sits in the place of a reader encountering the story for the first time. A beta reader owes you an honest opinion. They play a role in making your story better. They aren’t there just to reassure you or tell you it’s a great story. They are there to help.
So, give your beta the best possible draft you can write. After receiving it back, be willing to write another draft if it’s needed. If you’re feeling insecure about your best draft, you can ask your beta reader to start with feedback about what they liked about the story and thought was well done. Then they can tell you what they have questions about or feel was less successful.
Examples of the kinds of comments a beta reader might make include:
  • I think this is too short/too long.
  • I didn’t understand what Spock was trying to say here.
  • I don’t think Kirk would be shouting at Bones here.
  • I didn’t understand where the characters were in the last scene.
  • I think Spock is out of character here.
  • I couldn’t picture the gizmo they’re using.   
  • I thought the story was going to be this, but it turned out to be that. Was that your intention?
Betas don’t have to know how to fix an issue, but they should be able to articulate what strikes them as wrong (or right!) or vague or confusing or…. And they should be able to tell you why. If you and they agree to it, they can provide more in-depth commentary, or even ideas for fixes. In the end, of course, it’s your story.
Please provide a copy of this guide to your beta so you both know what to expect. If either of you wants to further communicate with questions and clarifications, all the better.

Style guide


To help both you and your beta reader, we’ve provided a guide that includes grammar, consistent spellings, design rules, and more. We use The Chicago Manual of Style and The Chicago Guide to Copyediting Fiction.
Both you and your beta should proofread for typos and other obvious errors.
All submissions will be formatted according to zine standards.

Italics
  • All language from other planets, especially Vulcan, is in italics, including food, e.g. plomeek soup, le-matya, Klingon bat’leth, Spock’s fra’als.
  • All names of ships (starships, sea ships, space freighters, etc.) are in italics, e.g. the Enterprise, USS Enterprise, USS Grissom, the Fesarius.
  • Direct thoughts and mind-meld communication are in italics. Example: Mr. Scott ran down the corridor. I’ve got to get to the transporter room in time! But: Mr. Scott ran down the corridor. He had to get to the transporter room in time.
  • Italics can be used for emphasis but should be used sparingly throughout.
Regular type (not italics)
The rest of your story should be in regular type, not italics. This includes the following:
  • Planet, star system, and starbase names, e.g. Earth, the Earth, the Andromeda Galaxy, Deep Space Station K-7.
  • Cities and other geographical locations—on Earth or any other planet, e.g. New Orleans, Vulcan’s Forge, the Pacific Ocean, Mount Seleya.
  • Past memories and flashbacks. (Large passages in italics are hard to read. Try to make it clear that the passage is in the character’s head.)
  • Alien names are in regular type, like other names.
Upper case vs. lower case
  • Words in ALL CAPS or in bold are not used in zines. Try italics.
  • Rank and profession should be upper case when used with the name, e.g. Nurse Chapel, Commodore Decker, Doctor McCoy, Ensign Chekov, Mr. Spock.
  • Rank and profession should be lower case when simply referring to the person (the captain, the doctor, a lieutenant, the healer). Example: “Captain Kirk!" Spock protested as the captain bent his favorite first officer over the chair.
Numbers
  • In dialogue, spell out all numbers. Example: “Jim, there’s a twenty-three-point-two percent chance of success.”
  • In text, spell out numbers from zero to ninety-nine. From 100 and up, use Arabic numerals. Example: Uhura tried to make contact for the twentieth time. She was 110 percent fed up.
  • Use numerals for measurements, dates, times, etc., e.g. warp 5 or warp factor 5, Stardate 2253, 25 meters, 97 parsecs away.
  • Starbases and space stations use Arabic numerals. Planets use Roman numerals, e.g. Starbase 3, Deep Space 9, but Omicron Ceti III, Tarsus IV, Altair VI.
Punctuation
  • We use a serial comma, which means putting a comma before the “and” in a list of three or more. Example: Kirk got along the best with Humans, Andorians, and Vulcans.
  • We also use a comma before “too,” whether within or at the end of a sentence. Example: Spock hoped he would have the opportunity to penetrate Jim, too.
  • Short introductory phrases are followed by commas. Example: “By the way, my back is killing me,” Kirk hinted. So, Spock gave him a backrub.
  • Periods and commas always go inside quotation marks. Example: “Captain…Jim,” Spock whispered. Wesley had called him “Captain Dunsel.”
Vocabulary (spelling, upper-case words, compound nouns, hyphenated adjectives, etc.)
Overall, use U.S. spelling.
(toward, not towards; flavor, not flavour; among, not amongst)

all right (not alright)
ashayam
bondmate (not bond mate or Bondmate)
come (verb and noun)
force field (not forcefield)
fra’als
half-Human, half-sister, half-breed
Human (also Tellarite, Orion, Vulcan)
human being
kal-if-fee
Kolinahr
le-matya
mind meld (not mindmeld or mind-meld)
multianything (multicolored, multipurpose, etc.)
non-stop, non-vibrating, non-native, etc.
planetside (location)
psi-null (adjective)
psi points
ShiKahr
sickbay, the bridge, the mess/mess hall, the observation lounge, etc.
starbase, moonbase
stardate
Starfleet Headquarters, Headquarters
t’hy’la (not uppercase unless it starts a sentence)
turbolift
Vulcan Science Academy, Vulcan High Council

There are a few cookies involved when you use our website, to make your browsing experience better. However, we do not have any targeted ad content here, and we don't analyse site traffic because our webmaster has better things to do (e.g. write K/S fic). We anonymise requests to third party servers, so no user-identifying information will be shared when you click on a link to an external website.