21–30 of 51 posts
Caveat to most of the answers so far - you can read Javascript books until you're blue in the face, you need to build stuff as much as possible.
Earlier quoted context omitted.
While I mostly agree... there's something to be said for a simpler, server-driven stack. HTMX is particularly interesting as a point for server driven integration(s). Many (most) apps are for internalized use at a given company... there's a lot of corporate development and most of these applications can scale perfectly fine with a relatively simple stack backed by a traditional RDBMS. It's usually somewhere between 1…
Sure, nothing wrong with a simple server-side stack. But even then, you probably wouldn't write it (today) by spinning up Microsoft SQL Server on a bare-metal machine so that your sysadmin can maintain its records with MS Access, then writing a bespoke CMS by creating your own prepared SQL statements from scratch, all while making sure your designer knows Frontpage and that you have a WAP version ready to roll out so…
Aside: Right now, exploring HTMLX + server-side yew for rendering in rocket (rust), which could be very interesting. Usually do https termination at the platform, or reverse-proxy via Caddy. And I'm a proponent of containerizing all the things (Docker).
https://www.amazon.com/DOM-Scripting-Design-JavaScript-Docum... 1. If you want to be good at this start with a solid foundation. The compile target of the browser is the DOM (Document Object Model). 2. Read about accessibility: https://www.w3.org/WAI/standards-guidelines/wcag/ Understanding accessibility will influence why things are done in certain ways and will make clear the difference between presentation and dev…
You don't need to search SEO spam for that stuff; ChatGPT knows it. I think Vite and React would be a good place to branch out to.
I learned HTML and CSS mainly from MDN, so that's where I suggest you look. As for stuff I use in css most often I can only recommend a few articles and such. Learn how to use Flexbox and CSS Grid though for sure (as those are the two most modern ways to layout an HTML page) as well as CSS Positioning [0] (which is some of the older ways to lay things out). [0]: https://alistapart.com/article/css-positioning-101/ For…
I remember "JavaScript: The Good Parts" by Douglas Crockford touched some parts in depth. Also "You Don't Know JS Yet" has some depth in it https://github.com/getify/You-Dont-Know-JS
You don't know JS series didn't sit well with me. It tries to lead the reader through some a-ha moments, except those are pretty individual. But it might work for someone else.
https://www.amazon.com/DOM-Scripting-Design-JavaScript-Docum... 1. If you want to be good at this start with a solid foundation. The compile target of the browser is the DOM (Document Object Model). 2. Read about accessibility: https://www.w3.org/WAI/standards-guidelines/wcag/ Understanding accessibility will influence why things are done in certain ways and will make clear the difference between presentation and dev…
It does a great job at explaining intermediate/advanced caveats and gotchas along the way.
I learned HTML and CSS mainly from MDN, so that's where I suggest you look. As for stuff I use in css most often I can only recommend a few articles and such. Learn how to use Flexbox and CSS Grid though for sure (as those are the two most modern ways to layout an HTML page) as well as CSS Positioning [0] (which is some of the older ways to lay things out). [0]: https://alistapart.com/article/css-positioning-101/ For…