SWCCG Wiki:Style guide

This page sets the editing standards for everyone who writes on the SWCCG Wiki, human or AI. The same rules apply to all editors. The wiki is an encyclopedia: a compendium of existing knowledge that is honest about where the knowledge comes from. Editors do not invent knowledge.

Standing rule: SWCCG is a small world (identity matching)

Bill (2026-10-12; repeated many times): SWCCG is a small world. If a match is about 99.8% likely to be the same person, treat them as one person and go with it. Never ask Bill to confirm near-certain matches. Skip only genuinely ambiguous cases.

State near-certain matches plainly (Bill, 2026-10-13): once a match passes this rule, write it as fact. Do not add "(inferred)", "matched by name" or conflict/hedging notes on pages, tables or Talk pages. Keep factual spelling-variant notes (e.g. listed as "Clint Hayes").

This covers all identity matching:

• Name variants: nickname or short form, middle initial, obvious typo, same events (Charlie/Charles, Matt/Matthew).
• Nicknames and handles: forum shorthand (for example "BFred" for Brian Fred), and GEMP, Holotable, DeckTech, or Slack handles when context makes the match near-certain.
• Photo identification: a tag or caption, the person's own comment, elimination within a tagged group, a nickname or handle plus thread or event context that makes the person near-certain, or a distinctive name plus a Decipher or SWCCG link (for example, a Decipher staffer of that name), with the reasoning on the page's Talk page (Bill, 2026-10-27). A photo may come from any source. Uncertain faces stay unidentified.
• Exact name + Star Wars CCG Facebook group (Bill, 2026-10-30): an exact legal-name match already on the wiki who is a member of facebook.com/groups/starwarsccg is the same person; dest. Group membership is a Decipher/SWCCG link. Hometown match is extra color, not a gate. A public Intro with no SWCCG text does not block. Worked: John Petelle. Still skip locked identity traps and inexact names (Caputo ≠ Caputa).
• Decklist and results attribution: last-name-only sheets, first name plus initial, Username boxes, and published nicknames — merge onto the identified player page when context makes the match about 99.8%.

One canonical page per person; other names redirect. Link as Name as in source. Add an "also known as" or handle note on the person page.

Conflicting spellings. When name variants conflict, compare the sources (results, forums, decklists, videos) and use the best-supported name for the page; the other spellings are redirects, with a "sometimes spelled" note on the page. Example: JW Millet (also published as J.W. Miller and JD Millet).

Write for the reader

• Reader value decides what stays. Include a fact if it changes what a player understands or what a collector does. Cut it if it does not, even when it is true and sourced. Catalog bookkeeping, such as a rarity code or how an encyclopedia labels a pack slot, is not reader value.
• Be concise. Use short, neutral sentences. Cut repetition and unnecessary detail. Cut words before facts. When a source has a long list, put it in one sentence and move on. Clarity and full understanding come first: a sentence or quote may be as long as clarity needs (Bill, 2026-10-26).
• Describe the subject, not the sources. Write "X is Y", not "The Encyclopedia lists X as Y". Where the information came from belongs in the citation.
• Minor facts are welcome. Many readers collect and never played, so short, sourced collector and pack facts, such as the original price of a pack, add to the article.
• Give an example for an unusual rule. A concrete example makes a strange concept clear, for example "if both cards were in hand, they would be lost to Monnok". Not every rule needs one.
• Lead with the fact (Bill, 2026-10-13). The first sentence says what the subject is and the most important thing about it. Context and background come after the facts, never before.
• State facts plainly. When a reliable source, or Bill's own knowledge, supports a fact, state it directly ("Decipher showed Lucasfilm the card"). Do not soften it with "reportedly", "is said to", "appears to", or labels such as "soft" or "secondary". If a claim is genuinely disputed, name who says it ("According to Holland, ...") once, then move on.
• No research notes in articles. The article body never contains process or meta text: no "research note", "this pass", "this page does not invent", "not found", "no source says", "unverified", and no Gaps, Open questions, Research, or Sources-checked sections. Open questions and empty searches go on the Talk page under Missing data.
• Do not describe what an image shows. Captions identify the subject and credit the photographer ("Sealed first-series box. Photo: BoardGameGeek user KaosBound."). Do not narrate visible content (art, colours, frames, which box is on the left). Quote printed text only when the text itself is the fact.
• Length discipline. Write the shortest article that covers the facts. Each section earns its place. Do not repeat a fact in a table and in prose, or in the lead and again later. A rewrite should usually be shorter.
• End directly. The last section ends on a fact, usually the outcome or the current state. No summary paragraph, no caveats, no "more research is needed".
• One reference list. Use the References section only; do not add a separate Sources list that repeats it.
• Filler check before saving. Search the body for "note", "research", "pass", "not found", "no source", "unverified", "soft", "reportedly", "appears", "Gaps", "Inferred". Rewrite each match as a plain fact or move it to the Talk page. "Inferred" is still allowed as a Talk-page or reference note (likely facts may be published marked inferred there); just do not put an "Inferred:" label in body prose.
• Run the style lint (Bill, 2026-10-14). AI agents must run python3 authoring/style_lint.py draft.wiki --title "Page" (in the billbisco/swccg-wiki repo) and fix every flag before saving any article, then run style_lint.py "Page" on the live page after saving; never save with open flags. Human editors may run it too (optional). It flags hedge and meta words, Gaps/Notes/Research headings, a Sources heading outside deck and event pages, captions that describe the image, cited URLs without a Preserved copy, personal email addresses and empty refs, and reports the body word count against the previous revision. It has no sentence- or quote-length limit.

Cite your sources

• Important facts deserve a citation: numbers, dates, rules, and anything a reader might doubt. Not every sentence needs one.
• When a fact is well established, add the reference and move on.
• When a claim is disputed, doubtful, or an opinion, name the source in the sentence itself ("According to ...").
• Citation layout (Bill, 2026-10-20). Sources go in the References section as <ref> citations, each with its Wayback Machine Preserved copy inside the same ref: <ref>[https://example.com/page Title], site (date). Preserved copy: [https://web.archive.org/web/20261020000000/https://example.com/page Internet Archive]</ref>. An External links section is only for further reading, and its links are archived too. Only deck and event pages (decklists, tournaments, championships, Retro League events) keep a Sources section; every other page cites in References.
• Every cited URL needs a checked Wayback copy (Bill, 2026-10-20). Every external URL on a page needs a Preserved copy, including links in lists, tables, body text and External links. The copy is a Wayback Machine capture (web.archive.org/web/ + 14-digit timestamp + the URL) or an Internet Archive item. Cite a copy only after it has been opened and checked, or verified against the source by the archive worker. Links to wiki.swccg.com and swccg.com/images need no copy.
• Private source documents (Bill, 2026-10-12). When Bill provides private source documents (for example, an organizer's email), host them under swccg.com/snapshots/ (for example, snapshots/email/) and archive them like any other source, with a Preserved copy.
• No personal email addresses on wiki pages (Bill, 2026-10-14). Do not publish personal email addresses (player contacts, mailto strategy credits that only carry a private address, or emails embedded in Service rows). Keep callsigns, hometowns, dates, and citations. Drop an emptied email column. Exception: a clearly defunct, historically significant, non-personal address may stay (for example a Decipher corporate strategy credit such as joea@decipher.com).
• Don't narrate source disagreements (Bill, 2026-10-13). When sources differ, state the best-supported fact and cite all the relevant sources on it. Explain the discrepancy on the Talk page, not in the article. Avoid sentences such as "Decipher announced 11 July; the Players Committee gives only Summer 2001."
• Do not add inferences. If no source states it, it does not go in the article. Put the idea on the article's Talk page, labeled as an inference.

Accuracy

• Link card titles and use the exact card title, including the printing's own title (for example, the Alternate Image of Queen Amidala, Ruler Of Naboo is Queen Amidala, Ruler Of Naboo (AI)).
• Give a price only where it shows something, such as an Alternate Image against the regular printing. A pack's original price is welcome.
• Proofread and read the changes before saving.
• Always give the deck's format (Bill, 2026-10-14). Every decklist page and table row names a format. If the source does not state it, use the smallest format that fits the newest set in the list and the date, and mark it "(from the card pool)".
• Deck format comes from the tournament. A DeckTech post date does not determine a deck's format; use the tournament's format. For example, every FreedomCon 2001 deck is Premiere - Reflections III.

Holder and tenure tables

• No repeated person. Never repeat a person across rows when their tenure is continuous; show each name once on the row where they belong so one line shows their full tenure.
• Merge identical adjacent rows. Merge adjacent rows with identical holders into one row with the combined date range.
• Close gaps. Check for gaps between one holder's end and the next holder's start; research the true handoff date rather than leaving a gap.
• One range, not capture dates. When nothing changed between documented dates, show one range from the start date to present (or to the last documented date if no longer current), not a list of capture dates. Never split a continuous tenure at a year or archive-snapshot boundary unless the role, team or title actually changed per a source.
• Same role, one row. Abbreviations or wording variants of the same role (e.g. Dev = Developer) are one role: merge into one row with the full name.
• Position first. In organization and roster lists, write every entry position first, then person (for example "Design Advocate: Chris Kelly"), including advocates, in the same format as team entries. Service roles inside teams (for example lead GEMP slicer) are positions too: write "Lead GEMP slicer: Jeremy DiPaolo", one sub-bullet per role, not "Jeremy DiPaolo (lead GEMP slicer)".

Photos of people

• Photo sources (Bill, 2026-10-27). A photograph of a person may come from any source. The only test is how certain it is that the photo shows the same person.
• Small World Rule for photos (Bill, 2026-10-27). A distinctive name plus a Decipher or SWCCG link (for example, a Decipher staffer of that name) means the photo is taken as the same person. Record the reasoning on the page's Talk page. See Standing rule.
• Facebook photographs (Bill, 2026-10-30; worked: Charles Lund). Dest the photograph as the wiki File (lead and Photographs; caption is the name, or the words printed in the frame). Preserve a screenshot of the Facebook surface as it appeared (photo viewer or group post) as the Route C snapshot: a short yellow banner with the date and live URL, then that screenshot. File page: who, Facebook, date, live URL, Preserved copy. Identification stays on Talk. The Facebook-chrome screenshot stays off Photographs.
• Photo difficulty is not a skip (Bill, 2026-10-30). Dest the best available photograph of the person. Tiny circulars, AVIFs, and low-resolution faces dest as JPEG; the wiki scales them. Worked: Jindřich Nepevný 88×88 circular. Do not HOLD for a failed circular click, AVIF, "need a larger JPEG", or a two-person frame when the subject is identifiable.
• Repeating face in a group (Bill, 2026-10-30). When one face is present across several pictures, dest that person (crop of that subject + uncropped original in Photographs). Worked: Roberto Borias left-most face.
• Memes and logos are not the lead. Skip a meme, logo, or product circular as the person lead; dest a real photograph of the person from the same profile. Worked: David Shettlesworth fish photograph instead of the meme circular.
• Identify from evidence under the small-world rule. Name a person from a tag or caption on the source (or the person's own comment), by elimination within a tagged group, or from a nickname or handle plus thread or event context that makes the match about 99.8% certain (see Standing rule). Mark anything truly uncertain as unidentified rather than guessing.
• No obscene gestures on person pages (Bill, 2026-10-12). Do not put a photo that shows an obscene gesture (for example a middle finger) on a person page. Such a photo may be used only as an identification reference; do not upload it to the person page or display it there.
• Cite the source and an archive copy. On the File page, link the source photo or post and add a preserved copy (Preserved copy: Internet Archive). If no archive can capture it, say so.
• Credit the photographer only when known. Otherwise leave the photographer field blank. A still from a video is credited to the video's creator (the Players Committee YouTube channel is titled Star Wars CCG; credit those stills Players Committee).
• New file names only. Never overwrite an existing file; check for duplicates on the wiki first.
• Hunt a lead photograph (Bill, 2026-10-16). When creating or expanding a person page, hunt a sourced photograph and put it on the page. Video stills from SWCCG shows are allowed; crop StreamYard nameplates, host picture-in-picture, letterbox, and empty background out of stills so a single subject is centered. Do not leave a person page without a photograph when a sourced copy exists.
• One lead photograph. A person page carries one lead portrait at the top as [[File:Name.jpg|thumb|right|260px|Caption.]].
• Centered images of single subjects (Bill, 2026-10-16; restated 2026-10-17; measured 2026-10-17). A lead photograph of one person is cropped so the subject's head sits in the center of the frame. Measure the head bounding box on the original. The crop-box center must match the head center within 5% of the crop width. Crop letterbox, black bars, StreamYard chrome, empty background, other players, bags, and table until head and shoulders fill the frame (Shannon tightness: worked 230×208). After the crop, open the crop file; if you can name empty table, a bag, or another player on one side, recrop that side off. Worked: Kevin Shannon 2011 Match Play Championship crop. Worked miss: first Ray Bordier SAT crop (File:Ray Bordier DecipherCon 1999.jpg; face on the right, bag and other players on the left). If a hall-shot crop is still off after that gate, use the full original as the lead and keep the crop File on wiki unused. Worked: Aldrin Long, Piergiulio Nardulli, John Arendt, Jason Burrows, Stuart Jones (Bill 17 Oct 2026).
• Additional photographs after the results (Bill, 2026-10-16). Extra photographs go in == Photographs == after Tournament Results, Retro League, Appearances, and In print when those sections exist, before Community card or See also. Use a <gallery> in that section. Do not put a gallery between the lead and the first heading.
• Photographs extras are gallery thumbs. In == Photographs ==, extras use a <gallery> so they render as thumbnails. Do not put [[File:…|thumb|left|…]] or a raw File in that section: that floats a full-size picture. Worked miss: first dests of Allen Varney and Lester Smith. Worked: Michael Mikaelian.
• Add good extras to Photographs (Bill, 2026-10-17). When a sourced photograph of a person is found, dest it. One lead; extras go in Photographs even when the page already has a portrait. Do not skip a good extra because a lead exists. Excess can be trimmed later. Worked: Gary Carman keeps sat14 as lead and the events-page sw99champ.jpg highlight in Photographs.
• Every new photo goes in the gallery (Bill, 2026-10-27). Whenever a new photograph of a person is found, add it to the <gallery> in == Photographs == on that person's page, even when it is also the lead image. If the page has no Photographs section, add one in the usual place and keep the existing layout. Worked: Kendrick Summers (File:Kendrick Summers Rebel Leaders 1997.gif).
• Keep the original with a crop (Bill, 2026-10-23). A person-page lead may be a crop of one subject from a larger still. Put the uncropped original in == Photographs == on the same page. Do not dest only the crop. A two-person or group original still belongs in Photographs when it is the source of the lead crop. Worked: Michael Mikaelian lead File:Michael Mikaelian 1996 Worlds.jpg with File:Michael Mikaelian at 1996 Worlds table.jpg in Photographs.
• Heading is Photographs. Use == Photographs ==, not Gallery or Photos.

Pictures for articles

• Find pictures for every article (Bill, 2026-10-16). Event, place, set, mechanic, and website articles should carry relevant pictures when a sourced copy exists. Hunt for venue photographs, contemporaneous magazine coverage, player portraits from that event, product shots, related card images, and archived website graphics.
• Historic venue photographs. Public-domain photographs of a venue used for an SWCCG event are allowed (worked: Cavalier Hotel for the 1998 Decipher World Championship and 1999 Decipher World Championship).
• Venue photograph in the lead (Bill, 2026-10-16). An event article puts a photograph of the site in the lead. Two right-hand thumbs are allowed: the venue, and an event graphic or a later photograph of the same building. Worked: Cavalier Hotel on 1998 and 1999 Worlds; Virginia Beach oceanfront on FreedomCon and 2001 Decipher World Championship. Hunt a contemporaneous licensed photograph first.
• Website screenshots and original graphics (Bill, 2026-10-16). An article about a website carries archived screenshots or original site graphics of the home page and major section pages when those copies exist. Prefer the original GIF or JPEG from the archived site over a screenshot of Wayback chrome. Worked: Decipher.com lobby image-maps and section banners.
• Split oversized website articles (Bill, 2026-10-16). When a website article is too large for one lead-plus-gallery, split major sections into subpages so each page can carry its own pictures. The hub keeps a short summary and a history gallery; the subpages hold the detail and the section graphics. Worked: Decipher.com into Decipher.com Star Wars CCG, Decipher.com Galleries, Decipher.com contests and Decipher.com downloads.
• Straighten and crop. Straighten skewed scans so the subject fills the frame. Edit out magazine margins, adjacent cards, and card chrome from a portrait crop.
• Two lead thumbs plus a gallery. Two lead thumbs plus a gallery is enough. Do not leave an event page or a website page text-only when sourced pictures exist.
• Facebook groups (Bill, 2026-10-16). An article about a Facebook group carries a screenshot of the group (cover, title, and membership line). Crop out Facebook chrome and personal posts. Worked: Star Wars CCG Graded.
• Person pages. Person-page photographs follow Photos of people (one lead thumb; extras in Photographs after the results). This section is for event, place, set, mechanic, and website articles.
• Where to look first. For event, place, set, mechanic and website pictures, search SWCCG-associated sources first. A public-domain historic venue photo is allowed when that venue hosted an SWCCG event. Photos of people may come from any source (see Photos of people).
• Convention and multi-game event pages (Bill, 2026-10-16). This is an SWCCG wiki. Convention pages stay SWCCG-first: other Decipher games get a brief mention and a hub link. Photographs on those pages show SWCCG play, SWCCG people, the venue, or SWCCG prizes. Other-game-only photographs stay on that game's hub or on the person's page. Worked: DecipherCon 2002.

Tournament and league pages

• All service goes in the Service table (Bill, 2026-10-14). Whenever a person page or a source mentions any service by that person, it must be a cited row in the person's == Service == table, not just prose. Service includes tournament director, judge, Squadron or other volunteer roles, Players Committee or Decipher roles, event host, and GEMP or development work. Each row gives the dates and the role in the source's own words, with a reference. If the page has no Service section, add one just above the first section.
• Hosting a show is Service (Bill, 2026-10-16). Creating or hosting a published SWCCG show or channel is a Service row. Being a guest on someone else's show is Appearances.
• Formats are single GEMP format names, e.g. "Premiere - Jabba's Palace Sealed Deck" or "Premiere - Cloud City (Modified)". Link the exact format page if it exists; otherwise write the exact name as plain text.
• Standings: show the top 8, with the full list in a collapsed table (class="wikitable sortable mw-collapsible mw-collapsed").
• GEMP handles go in a standings column, filled where known from the player's page or the sources; leave the cell blank if unknown.
• No handles in prose. Link the person; their page gives the handle.
• Newest first (Bill, 2026-10-13). On player pages, Tournament Results and Retro League rows run newest first: latest year at the top, and within a year the latest event first (season standings and ROCS playoffs above that year's events).
• Lead with the best result (Bill, 2026-10-13). A player page's lead opens with the player's best or most notable sourced result (a win, a top finish, or a season or ROCS title), not a weaker or older placement. Mention other results after it, keep it to a sentence or two, and cite it, reusing the result row's reference.
• Every decklist page needs a source plus an archive copy (Bill, 2026-10-13). Cite where the list came from (the PC decklist page, a GEMP deck share, a forum post, or a Bill-provided email) under Sources, with a Wayback Preserved copy. Forum and PC pages are first saved as a snapshot under swccg.com/snapshots/, and that snapshot is archived; cite both the original and the archive. Never invent a source; if none can be found, say so on the Talk page.
• Unmarked cards are the original (Bill, 2026-10-13). In a decklist, a card or objective not marked (V) is the regular Decipher card: link the original printing (for an objective, its two-sided page, e.g. Hunt Down And Destroy The Jedi). Link the (V) card only when the list says (V). If an objective is on the wrong side for the deck, it is a transcription error: leave the link and note it on the Talk page.

Tournament reports (Bill, 2026-10-24)

• One article per report. A player's own account of a tournament (from DeckTech, a fan site, the Players Committee forum, a video, …) gets its own article, titled <Author> <Report title> (tournament report). It gives the author, publication, event, date, finish, record and decks, a table of the games described, and the original report.
• The report text is reproduced verbatim and uncensored. Only a crude page title is replaced (by author and event); the original title stays in the article.
• Every tournament a report mentions gets a page with what is known (date, site, format, players, winner, results) and a row on List of SWCCG tournaments. A side event covered in a report (for example a sealed event at Worlds) gets its own page and is mentioned on the main event's page.
• Every named player gets an article about them and what they played, with a Tournament Results row citing the report. The small-world rule applies: a named person is the same person as the existing page of that name. A player named only by first name gets no page.
• Reports update existing event pages: new participants, finishes, records, player counts, dates and sites, each cited to the report.
• Discrepancies: Decipher's records, and an event page's existing sourced record, are trusted over a player's report until there is more evidence. The conflict is noted in a Discrepancies section on both the report article and the event page.
• Each source has a catalog page (e.g. DeckTech tournament reports) and a category under Category:Tournament reports; the overview is Tournament reports.

Appearances and In print

• Guest spots and written features (Bill, 2026-10-16). A guest on a video or audio SWCCG show, or the subject of a written feature, gets a cited row on their person page the same turn. The table is the mention, as with Service.
• Appearances (video and audio guest spots): heading == Appearances ==, table columns Date / Outlet / Title / Role, oldest-first. Role in the source's own words, otherwise guest, co-host, panelist, or interviewee. Place after Tournament Results and Retro League (after Tournament Results when there is no Retro League; after Service or the lead when there are no results sections).
• In print (written articles and features): heading == In print ==, columns Date / Publication / Title, oldest-first. After Appearances when both exist.
• Cross-reference the host catalog. Filling a Guest(s) cell on a host page (for example BoardMatt) also adds the matching Appearances row on the guest's page that turn.
• Interviews stay Interviews. == Interviews == with === Outlet, date === subsections remains the write-up of interviews OF the person when there are two or more. A video interview still gets an Appearances row.
• Not every mention. The person must be a guest, interviewee, panelist, or named co-host who is there to discuss. Personal opinion lists are not cross-referenced. A first name with no last name stays unlinked (do not invent a person page).

Anagrams on person and card pages (Bill, 2026-10-15; restated 2026-10-17)

Sourced printed-title anagrams of a person, a close family member, or a named pet get their own section. Worked examples: Tom Braunlich / Nabrun Leids; family table: Chuck Kallenbach.

• Person page. Heading is always == Anagrams ==. Place after the last career or results section, before See also. Use the same three-column table as Anagrams (Card / Unscrambled / Relation). The table is the mention; keep designer leads on the career. Stubs whose only sourced fact is the anagram keep one sentence in the lead and still use the table.
• Intro sentence. Write the fact ("Nabrun Leids is an anagram of Braunlich" / "Printed titles scramble Braunlich's surname."), then the table. Cite Anagramed Decipherians and Encyclopedia 3.2 p.200 on that sentence.
• Family and pets stay on the same table, with Relation filled in. Each related person still gets their own page and their own one-row table.
• Only sourced rows. Copy Card / Unscrambled / Relation from Anagrams or a named Decipher source. Uncertain hub rows stay on the hub until the match is solid. Do not invent new anagrams.
• Card page. Always Template:Card |anagram= ("The title is an anagram of Person."). That renders == Anagram ==. Not under Also known as.
• Printed title. The Card column and the card page use the printed title. A short-title redirect is allowed (R'kik D'nec → R'kik D'nec, Hero Of The Dune Sea).
• Hub. Anagrams is the full list. Person pages list only that person's rows. See also includes Anagrams. No card art on the person page.

Easter eggs on card pages (Bill, 2026-10-17)

Hidden jokes, call-outs, and extra images on a printing get their own section. Hub: Easter eggs.

• Card page. One == Easter egg == via Template:Card |easter_egg=, immediately before See Also. Omit when none. Two eggs on one card stay one section.
• Cite the fact. Cite Decipher Art Show 1999 (the capture you opened) as primary for Premiere through Jabba's Palace. Later-set eggs cite Encyclopedia 3.2. Write the fact, not the source. Zoom crop on the card.
• Hub. Easter eggs is the full list. See also includes Easter eggs.
• Packaging. The Hoth display-box egg goes on Hoth Limited, same heading immediately before See also.

Card infobox Versions (Bill, 2026-10-26)

Template:Card Versions is the family navigator. Full lineage both directions. Omit the row when this printing is the only one. Dest remaining families in waves. Worked family: Luke Skywalker.

• Closed prefixes, oldest first: Decipher · Decipher (AI) · Decipher Errata · PC Errata · Virtual Original · Virtual Legacy · Virtual Legacy (AI) · Virtual Modern · Virtual Modern (ALT).
• Unmarked Decipher is the printed face. Do not prefix Original. Title (Original) redirects to unmarked print.
• Decipher Errata is a later Decipher rewrite (Glossary or Supplement).
• PC Errata only when the Players Committee rewrote past Decipher.
• GEMP ID is the id GEMP loads. Bare on the current playable article. Letter o on the first-published face. Letter d only as a middle layer when print, Decipher errata, and PC errata are three distinct texts. Worked: Luke Skywalker (Errata) is 1_19.
• Current row: bold this page plus the GEMP id.
• Host twins that share one GEMP id use one Versions line plus a hatnote "also listed as".
• Fan and custom printings stay off championship Versions.
• Docs: Template:Card/doc · Card versions.

Websites and sources

• Include the site's images (Bill, 2026-10-14; expanded 2026-10-16). An article about a website or source includes its relevant images (banners, deck or event graphics, home-page and section landing-page screenshots) from archived copies. Prefer original archived GIFs and JPEGs. Each File page cites the source page and a Wayback copy of the image or page. Event and mechanic articles follow Pictures for articles.
• Split for size and pictures (Bill, 2026-10-16). Oversized website articles split into pictured subpages. Each subpage gets its own lead image and gallery.

Cross-linking checklist (Bill, 2026-10-14)

When you create a page, add it to every index it belongs in, and create missing pages for what it mentions:

• Fan site: the Fan sites table and Category:Fan sites.
• Facebook group: the Fan sites table, Category:Fan sites, the admin's Service row, and a screenshot of the group.
• Decklist: a page for every list an article mentions. Link it from the decklists index (Decklists or its source catalog), the event page, the player's Deck designs section and the source article.
• Tournament: an article for every tournament mentioned, listed on List of SWCCG tournaments, with a row in the TD's Service table.
• Results, both ways (Bill, 2026-10-24): every player listed in an event's results has a row for that event in a results table on their own page (Tournament Results, or Retro League for league events), citing the same source. A link in See also or in a Tournament reports list does not count. A new player page always gets its results row, never an empty table.
• People: named team members and organizers get player pages (stubs are fine), linked from the event and team. A personal opinion list (someone's Top 10) is not cross-referenced onto each named player's page.
• Guests and features: guests on SWCCG video or audio shows, and subjects of written features, get a cited Appearances or In print row the same turn the host catalog records them.

Talk pages

Use an article's Talk page as the editors' notebook after any substantial edit. Useful sections are:

• Missing data: what you looked for and could not find or verify.
• Possibly faulty data: facts you doubt, with the conflicting sources.
• Marginal cuts: things you left out that another editor might want back, with their sources.
• Build notes: how a fact was traced, for the next editor.

When tightening an article, move anything cut that may be useful (open questions, weak sources, cut text) to the Talk page under Missing data or Marginal cuts, so the article stays clean and nothing is lost.

Working together

• If you disagree with another editor's change, or think it is wrong or incomplete, say so and give your reason.
• Once your concern has been heard and the decision stands, follow it. Speak up, then support the decision.
• Check the current version of a page before editing, and apply your changes on top of other editors' wording rather than replacing it.
• Use a short edit summary that says what changed.