How kantrun/quanlychuyenmon works
This is a .NET 9 Blazor telemedicine landing page, not a clinical workflow system: visitors view teleconsultation, specialist-directory, health-tracking, trust, and app-download content, then follow configured calls to action. The request path is hosted by ASP.NET Core and rendered through Blazor routes and page components; landing content is supplied by a singleton service using in-memory examples. The README explicitly excludes patient-data storage, a database, CMS, API, and real appointment booking. Component wiring beyond the sampled host and service is inferred from the tree and product description.
Main entry points: Home.razor Landing page · Program.cs ASP.NET host · Routes.razor Page routes · App.razor Blazor app
Components 22
Web entry and routes
- ASP.NET host
src/telemedicine-landing-page/Program.cs - Blazor app
src/telemedicine-landing-page/Components/App.razor - Page routes
src/telemedicine-landing-page/Components/Routes.razor - Main layout
src/telemedicine-landing-page/Components/Layout/MainLayout.razor - Login page
src/telemedicine-landing-page/Components/Pages/Login.razor - Registration page
src/telemedicine-landing-page/Components/Pages/Register.razor
Landing experience
- Landing page
src/telemedicine-landing-page/Components/Pages/Home.razor - Hero and CTA
src/telemedicine-landing-page/Components/Sections/HeroSection.razor - Video consultation
src/telemedicine-landing-page/Components/Sections/VideoConsultationSection.razor - Specialist directory
src/telemedicine-landing-page/Components/Sections/SpecialistDirectorySection.razor - Health tracking
src/telemedicine-landing-page/Components/Sections/HealthTrackingSection.razor - Creative features
src/telemedicine-landing-page/Components/Sections/CreativeFeaturesSection.razor - Trust signals
src/telemedicine-landing-page/Components/Sections/TrustRailSection.razor - App downloads
src/telemedicine-landing-page/Components/Sections/AppDownloadSection.razor - Footer links
src/telemedicine-landing-page/Components/Sections/FooterSection.razor
Content and configuration
- Landing content service
src/telemedicine-landing-page/Services/LandingPageContentService.cs - Content models
src/telemedicine-landing-page/Models/LandingPageContentModels.cs - CTA link options
src/telemedicine-landing-page/Models/LandingPageLinksOptions.cs - Application settings
src/telemedicine-landing-page/appsettings.json
Browser interactions
- Browser motion
src/telemedicine-landing-page/wwwroot/js/animations.js
Other components
- Visitor
- App stores
Connections 21
- Visitor → ASP.NET host: requests page
- ASP.NET host → Blazor app: maps components
- Blazor app → Page routes: renders routes
- Page routes → Landing page: selects page
- Page routes → Login page: selects page
- Page routes → Registration page: selects page
- Landing page → Main layout: uses layout
- Landing page → Hero and CTA: renders section
- Landing page → Video consultation: renders section
- Landing page → Specialist directory: renders section
- Landing page → Health tracking: renders section
- Landing page → Creative features: renders section
- Landing page → Trust signals: renders section
- Landing page → App downloads: renders section
- Landing page → Footer links: renders section
- ASP.NET host → Landing content service: registers service
- Landing content service → Content models: returns content
- ASP.NET host → CTA link options: binds options
- Application settings → ASP.NET host: provides configuration
- Browser motion → Visitor: animates page
- App downloads → App stores: links to stores