mvc and template

[tslxxcxy]

Note: consider using Discussions to open a conversation about new features…

🚀 Feature Request
being a new BlackSheep-er ,createing a BlackSheep project ,i have some ambiguity ider,if use MVC project ,not use api in the MVC,or if use another (pip install blacksheep uvicorn),not use MVC ? would give me some advices about mvc and api and template (the best practice).

[RobertoPrevato]

Hi @tslxxcxy
The MVC project template is ideal when you want to build web applications that can serve both dynamic HTML pages and APIs. It provides a folder structure ready for controllers, views (using Jinja templates by default, and allowing alternative solutions), and serving static files, making it easier to implement server-side rendered websites.

In contrast, the API project template is streamlined for building RESTful APIs only, without view rendering or UI scaffolding. Use it when your application is purely backend and will be consumed by clients like SPAs, mobile apps, or other services.

Choose MVC when:

• You need to render HTML views on the server.
• You want to handle user interactions via forms.
• You require a mix of web pages and API endpoints.

Choose API when:

• You only need to expose data/services via HTTP endpoints.
• Your frontend is a separate SPA or mobile app.

In summary, the MVC template is meant for full-featured web apps with UI, and the API template for backend-only services.

---

Personally, I often choose the API Project template for my closed source projects built with BlackSheep because usually I build front-end SPAs using Vue.js and TypeScript (I don't care about server side HTML rendering). The API template can be used to serve static files, if desired.

[tslxxcxy]

That’s so kind of you—thanks a ton! got it .using the built-in browser power ,not rendering the server .Thanks so much!