Restructure files so theme can be used as submodule?

With hugobricks, the demo site is also the git repo that users must clone to start a new site. I can see why this is useful: users have the most up-to-date docs downloaded and available even when offline, and the maker/owner doesn't have to maintain both a demo-site git and a theme git.

With lots of other themes, the files in the git are structured differently, making it possible to add a theme via the git submodule function (for example: `git submodule add https://github.com/jhvanderschee/hugobricks themes/hugobricks`. )

The main benefit is that updating your own theme from the submodule git is extremely easy. With the current setup, I struggle to find a way to update my site to the latest version in an easy way.

It's common practice to add a folder called /ExampleSite/ to the theme git, so new users can copy those files and get an understanding of how the theme works. Could this be an option for hugobricks too? Only thing is that the theme git must be seperate from the demo-site git, and an updated demo-site must be copied to the ExampleSite folder too.

Is this something you would be interested in to change?