1. In the structured example, I decided to name my files this way because I felt it is more convenient, for example when you navigate in your code editor. Furthermore I got inspiration from Angular2+'s naming conventions. But in fact you can name your "actions" and "routing" files as you want, but you have to set in Lumie's configuration to not search for a "routing configuration" in those files. This is why a I told Lumie to exclude all .action files. So if you want to name all your actions files: "action.js", you have to exclude: "action.js".
2. You are right, this is a good point. This could be the object of my next PR
3. You can do it the same way as others, you can use whatever routes names you want. I'll add another example to illustrate it
I've made the changes to fix the broken links. Don't hesitate if you have any others questions or tell me if I was unclear in my answers