How kayamuhammet/simplenotesapp works
Project type and purpose
• This is a monolithic, full-stack web application built on ASP.NET Core MVC (C#).
• Purpose: provide a user-friendly note-taking and management system with features such as authentication, categorization, favorites, PDF export, email verification, password reset, localization, and responsive UI.
File structure
• Top-level folders and roles:
• Controllers: handle incoming HTTP requests (Account, Auth, Category, Notes, Home, Error, SharedResource)
• Views & ViewModels: Razor pages and strongly-typed view models for rendering HTML
• Models: domain/entities (User, Note, Category, AuthResponse, error models, etc.)
• Services & Interfaces: business logic layer (IEmailService + EmailService)
• Data: EF Core DbContext (AppDbContext) for database access
• Resources: .resx localization files for Turkish/English
• wwwroot: static assets (CSS, JS)
• Program.cs & appsettings.json: host & middleware configuration, DI setup, connection strings, JWT & SMTP settings
README insights
• Architecture patterns: Layered (Presentation → Business/Services → Data) + MVC
• Tech stack: ASP.NET Core MVC 7.0, EF Core, SQLite, Identity + JWT, SMTP email, Localization, Bootstrap 5
Main components and relationships
A. Client / Presentation
• Browser (HTML/CSS/JS) ←→ ASP.NET Core MVC (Controllers → Views + ViewModels)
• Static file server (wwwroot) delivers CSS/JS assets to the browser.
B. Application / Business
• Controllers inject Services (EmailService, IdentityManager, PDF generator)
• Localization middleware reads .resx Resources → Controllers via IStringLocalizer
• Authentication & Authorization via ASP.NET Identity + JWT
C. Data / Persistence
• Services & Controllers call AppDbContext (EF Core) → SQLite database
• Entities in Models map to tables (Users, Notes, Categories, etc.)
D. External services
• SMTP server for email verification & password reset
• (Optional) PDF engine library (internal or third-party NuGet)
Interaction flow example (User registration):
1. Browser → POST /Account/Register with form data
2. AccountController validates ViewModel → creates ApplicationUser via UserManager
3. Generates email token → EmailService.SendAsync(token) → SMTP
4. Controller returns confirmation view
Architectural patterns and principles
• Layered Architecture: clear separation Presentation → Business → Data
• MVC pattern: Controllers + Models + Views
• Dependency Injection: services, DbContext, localization, email, JWT configured in Program.cs
• Convention-based routing & folder structure of ASP.NET Core MVC
• Use of EF Core migration / Code-First approach