This is where the confusion comes in though. Front-end USED to mean the HTML, CSS and text copy and back-end was anything on the http request.
TODAY front end (imho) also requires form validation, dynamic update of DOM based in user actions, management of the data store, local storage strategy to work offline, async fetch and post data without a page refresh, manipulation of data from an API endpoint that is not in quite the right format
All if this requires extensive knowledge of JS and/or frameworks, computer algorithms, and entity modelling. If you include the new WASM technology then you will also need to know A LOT of .net/python/rust/go
This is where the confusion comes in though. Front-end USED to mean the HTML, CSS and text copy and back-end was anything on the http request.
TODAY front end (imho) also requires form validation, dynamic update of DOM based in user actions, management of the data store, local storage strategy to work offline, async fetch and post data without a page refresh, manipulation of data from an API endpoint that is not in quite the right format
All if this requires extensive knowledge of JS and/or frameworks, computer algorithms, and entity modelling. If you include the new WASM technology then you will also need to know A LOT of .net/python/rust/go
All of that was either in play a decade ago or was just coming out, and I can speak from experience that you don’t need to learn all of that.
Frameworks exist to help accelerate implementation of most of the features you listed.