Crossword first hour
By Across Bind editorial team Current release, published November 29, 2022
After you install XWord, spend the first hour proving a real crossword file opens, clues scroll, and saves land in a folder you control. Skip Package Manager until that baseline works.
Windows users should already have run XWord-Windows.exe. macOS users should have extracted XWord-macOS.zip. Linux builders should only continue if the binary launched from their source build.
Open one familiar puzzle
Use File, Open and choose a small Across Lite .puz you already trust. Confirm the grid appears beside across and down lists. If the file fails, note the format and try another .puz before changing preferences.
Confirm clue navigation
Click a few across and down clues. Tab or arrow through the grid the way you normally solve. The clue prompt should track the active entry. Docs: main window.
Timer once
Start the timer for one short practice puzzle. Stop it when you finish or pause. Timed crossword practice is optional; prove it works once so tournament habits are available later.
Check before reveal
Use check letter or check word before you reveal a whole grid. Learn where those commands live on the Solution menu so you do not spoil a puzzle by accident. Solving prefs: timer check reveal.
Save to a known folder
Save the puzzle under a folder on disk you control. Write that path on the machine ticket beside the installer filename. Cloud sync is not required for a local crossword habit.
Light layout only
After one save works, try a single layout tweak such as floating a clue list. Heavy layout experiments wait until tomorrow. Layout notes live in upstream docs.
Optional Package Manager later
Tools, Package Manager can add downloaders. Do that only after the first .puz path is boring. Guide: lua packages.
Write the update door
Bookmark GitHub Releases for mrichards42/xword. Prefer the same asset names next time. Update guide: update uninstall. Safe path: download safe.
Across Bind publishes this first-hour checklist for people who searched for crossword software. Upstream XWord remains GPL-3.0. Keep Across Lite or browser boards as fallbacks until the new window feels normal on shared desks.
Club machines should prove the same eight habits after every reimage. Travel laptops should open one cached .puz offline after the first download. Classroom tickets should list the puzzle folder path so volunteers stop inventing new download folders mid-workshop.
Asset names to keep boring
Prefer XWord-Windows.exe on Windows and XWord-macOS.zip on macOS from GitHub Releases for mrichards42/xword. Linux remains a source build on the current tag. Write those names beside the OS version on the machine ticket so the next bump stays honest.
- Windows door: XWord-Windows.exe
- macOS door: XWord-macOS.zip
- Linux door: README build notes only
- Ignore packages_*.lua when you only need the installer
Habits that keep installs clean
Type the GitHub Releases URL yourself. Refuse Softonic-style rename jobs. Prove one local .puz open before Package Manager. Keep Across Lite or a browser board as a labeled fallback during the first week on shared desks.
Travel laptops should download once on trusted network, then solve offline. Classroom images should re-prove File, Open after every reimage. Club volunteers should stop inventing a third download when SmartScreen or Gatekeeper blocks the first honest run.
- One Releases bookmark per profile
- One puzzle folder path on the ticket
- One update door forever
Related paths on this guide
Home install panel: crossword home. Safe download: download safe. Releases map: releases. GitHub overview: GitHub. First hour: installed. Windows detail: install on Windows. macOS detail: install on macOS. Linux source: install on Linux.
Across Bind publishes this map for people who searched for crossword software and need an offline XWord client under GPL-3.0. Upstream remains at mrichards42/xword. Subscription newspaper apps stay optional for archives and are never required for a local .puz habit.
When Releases change which OS assets appear, re-check the live list before you refresh a lab image. Prefer the same tag family across Windows and macOS desks whenever both assets still ship together. That habit reduces confused uninstalls after a reimage weekend.