Weapsy.Host is a better name for the presentation project.

[mikeandersun]

IMHO Weapsy.Host is a better name for presentation project.

[lucabriguglia]

Agree, changing the name it's something that I had in mind for a long time now. I'm still undecided between Weapsy.Web, Weapsy.Host or Weapsy.Host.Web. Eventually Weapsy is going to be a Headless CMS, everything will be accessible via API. The long term plan is to potentially have multiple hosts.

[ElderJames]

How about Weapsy.Web.Host ? :-)

[lucabriguglia]

Another candidate :-)

[araqiel2552]

I prefer Weapsy.Web. We understand directly that it is the content of the website.

[lucabriguglia]

Another dilemma regards the Web API. At some point I would like to be able to host 2 different applications for web UI and web API. Weapsy.Web and Weapsy.API?

[araqiel2552]

Yeah. For me it's a good idea.

[mikeandersun]

I Think a project like Weapsy.Mvc for APIs (Weapsy.Api) and a project for hosting concepts Weapsy.Host So we can refrences Weapsy.Api in Weapsy.Host and host web and api on one website. Anyone can make a separation Host project for hosting APIs and live it for a production environment (api.anydomain.any).

[lucabriguglia]

I'm also going to move the projects into sub folders that match the solution structure.

[lucabriguglia]

Hi @mikeandersun, are you able to create a proof of concept?