Rebuild site as ASP.NET Core MVC editorial platform (final)

[Code-311]

Motivation

• Replace the previous portfolio-oriented code with a disciplined, production-shaped ASP.NET Core MVC content platform that matches the thesis, tone, and sitemap requirements.
• Provide a minimal, server-rendered editorial CMS with DB-backed content, admin CRUD, and safe Markdown rendering for long-form content.

Description

• Project shape and persistence: converted to a single ASP.NET Core MVC app with ApplicationDbContext (inherits IdentityDbContext<ApplicationUser>), EF Core entity configurations, and environment-based provider switching to use InMemory in Development and PostgreSQL in non-development via UseNpgsql/UseInMemoryDatabase in Program.cs.
• Domain model and assets: added explicit domain entities under Models/Domain (Essay, FrameworkModel, Tool, ToolQuestion, MediaItem, UploadedAsset, StaticPage, SiteSetting) with EntityBase and PublishableEntityBase base classes, and an UploadedAsset byte-array storage model plus DB streaming endpoint at Controllers/AssetsController.Get.
• Identity and seeding: added ApplicationUser, ASP.NET Identity wiring, and a DatabaseSeeder that creates an Admin role and seeds a single admin user with the password read from config (Seed:AdminPassword, default Password123!) and starter content aligned to the platform thesis.
• Admin area and admin UX: implemented Areas/Admin with role-protected MVC controllers, viewmodels, and Razor views for CRUD/publish workflows for Essays, FrameworkModels, Tools, ToolQuestions, MediaItems, UploadedAssets (upload), and StaticPages, keeping admin layout separate from public site navigation.
• Public site and routes: added public controllers and typed viewmodels and views to support /, /writings, /writings/{slug}, /models, /models/{slug}, /tools, /tools/{slug}, /media, /about, and /contact and ensure DB-backed rendering of Markdown content.
• Markdown and services: added a small IMarkdownRenderer implementation using Markdig (HTML disabled) and an IAssetService/AssetService to save uploaded files into the DB; wired both via DI in Program.cs.
• Theme & visual: implemented dark/light only theme behavior (system default + persisted user override in localStorage), removed accent switching, and added wwwroot/img/Logo-Out.svg integrated to respect CSS variables for light/dark rendering.
• Razor/viewmodel alignment: replaced old-site models with explicit domain types, added typed list/detail viewmodels (ListPageViewModel<T>, DetailPageViewModel<T>, StaticPageViewModel) and updated/removed stale partials to avoid portfolio-era references.

Testing

• Attempted dotnet build but it failed because the container lacks the .NET SDK (dotnet not available), so full compile/runtime verification and Razor compile checks were not executed here (failure).
• Ran an automated search for stale portfolio-era terms with rg -n "Atelier Vertical|\bWork\b|Archive|Thoughts|portfolio|studio" and found no active matches beyond the README (success).
• Performed an automated scan script over Razor files to detect missing @model declarations and other basic view-model presence (script executed and returned without errors, indicating a basic surface-level alignment pass succeeded); full Razor compile validation requires dotnet build.
• Recommendation: run dotnet build, dotnet ef migrations add Initial (or verify migrations), and run the app in a dotnet-enabled environment to confirm zero Razor compile errors, DB migrations for PostgreSQL, and seeded admin login end-to-end.

---

Codex Task

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.