Separate Web and API concepts?

I think that it would benefit those using this project to have an option which is API only as opposed to a traditional Web project which also includes the API within.

Pulling out controllers and views which are redundant can be tedious.

If a web project is also desired, it could be also be included. It could take a "Connected Services" dependency on the API via it's generated Swagger document.

No files, tests, or entry points are named. Start by reviewing the template's current web project structure, including its controllers, views, and generated Swagger document, then determine how an API-only option and a separate web project could be represented. Done means the project can generate an API-only variant while allowing a web project to consume it through the documented API.

Written by the indexing model from the issue text.