I'll try to remember to bump the font up a bit more next time!
And the MVC part will primarily just be the built-in ASP.Net Core MVC (so Razor syntax in the actual view) with some simple jquery for validation, interactivity, ajax, etc. (since it's already there).
I DO want to eventually try out server-side Blazor on this project (and then client side Blazor in a different project) as a SPA. In CoreLMS, I'd like to use it when actually viewing a course (simple, isolated from the rest of the app's functionality, etc.).
Server side blazor is nice. You can even use matblazor or radzen components or just simply bootstrap for design. Btw, what's your primary programming language, c#?
I'll try to remember to bump the font up a bit more next time!
And the MVC part will primarily just be the built-in ASP.Net Core MVC (so Razor syntax in the actual view) with some simple jquery for validation, interactivity, ajax, etc. (since it's already there).
I DO want to eventually try out server-side Blazor on this project (and then client side Blazor in a different project) as a SPA. In CoreLMS, I'd like to use it when actually viewing a course (simple, isolated from the rest of the app's functionality, etc.).
Server side blazor is nice. You can even use matblazor or radzen components or just simply bootstrap for design. Btw, what's your primary programming language, c#?
"Primary" as in most used today is C#, though I'm nowhere near mastery of it.
I spent most my career in PHP and Javascript, but I've seen the light. 🤣