Project Overview MDE is a Polish e-commerce web application built for full-stack .NET developers to deploy and extend a production-ready storefront for diesel engine parts and commercial vehicle components. It targets workshops and fleet operators running vehicles such as the Iveco Daily, Fiat Ducato, Citroën Jumper, and Peugeot Boxer. The project solves the gap between a generic CMS and a bespoke parts catalog by providing a typed, database-backed catalog with a built-in admin panel — ready to extend without starting from scratch. Key Features Browse and purchase diesel engine parts through a fast, category-driven product catalog tailored to commercial vehicle makes and models. Manage inventory without writing code via a Blazor Server admin panel with real-time UI updates and full CRUD over products and orders. Zero-friction local setup thanks to SQLite in development — no Docker, no external database process required to get running. Consistent, maintainable UI powered by Tailwind CSS v4 with a design system derived from the MDE brand, replacing Bootstrap entirely. Secure admin access with seeded credentials, session-based authentication, and a dedicated login flow isolated from the public storefront. Production-ready architecture with clean separation between the MVC public frontend and the Blazor admin area, making deployment and scaling straightforward. Tech Stack TechnologyPurposeASP.NET Core 9 (MVC)Public-facing storefront — Razor Views, routing, controllersBlazor ServerAdmin panel — interactive components with server-side stateEntity Framework Core 9ORM — database access, migrations, seedingSQLiteLocal development database (file-based, zero config)PostgreSQLProduction database targetTailwind CSS v4 (standalone CLI)Utility-first styling — installed via winget, compiled to wwwroot/css/output.cssAlpine.jsLightweight JS behaviour (navbar collapse, dropdowns) — replaces Bootstrap JSBootstrap IconsIcon font (CDN) — retained independently of Bootstrap CSSC# / .NET 9Application language and runtime Getting Started Prerequisites .NET 9 SDK Node.js (optional — only if you prefer the npm Tailwind CLI over the standalone binary) Tailwind CSS v4 standalone CLI — install via winget: powershellwinget install TailwindLabs.TailwindCSS After installation, open a new terminal session so the tailwindcss binary is on your PATH. Installation Clone the repository bashgit clone https://github.com/your-org/MarciniakWebpage.git cd MarciniakWebpage Create the development config file The file appsettings.Development.json is gitignored and must be created manually: json{ "ConnectionStrings": { "DefaultConnection": "Data Source=mde_dev.db" }, "Admin": { "DefaultPassword": "your-local-admin-password" } } Restore .NET dependencies bashdotnet restore Apply database migrations bashdotnet ef database update On first run, SeedData.cs will automatically create the default admin user using the password from appsettings.Development.json. Run the Project bashdotnet watch run The TailwindHostedService embedded in Program.cs will automatically launch tailwindcss --watch alongside the application. The compiled stylesheet is written to wwwroot/css/output.css. The application starts at https://localhost:5001 by default. The admin panel is available at /admin. Usage Navigate to the admin panel to add your first product: https://localhost:5001/admin Log in with the seeded admin credentials, then use the Products section to create a new listing: csharp// Example: Adding a product via EF Core directly in a seed or migration context.Products.Add(new Product { Name = "Filtr oleju Iveco Daily 2.3 HPI", PartNumber = "504179764", Category = "Filtry", Price = 49.99m, Stock = 120, Compatible = new[] { "Iveco Daily", "Fiat Ducato 2.3" } }); await context.SaveChangesAsync(); The Blazor admin panel reflects inventory changes in real time without a page reload. The public MVC storefront reads from the same database and renders product listings, category filters, and part compatibility tables server-side via Razor Views. Project Structure MarciniakWebpage/ ├── Components/ # Blazor Server app host and admin components │ ├── App.razor │ ├── Routes.razor │ └── Pages/ │ ├── Admin/ │ │ ├── Dashboard.razor │ │ ├── Products.razor │ │ └── Orders.razor │ └── Shared/ │ └── AdminLayout.razor ├── Controllers/ # MVC controllers for the public storefront │ ├── HomeController.cs │ ├── ProductsController.cs │ └── AccountController.cs ├── Data/ │ ├── AppDbContext.cs │ └── SeedData.cs ├── Models/ │ ├── Product.cs │ ├── Order.cs │ └── ViewModels/ │ ├── LoginViewModel.cs │ └── ProductListViewModel.cs ├── Views/ # Razor Views for the public MVC frontend │ ├── Shared/ │ │ ├── _Layout.cshtml │ │ ├── _Navbar.cshtml │ │ └── _Footer.cshtml │ ├── Home/ │ │ └── Index.cshtml │ ├── Products/ │ │ ├── Index.cshtml │ │ └── Detail.cshtml │ └── Account/ │ └── Login.cshtml ├── wwwroot/ │ ├── css/ │ │ ├── input.css # Tailwind source — edit this │ │ ├── output.css # Compiled output — gitignored │ │ └── site.css # Global custom styles │ ├── js/ │ │ └── site.js │ └── images/ ├── appsettings.json ├── appsettings.Development.json # Gitignored — create manually (see Getting Started) ├── Program.cs # App entry point + TailwindHostedService └── MarciniakWebpage.csproj Contributing Contributions are welcome — whether that's fixing a bug, improving the UI, or adding new catalog features. Before opening a pull request, please create an issue first so we can discuss the change and avoid duplicated effort. Fork the repository, work on a feature branch, and submit a PR against main with a clear description of what was changed and why. All contributions should follow existing naming conventions and include a brief test or manual verification step in the PR description.