Goal for this part
Export the preview as an HTML file.
Treat 11-Export-HTML 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 Neutralino 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 Neutralino fits Markharbor
Neutralino is a lighter alternative to Electron: a native webview with a small Go/ native backend for file access.
Split editor and live preview panes. Keep filesystem calls behind Neutralino APIs instead of Node’s fs.
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:
await Neutralino.filesystem.writeFile(path, markdown)How to run it
Clone the teaching repo, open 11-Export-HTML, install what the README asks for, then run neu run.
git clone https://github.com/michaeldunga1/fcc-neutralino-markdown.git
cd fcc-neutralino-markdown/11-Export-HTML
npm install
neu runCommon mistakes
- Ignoring platform-specific install notes in the snapshot README
- Hiding a feature in the UI without enforcing it in code
- Leaving trash/spam actions irreversible
- Forgetting a status message after a bulk action