The Vi blog
Articles about keeping a project board honest: how finishing a task in the IDE can update the board, why boards drift away from the code, and what changes when task execution moves into the IDE.
No articles in English yet — the first one is being written.
What this blog covers
Three subjects, all of them about the gap between what a repository already knows and what a project board shows.
Commit & Close
Finishing your step on a task from the commit that completed it, without leaving the editor.
Git project management
Branches, pushes and reviews read as the real record of progress on a project.
IDE project management
What a task board looks like when it lives beside the code instead of in a browser tab.
About this blog
What is the Vi blog about?
The Vi blog covers Git-aware project management — keeping a project board connected to real development work, with each task tied to its own commits and finished from the IDE. The articles are written for software teams who already use Git every day and want the board to reflect their work without a second round of manual updates.
Where else are these articles published?
Articles are cross-posted to DEV (dev.to) with a canonical link back to useviapp.com, so this site stays the original source and search engines credit it rather than the copy.
How often do new articles appear?
New articles appear when there is something concrete to document — a shipped capability, a measured result, or a question that keeps coming up from teams. There is no fixed publishing schedule.
See it on your own repository
Install the IDE plugin, connect a project, and move a task forward from the commit that finished your part. The free plan needs no card.