We are positioning Red Hat DevSpaces to our customers as a full replacement for any local editor, i.e. users can just use a browser for development and do not need to install anything local (other than VPN clients perhaps). And we do deal with an audience that might have not yet used Git and do not have VS Code or another editor used, yet.

With the release of 3.0 we have a hard time to make that argument as we do not understand the Getting Started workflow. The docs describe that a user can start by just specifying a Git repo url that has a devfile, but how did that repo get there in the first place? This feels like a chicken-egg problem as to be able to create a git repo with a devfile I need to be able to create a workspace with a devfile in the first place.

I therefore feel that it is essential to bring back the devfile editor to the dashboard where a new user can select from a template and write the devfile they need to start that new project.  This would also be import for making any changes and fixes to a devfile before starting the project. What if the workspace does not start up because of an issue with the devfile? Do users have to install and configure VS Code to fix it first before they can use Dev Spaces?