On build, the project structure will be mirrored into the documentation project
For each file in the target project, a docs file will be automatically generated
For each file in the target project, a file in the docs project will generate the same file, but instead of copying the contents, it will create void method stubs for each public method in the class that it represents. The developer can then fill in the void method with a coded example.
For each example that is generated, a markdown file template will also be generated so that it will be emitted to the printable document on build.
With each build, ensure that the docs project is still in sync with the target project, preserving any additions by the developer.
Based on @dasjestyr's suggestions in https://github.com/defrancea/Projbook/issues/48, consider having this behavior: