The library
The left side of the window lists every project and its devlogs, as folders and files. A project’s game page, when it has one, sits first with a gamepad icon, then its template, then the devlogs. A dot at the end of each devlog’s row says whether it’s live on itch, a draft there, or only here (Saving to itch).
Making things
The folder button at the top makes a new project. The + that appears when hovering a project (or Ctrl+N) adds a row for a new devlog: type its name and press Enter, or press Esc to change your mind. A project’s game page starts from its right-click menu, with New game page.
Keeping it tidy
Double-click a name, or press F2, to rename it. Drag devlogs and projects to put them in the order you want, until you do, names sort as people count, so 0.2 comes before 0.10. The arrow beside a project folds it shut.
As a library grows, the filter box at the top narrows it down as you type. A devlog stays in view when every word typed is in its name or its project’s, so canyon 0.4 finds it, and case and accents don’t matter. Esc clears it.
The right-click menu
On a devlog, the menu also offers:
- Show in file manager, which opens its folder with the file selected
- Copy path, the file’s full path
- History…, its earlier versions
- Make a draft on itch…, a new post on itch for it (Saving to itch)
- Bring in from itch…, on a game page or a devlog linked to its post: its text as it is on itch now (Importing from itch)
- Move to trash…, which uses your system’s trash, after asking, so a mistake can still be undone there
History
While you write, a copy of each devlog is kept every few minutes, and another just before anything replaces it whole. History… lists them; choosing one puts it back, as a single edit that Ctrl+Z undoes. Every copy from the last day stays. After that only one a day is kept for a month, then one a week, so an in-between version from long ago won’t be there. The copies taken before something replaced the devlog are always kept.
Saving
There’s no save button. Devlogs are saved a moment after you stop typing, when you open another one, and before the window closes. The top bar says whether the open devlog is saved. Going back to a devlog opened earlier finds it where you left it, same line, same scroll.
Moving the library
Library folder button, at the bottom of the library panel, shows where your projects are kept and lets you put them somewhere else. Choose an empty folder and the whole library moves there, images and history included. Sublime Itch keeps it there from then on, and Back to the default button brings it home again.
That’s also how to have your devlogs on more than one computer. Put the library in a folder Dropbox or google drive keeps in sync, or in a git repository, then on the other computer choose that same folder: Sublime Itch sees there’s a library in it already and uses it as it is, leaving the one it had where it was. A folder with other things in it is turned down, so your projects never get mixed in with unrelated files.
If a devlog changes on disk while Sublime Itch is open, because a sync brought in another computer’s version or another editor saved it, the app notices when you come back to its window. The new version takes the devlog’s place and yours goes into its history, one Ctrl+Z away. If you had edits that weren’t saved yet, yours are kept and saved, and the other version goes into the history instead. Nothing is thrown away either way, but two computers writing the same devlog at the same moment is still best avoided.
If the library’s folder is on a drive that’s unplugged, or in a synced folder that isn’t there, Sublime Itch says so instead of starting an empty library. Connect it and open the app again, or choose another folder.