9. Interim Conclusion

The twenty-five examples have introduced the concepts we need to write the [RdvMedecins] client:

Concept	Where it will be used in the case study
components, inputs, outputs, [model()], projection	the navigation bar, form fields, windows
signals, [computed], [effect], [linkedSignal]	all pages; the calendar, which follows the address
forms with signals, validation, custom controls	login, doctor and client profiles, account creation, user account
pipes	formatting of dates, times, and names
services and dependency injection	logged-in user, messages, confirmation window
the router and its guards	pages, permissions for each role, the session to be restored after F5
[ngx-translate]	French and English, and the translation of server errors
[HttpClient], interceptor, cookie httpOnly, proxy	connection, expired session, all communication with the server
the API access layer	a file [rdvmedecins.api.ts], one method per route

The client will be the exact equivalent of the HTML application from the [NestJS] course, page by page. The difference lies elsewhere: the server no longer generates any pages; it responds in JSON, and everything related to display (pages, language, date formatting, messages) has been moved to the browser.