LeCoqRoti
A research assistant opens iA Writer before dawn, the screen set to a warm dark mode. The task is a conference abstract due by nine: 300 words, no footnotes, pure argument. She pastes a rough draft of 500 words into the editor and activates the syntax highlighters. Adjectives glow purple, weak verbs underline themselves in grey. Within a minute she has pruned seven modifiers and re-cast three passive constructions — the text already breathes more easily.
Structure comes next. The new Document Outline, summoned with a quick search keystroke, shows the heading hierarchy at a glance. She drags a section upward to tighten the logic, then uses the Command Palette to set a focus mode that dims everything except the current paragraph. For ten minutes the only thing on screen is the claim, the evidence, the bridge sentence.
When the abstract reads clean, she opens the preview pane: text links and a small data table render without friction. Export to HTML takes two keystrokes, and a PDF with her department’s template follows just as fast. Because the abstract must also appear on the lab’s site, she sends it directly to WordPress from inside the app, assigning herself as author through the new Authorship indicator — a thin band of colour in the menu that confirms the post is hers.
Files on disk: finding where your writing actually lives
A few friction points surface regularly, especially for those switching from rich-text editors. The most frequent is confusion over where files live. iA Writer does not maintain a proprietary database; it reads and writes plain .md files directly on disk or in cloud folders. If a document appears missing from the Library, the likely cause is that the folder containing it was removed from the Locations list. Adding it back through File → Add to Library restores visibility without moving any data.
Preview rendering can also puzzle newcomers. Inline images sometimes fail to display because the file path uses an absolute reference from another machine. Keeping images inside the same folder as the .md file and using relative paths — ./image-name.jpg — solves this across devices. The preview pane respects standard Markdown, but custom CSS in export templates does not apply there; that distinction is worth remembering when a PDF looks polished while the live preview appears bare.
Syntax highlighting occasionally marks a word that is not, in context, a weak verb or filler. The engine uses pattern matching, not prose understanding. Tapping the Escape key dismisses the highlight for that instance, though the same word elsewhere will still be flagged. Writers who find the analysis too aggressive can adjust which parts of speech are checked in the settings, or toggle the feature off entirely for a session.
A less obvious issue involves the WordPress publishing path. If the site uses a custom REST API prefix or an unusual permalink structure, the built-in connection may fail silently. The workaround: export as HTML and paste into the WordPress editor manually — a small extra step that preserves all formatting.
Library setup: add parent folders instead of single files
Setting up the Library correctly on day one saves repeated small annoyances. Rather than adding individual files, add the parent folders that contain your writing projects. The compact Library layout, new in version 8, hides dates and text excerpts; enable it in View → Compact Library if you prefer a lean sidebar that shows only filenames.
Spend ten minutes with the Command Palette. It opens with ⌘⇧P and allows you to reach nearly every action — export formats, focus modes, syntax controls — by typing a few letters. Writers accustomed to keyboard-driven tools will find the palette becomes muscle memory within an afternoon. For those who work in multiple languages, the palette’s fuzzy matching means typing “pdf” finds the PDF export even if the interface is set to Japanese or French.
Customise one export template early. The default PDF output is functional but generic; adding a header with your name or a working title, adjusting the font size, or setting the paper dimensions makes repeated exports consistent. Templates are simple HTML files with CSS, stored in ~/Library/Application Support/iA Writer/Templates/. A single edit there flows into every future export.
If you write across devices, decide on a cloud location — iCloud Drive or a third-party service added through the Locations pane — and make it the default save destination. The app’s single-window search draws from all connected sources, so a consistent folder structure prevents duplicate drafts and the quiet panic of not knowing which version is current.
A scenario: the podcaster scripting an episode
A narrative podcast producer opens iA Writer in a studio corner while the audio engineer checks levels. The task is the cold open for episode twelve: ninety seconds of script that must land with conversational rhythm. She types quickly in focus mode, the interface dimming everything but the current sentence. The syntax engine highlights repeated nouns — she catches the word “city” occurring five times in four lines and rewrites three of them. Adjectives in purple remind her to let the host’s voice carry the tone rather than stacking modifiers.
Her collaborator, the video maker sharing the Ikebukuro studio, leans over to check a cue point. She opens the preview pane to show a clean reading view, then exports a PDF with a template matching the show’s script format — monospaced font, wide margins for handwritten notes, episode number in the header. The file drops into a shared cloud folder; ten seconds later the host, recording from Berlin, confirms it is open on her tablet.
Visual refresh: less chrome, more writing surface on Mac
The interface refresh for recent macOS versions is subtle but noticeable over long sessions. Toolbar spacing, icon weights, and the overall visual density have been adjusted toward a lighter presence — less chrome, more writing surface. On a laptop display at café scale, the difference is the removal of small distractions that accumulate across hours.
Document Outline with Quick Search shifts how longer projects are navigated. Before version 8, jumping between sections of a chapter-length document meant scrolling or memorising line positions. Now, opening the outline and typing a heading fragment moves the cursor instantly. For research reports or manuscripts with thirty or forty headings, this saves real time.
Authorship indicators, a feature that colours author names in menus and the status bar, prove most useful for collaborative writing. When a document passes between two or three people — a blog post with editorial input, a grant proposal with co-authors — the colour cue removes the need to check file metadata or read commit logs. The current author’s colour is visible at a glance, and the palette also shows other contributors who have worked on the file.
The Command Palette, new in this version, absorbs actions that previously required memorising separate shortcuts. Formatting, export, and focus commands all sit under one text prompt. It is the kind of addition that feels like a small convenience at first, then becomes indispensable after the first week.
In short: version 8 refined the workspace itself — the frame around the text — rather than adding features to the writing engine. The result is an app that fades further into the background, which is, for a tool built around focus, exactly the point.
What remains is a tidy folder of plain-text files, searchable alongside cloud documents in a single window, ready for the next early-morning session.
Correspondence 0
Take a chair or join the table to send a letter.
No correspondence on this note yet. Letters are read before they appear.