I'm not sure how relevant project structures are to code review, but I think they are equally as important in terms of people knowing where to find things.
There are projects like cookiecutter [1] that pre-populate a project for you so all that's left is fill-in-the-blanks so things can go where they belong from the beginning, instead of having to re-organize everything later (which might break things if there are references to them)
As I said in another thread, review is really all about adhering to standards which codify values. If one of your values is 'clear communication', then the structures you describe play right in.
I'm not sure how relevant project structures are to code review, but I think they are equally as important in terms of people knowing where to find things.
There are projects like cookiecutter [1] that pre-populate a project for you so all that's left is fill-in-the-blanks so things can go where they belong from the beginning, instead of having to re-organize everything later (which might break things if there are references to them)
[1] https://github.com/audreyr/cookiecutter