What you are building
Inkline is a text editor you assemble in twelve short stages. The teaching stack is Electron (JavaScript, Electron, HTML/CSS). By the end you should understand the shell, the data you persist, and the everyday workflows people expect from this kind of app.
Electron is how many shipping editors wrap Chromium and Node. You get a desktop window with web UI and file-system access from the main process.
A textarea, tab strip, and menu bar map cleanly to HTML. Keep file I/O in main/preload—never trust the renderer with raw paths unchecked.
Work in order. Early folders are intentionally small so you can see the window (or server) boot before features pile on. From the data-layer part onward, each snapshot should still run after you install dependencies.
Read the goal, clone the matching GitHub folder, run it, then skim the code against the notes below. If something fails, fix the run path first—most “bugs” on day one are the wrong directory or a skipped install.
Parts in order
Each chapter below is one checkpoint. Open a part when you are ready for that feature—not all at once.