Anyway, here’s how I solved this. This workaround is kind of ugly and beautiful at the same time lol:
First, I cleared the 404 in its entirety (to make it load faster), and added the following action on page load:
Thus, navigating to mydomain.com/vova/projects (for example) redirects to mydomain.com?path=vova/projects
On the index page’s load, the (free) Router plugin replaces the path in the browser with the one it received from the 404 page:
Now you can navigate within your single-page app by parsing Router’s path list as exemplified in @ZeroqodeTeam’s demo project
One thing to note is that the router Plugin for some example doesn’t catch up 1st Path/2nd Path in this case, but does catch the “Path list” parameter. Note that “1st Path” in this case is its item #3. Confusing, I know.
Anyway, this seems to work.