Goal for this part
Navigate with arrow keys.
Treat 07-Keyboard-Nav as the source of truth for this checkpoint. If your local tree drifted, re-clone that folder rather than mixing files from neighbors.
What you should already know
You do not need prior NW.js experience for part 1. Later parts assume you finished the earlier snapshots on the same machine.
- Node.js is installed so you can run
npm install - You are comfortable editing JavaScript and HTML files
Why NW.js fits Deckspire
NW.js runs Node and Chromium in one process—handy for a slide deck that needs both DOM and local files.
One slide per section element, fullscreen presenter mode, and keyboard nav teach structure without a SaaS deck tool.
After you run the snapshot, you should recognize the behavior described in the goal—before you move on. If the window (or server) never appears, stop and fix the run steps.
Code shape
Snapshots stay small on purpose. Look for this kind of core call as you read the folder:
fs.writeFileSync(path, JSON.stringify(deck, null, 2))How to run it
Clone the teaching repo, open 07-Keyboard-Nav, install what the README asks for, then run nw ..
git clone https://github.com/michaeldunga1/fcc-nwjs-slides.git
cd fcc-nwjs-slides/07-Keyboard-Nav
npm install
nw .Common mistakes
- Ignoring platform-specific install notes in the snapshot README
- Hard-coding paths that only work on your machine
- Skipping confirmation on destructive actions
- Mixing secondary-model IDs with primary ones