Guided course - 5 chapters
Training arcs: An Original Comic Workshop with Jax Jetstream
Jax Jetstream guides a five-chapter comic workshop built around Training arcs. You will shape the story promise, test character choices, thumbnail panel beats, revise dialogue and continuity, and finish with a creator-owned issue package.
Your course progress
0 of 5 chapters complete
0%Sign in is required to save progress, checkpoint answers, and notes. Sign in to continue.
What you will make
Build knowledge, use it, and leave with evidence of progress.
-
Build an original story promise around a character want, obstacle, stakes, and change.
-
Turn pressure and costly choices into scene-to-scene consequences.
-
Thumbnail readable panel beats and purposeful page turns.
-
Revise dialogue, lettering space, visual clarity, and continuity in focused passes.
-
Complete an issue sprint with a payoff, next hook, and production action.
Before you start
- No prior comic-making experience is required.
- Bring an original character or create one during Chapter 1.
- Use any writing or sketching method that lets you revise.
Useful materials
- Notebook or script document
- Paper, index cards, or a digital thumbnail canvas
- A continuity sheet for names, rules, motives, and unresolved threads
Suggested rhythm
Complete one creator workshop at a time: read the craft model, make the artifact, run the checkpoint, save the result, and carry one decision into the next chapter.
Original issue sprint
Training arcs Original Issue Sprint
Create a bounded original comic issue package that proves the central character choice, page rhythm, voice, and continuity work together.
What you will submit
- One-page story and issue brief
- Representative scripted or thumbnailed sequence
- Dialogue and continuity revision note
- Final payoff, next hook, and production action
How it will be reviewed
- Originality and creator ownership
- Character-driven cause and effect
- Readable visual sequence and page rhythm
- Distinct dialogue with room for art
- Continuity, payoff, and a finishable next step
Course chapters
Design, draft, check, and carry the story forward.
-
Chapter 1
Training arcs: Story promise and character engine
Turn Training arcs into a clear story promise. Define who wants what, what blocks them, why the result matters, and what must change by the final page.
Creator goals
- State the reader-facing promise of Training arcs in one sentence.
- Connect a character want to a visible obstacle and meaningful stakes.
- Separate an original premise from familiar genre shorthand.
- Build a compact story engine that can generate scenes.
Key terms
1 Write the story promise
Describe the experience this Training arcs issue will deliver. Name the central conflict, emotional flavor, and change the reader should witness without trying to summarize every event.
- Character Choose the person whose decision carries the issue.
- Pressure Name the obstacle that makes an easy solution impossible.
- Change Decide what cannot remain the same after the final page.
2 Build the character engine
Give the lead a public goal and a private need that do not align perfectly. The gap between them creates choices, reversals, and emotional consequences instead of a sequence of events.
A power is most useful when it complicates a choice as often as it solves a problem.
3 Protect originality
List the familiar genre ingredients you are using, then change the motive, cost, setting rule, relationship, or consequence until the combination belongs to this universe and these characters.
Story engineFrom promise to change
A durable premise connects what the issue promises to a choice that changes the story world.
Practice activity - 15 minBuild a one-page story engine
Create a compact premise sheet for Training arcs inside the Training arcs workshop.
- Write the story promise in one sentence.
- Name the lead, want, obstacle, and stakes.
- Add one cost attached to the obvious solution.
- Finish with the change expected by the final page.
DeliverableA one-page original story engine ready to outline.
Success looks like- The lead can make meaningful choices.
- The obstacle creates pressure rather than delay.
- The ending condition differs from the opening.
Knowledge check1 questionWhich premise creates the strongest comic story engine?
Not startedSign in to save chapter notes to your account.
-
Chapter 2
Funny sidekick stories: Pressure, choice, and consequence
Turn Funny sidekick stories into a scene ladder driven by pressure, character choices, and consequences. Each beat should make the next beat necessary rather than merely possible.
Creator goals
- Escalate pressure without repeating the same obstacle.
- Give the lead at least two costly options.
- Make consequences alter the next scene.
- Use reactions to reveal character values.
Key terms
1 Start late and under pressure
Enter the scene when a goal is already at risk. Give the character incomplete time, information, trust, or control so action begins with a decision.
Backstory belongs where it changes a present choice.
2 Force a revealing choice
Offer options that protect different values. The strongest choice is not simply correct; it reveals what the character prioritizes and creates a price the issue must carry forward.
3 Turn consequence into momentum
After every major choice, update the situation. A relationship shifts, a clue changes meaning, a rule is exposed, or a new danger appears. Use that change to launch the next beat.
Scene ladderPressure creates the next beat
flowchart LR N1["Goal at risk"] N2["Pressure closes in"] N3["Character chooses"] N4["Consequence changes scene"] N1 --> N2 N2 --> N3 N3 --> N4Each step should change the conditions of the scene and narrow or complicate the next choice.
Practice activity - 17 minDraft a four-beat pressure scene
Build one Funny sidekick stories scene in which a character choice changes the direction of the Training arcs issue.
- State the immediate goal.
- Add pressure that removes the easy answer.
- Write two costly options and choose one.
- Show the consequence in the final beat.
DeliverableA four-beat scene ladder with one decision note.
Success looks like- Pressure escalates.
- The choice reveals values.
- The consequence changes what happens next.
Knowledge check1 questionWhat makes a scene consequence useful?
Not startedSign in to save chapter notes to your account.
-
Chapter 3
Team-ups: Panel beats and page turns
Translate Team-ups into readable visual storytelling. Assign one purpose to each panel, vary distance deliberately, and stage a page turn that rewards the reader.
Creator goals
- Break a scene into purposeful panel beats.
- Choose shots for information and emotion.
- Keep action direction and geography readable.
- Place a reveal or reversal on a page turn.
Key terms
1 Give every panel a job
Label each panel action, reaction, information, atmosphere, or turn. Merge panels that repeat the same job and add space where an emotional reaction deserves time.
2 Choose the camera with intent
Use wide shots for geography, medium shots for interaction, close shots for emotion or evidence, and unusual angles only when they clarify power, danger, or point of view.
3 Engineer the page turn
Place the setup at the bottom of a page and the answer after the turn. The reveal should change meaning, danger, or direction, not simply display a larger image.
Panel workflowFrom scene goal to page turn
flowchart LR N1["Name scene change"] N2["List panel jobs"] N3["Choose shot distance"] N4["Place page-turn reveal"] N1 --> N2 N2 --> N3 N3 --> N4Thumbnail for clarity first; dialogue and polish come after the visual sequence works.
Practice activity - 20 minThumbnail one comic page
Turn a Team-ups beat into a five-to-seven-panel page for the Training arcs issue.
- Write the change that occurs on the page.
- Assign one job to each panel.
- Mark shot distance and reading direction.
- Move the strongest reveal to the page turn when appropriate.
DeliverableA rough page thumbnail with panel-job labels and a page-turn note.
Success looks like- The action reads without dialogue.
- Panel size reflects importance or time.
- The page ends with momentum.
Knowledge check1 questionWhen should a panel be removed from a page?
Not startedSign in to save chapter notes to your account.
-
Chapter 4
Short-burst speed: Dialogue, continuity, and revision
Revise Short-burst speed for distinct voice, clean balloon space, visual clarity, and continuity. Change one layer at a time so each improvement remains visible.
Creator goals
- Remove dialogue that repeats the art.
- Keep each speaker recognizable without name labels.
- Fit words to the available panel space.
- Run a focused continuity and cause-and-effect pass.
Key terms
1 Cut visual redundancy
Read the art description first, then remove words that narrate the same action. Use dialogue for intention, conflict, subtext, misdirection, or information the image cannot carry.
2 Protect character voice
Give each speaker a repeatable rhythm, vocabulary range, level of directness, and pressure response. Read the exchange aloud and cut any line that could belong to everyone.
3 Run one revision pass at a time
Check story logic, continuity, dialogue, lettering space, and visual clarity separately. A focused pass catches more than rereading while trying to fix everything at once.
Revision labExposition versus dramatic information
Compare what changes when dialogue responds to the image instead of repeating it.
Aspect First pass Stronger pass Action I am opening the vault now. Tell me you changed the code. Voice We should leave quickly. Run first. Regret it later. Continuity The prior injury disappears. The injury changes the tactic. The stronger pass adds intention, voice, or consequence while leaving visible action to the art.
Practice activity - 18 minRun a four-pass revision
Revise a one-page Short-burst speed script from the Training arcs issue.
- Mark dialogue that repeats visible action.
- Differentiate each voice and read it aloud.
- Check balloon space and panel order.
- Verify continuity, motives, and consequences.
DeliverableA marked first draft, revised page, and concise change note.
Success looks like- Dialogue adds information or pressure.
- Voices remain distinct.
- The revision preserves continuity and visual room.
Knowledge check1 questionWhich revision should happen first when a page feels crowded and unclear?
Not startedSign in to save chapter notes to your account.
-
Chapter 5
Wind tunnels: Issue sprint and next hook
Integrate Wind tunnels into a finishable original issue sprint. Build the issue spine, complete a representative script sequence, review it against clear criteria, and choose the next hook.
Creator goals
- Write a bounded issue brief.
- Connect setup, escalation, choice, payoff, and next hook.
- Complete and revise a representative script sequence.
- Leave with a realistic production plan.
Key terms
1 Lock the issue spine
Write the setup, pressure, central choice, consequence, payoff, and next hook in six lines. Remove any subplot that does not change one of those lines in this issue.
2 Build a representative sequence
Choose the scene that best proves the issue works. Script or thumbnail it completely enough to test voice, page rhythm, visual clarity, and emotional payoff.
3 Review, preserve, and continue
Keep the strongest choice, revise the highest-impact weakness, update the continuity ledger, and define the next production action with an owner and date.
Issue spineA complete issue changes the story
The ending pays off the current promise and creates momentum through a consequence, not an arbitrary cliffhanger.
Practice activity - 24 minComplete the issue sprint
Create a compact Training arcs issue package that integrates Wind tunnels and the previous four workshop phases.
- Write the six-line issue spine and success criteria.
- Complete one representative scripted or thumbnailed sequence.
- Request focused character feedback on one named concern.
- Revise, update continuity, and set the next production action.
DeliverableAn original issue brief, representative sequence, revision note, continuity update, and next hook.
Success looks like- The payoff answers the opening promise.
- Character choice drives the result.
- The page sequence is readable.
- The next hook grows from a consequence.
Knowledge check1 questionWhen is the issue sprint ready to close?
Not startedSign in to save chapter notes to your account.