How gabrielvesal/library-crud works
Project type and purpose
• This is a full-stack, ASP.NET Core MVC web application called “Library CRUD,” consisting of two Visual Studio projects in one solution:
• Library (the web app)
• LogicLibrary (a class‐library containing domain models and business‐logic services)
• Its purpose is to provide Create/Read/Update/Delete operations over a collection of books, with a JSON file (Books.json) as the data store (or optionally EF for persistence).
File structure
• Top-level: Library.sln, README.md, LICENSE, two project folders:
• Library/ – ASP.NET Core MVC project
– Controllers/HomeController.cs
– Views/Home (Index/Add/Edit/View/Remove) + Shared layouts
– wwwroot (CSS, JS, Bootstrap, jQuery assets)
– appsettings.json (+ Development override)
– Program.cs (host builder)
– Books.json (flat-file store)
• LogicLibrary/ – .NET class library
– Models/Book.cs
– Services/BookManager.cs
• No database folder, so data layer reads/writes JSON directly (or uses EF if swapped in).
README for additional insights
• Confirms stack: ASP.NET Core MVC, C#, optional EF, Bootstrap
• Describes core CRUD features
• Shows data model (Book)
Elements
• Blue for UI components (Browser, Views, static assets)
• Green for server components (Controllers, Services)
• Orange for data (JSON file)
• Gray for external frameworks (.NET, Bootstrap)
• Rectangles for apps/services
• Hexagon or cloud for external libraries/frameworks
Detail without over-splitting
• Logical piece (routing, middleware, views, controller, service, model, data file)
• Don’t fragment into internal build artifacts (bin/obj folders)
• Assembly boundary between Library and LogicLibrary