"A gentleman is one who never hurts anyone's feelings unintentionally"
-Oscar Wilde

I work in teams that use MVC more frequently and as a result don't know enough about the terminology of DDD but I think it's a more useful way of thinking for UX/UI

It's a secret third option, but I'd go with data-driven. I like to think about the database first and an idealized application as the friendliest way of representing its data to a user

Is there any useful way to mitigate security risk on db inserts based on hard coded strings in <script> tags?

Or is this whole plan silly

First of all: thank you, anon, for the compliment and for checking it out! Def made my day

Answer: I totally forgot to make one. I've been playing around with fend frameworks for a few years and I was way more concerned with trying to make my own spa with vanilla js to see what kinds of problems came up so I could understand them better. So seriously thanks for reminding me

There's also a bunch of other small changes I want to make and some bigger ones (like fixing header accessibility and making the skills buttons into clickable buttons), and I would have totally forgotten. I should make a list :)

I love Laravel because it is a collection of good, sturdy, battle-tested decisions and opinions from experienced devs so the framework is resilient and I never have to worry about other packages and services in the ecosystem.

I love PHP because I love writing Laravel code. I got used to PHP making me happy while Laravel was making me happy. It wasn't a love I was expecting, so I'm still learning and adjusting