Services like GitPod are about serving a development environment remotely.
The blogposts discusses dotfiles as a social thing. e.g. you should be able to fork someone's dotfiles repository as a good starting point for your dotfiles.
The idea in the blogpost is a suggestion which combines this idea of sharing dotfiles, with the idea of being able to quickly spin up a developer environment.
Project-specific configuration is just that, project-specific configuration, and you would not call it dotfiles anymore.
Also by defining dev environments in code that can be deployed on-the-fly (aka infrastructure-as-code), that allows you to do things like share the code with others, who can "fork" your dev environment with their own customizations. This seems to be what OP's article is about.