FreeStack guideWriting & publishing7 min

Make a versioned script draft before paying for writing software

Turn one short scene into portable Fountain files, named draft checkpoints, a language review and a checked delivery PDF.

YOUR TOOLKIT IN ACTION
From tools to a finished project
River WriterPart of this creative toolkit
GitPart of this creative toolkit
ValePart of this creative toolkit
PandocPart of this creative toolkit
Follow the guide and make it your ownIllustrative overview. Check the workflow and free limits below.
What you’re working towards

A small script packet containing an editable .fountain source, three named draft checkpoints, a reviewed language report, a PDF export and a one-page delivery note.

Start with the file you need to own, not a writing membership. The illustration is a FreeStack concept, not a River Writer or provider screenshot.

About this guide & its examples

This original FreeStack workflow uses a fictional two-page scene to demonstrate portable source, deliberate version checkpoints and a checked handoff. It does not claim a completed screenplay, editorial result or tested provider export. Official sources checked 25 October 2026.

Illustrations are FreeStack concepts, not provider screenshots. Check the free limits below and test your own files before delivery.

Free boundaries before you start

What’s free, whether you need an account, and when we last checked.

River Writer · checked 2026-10-25

Free MIT-licensed macOS writing software that keeps work in ordinary Fountain or Markdown files. The current release is source-build only, requires macOS 13 or later plus the documented developer toolchain, and includes no hosted sync, AI allowance or managed collaboration service.

No River Writer account is required because the project documents no accounts, cloud sync or network service. A source host or sync provider may require a separate account if you choose one.

Git · checked 2026-10-25

Free GPLv2 version-control software for local repositories, with no provider project quota. Remote hosting, backup, access control and large-file storage are separate services with their own limits.

No account is required for a local Git repository. Any remote host or sync service can require an account.

Vale · checked 2026-10-25

Free MIT-licensed local prose linter with no provider document or word quota. Style packages, editor integrations and continuous-integration compute are separate, and automated rules still need editorial review.

No Vale account is required for local command-line use. Registries, repositories and CI services may require separate accounts.

Pandoc · checked 2026-10-25

Free GPL-licensed local document converter with no provider conversion quota. Exact output depends on the selected format, templates, fonts and any optional PDF engine; complex layouts still need visual inspection.

No Pandoc account is required for local conversion. Storage, collaboration and publishing destinations are separate.

PICTURE THE RESULT

A small example to aim for

FICTIONAL TWO-PAGE SCENE · NOT A PROVIDER SCREENSHOT

THE LAST TRAIN

INT. STATION CAFE — NIGHT

MARA folds the timetable once, then again.

MARA
We can still choose the slower route.

draft-01Premise readable
draft-02Dialogue revised
export-v1PDF inspected
ONE SOURCE. THREE CHECKPOINTS.

Keep the words portable.
Make the decisions visible.

.fountain source · named Git history · reviewed style report · checked PDF

FreeStack concept · not a tested River Writer export or completed screenplay.

Illustrative example · adapt it to your project.

Jump to a step
01

Write the delivery contract first

Define the smallest useful result: a fictional two-page scene in Fountain, one PDF for review and a short note naming the source file, draft checkpoints and known limitations. Keep collaboration, production breakdowns, Final Draft import, cloud sync and AI rewriting outside version one. Decide who can approve copy and which file remains the editable source. A portable source file prevents the preview or PDF from becoming the only copy of the work.

02

Draft in a plain-text project

Create a River Writer project and write the scene in a .fountain file. Use fictional names and no confidential production information. Keep the outline, scratchpad and todos limited to this scene. Confirm the source opens in another plain-text editor before relying on the formatted preview. River Writer currently requires macOS 13 or later and a source build; if that setup is unsuitable, the Fountain file remains usable in another compatible editor.

03

Name three meaningful checkpoints

Create a Git checkpoint after the premise is readable, another after dialogue and action are revised, and a final one before export. Use messages that describe the editorial decision, not generic labels such as update. Create a temporary branch only when testing a genuinely different ending, then compare before choosing. A commit records file history; it does not replace backup, access control or an approved remote.

04

Review language without surrendering the draft

Run Vale against a copy or approved working folder with a small ruleset for spelling, repeated words and house style. Review each suggestion rather than applying changes blindly; dialogue may intentionally break a prose rule. Record the Vale version and rules used in the delivery note. A clean style report does not establish factual accuracy, legal clearance, sensitivity review or creative quality.

05

Export and inspect the actual delivery

Export the formatted PDF from the writing app, then open it outside the editor and inspect page breaks, character cues, scene headings and the final line. If you also need a DOCX or HTML reference copy, use Pandoc only after testing the conversion against this scene and keep Fountain as the source of truth. Name every delivery file with the same version label and never describe an unchecked conversion as production-ready.

06

Pay only for the missing writing requirement

Keep the local workflow when one writer can manage portable files and occasional review exports. FreeStack editorial upgrade triggers: a normal signed installer, real-time co-authoring, production-grade Final Draft interchange, managed backup, mobile editing, granular comments, studio permissions or supported delivery templates. Name the requirement and test it with a representative file before buying a membership.

THE BUILD AT A GLANCE

Your workflow, connected.

Follow the steps and carry the output into the next stage. These are suggested handoffs, not automatic integrations.

  1. 01Define the packet
    Start with a plan
    File list + approval rule
  2. 02Own the source

    River Writer is MIT-licensed, makes no network connections and currently ships as source for macOS. Building requires the free toolchain named by the maintainer.

    Editable Fountain draft
  3. 03Make revisions inspectable

    Git is free software. Repository hosting, remote access and backups are separate decisions.

    Three named checkpoints
  4. 04Check the words

    Vale is MIT-licensed local software. Rule packages and editorial standards have separate licences and assumptions.

    Reviewed style report
  5. 05Check the handoff

    Pandoc is GPL software; PDF output and some formats need separate engines or templates.

    PDF + optional conversion
  6. 06Choose the upgrade
    Review & finish
    A specific build-or-buy trigger

Provider information

Check current plans and documentation before committing to a workflow.

A couple of useful questions

Do I need River Writer to use the workflow?

No. The portable Fountain source, named checkpoints and checked delivery are the important outputs. River Writer is today's source-checked example, but another ongoing-free editor can fit if it preserves the file and version boundary.

What stays free?

River Writer, Git, Vale and Pandoc all provide ongoing-free software routes. Your Mac, build toolchain, backup location, remote repository, fonts and any production interchange service remain separate.

Is Git a backup?

Not by itself. Local history can live on the same disk as the working file. Use an approved independent backup or remote only after deciding its access, retention and recovery rules.

What does Save this toolkit keep?

The existing FreeStack flow saves the four catalogue tools to a private stack after sign-in. It does not copy your script, create a repository, run a language check, export a PDF or purchase a provider plan.

What would you try?

Share your result or ask a specific question about this workflow.

Join the conversation
SPONSORED · THE DIGITAL ACADEMYSearch your site. See what you might need.

Start with a TDA website audit to find your next useful improvement.