One of the delights of being a “full stack” web geek is that every week you get to do something different.
(Full stack, for all my untechy friends’ benefit, is when you handle everything from server configuration, to application administration, to server-side technology, to client side rendering. That’s all g(r)eek for, “You do everything and anything that’s necessary to get a site up, running and looking good on people’s screens.)
This week it’s jQuery.
When you look at a website these days, there are generally three components that go into making it look how it looks and do what it does.
- There’s the HTML (Hyper Text Markup Language). That’s like the skeleton the whole thing hangs on. It’s the page’s structure and content.
- There are CSS (Cascading Style Sheets). That’s like the skin. It’s what gives the site it’s look and feel. It’s shapes and colors and textures. Skin.
But you still have to fit that into all the other stuff that’s going on around the web page. You still have to script (or “chain”) all those mini programs together in a way that it makes sense and works in the right order.
This week, that’s my job. Two projects, actually:
- Use jQuery to make a page that can call up any number of photo galleries by clicking on various icons. Bonus if you can automatically open the right gallery when the page opens, depending on what was clicked on the previous page!
- Use jQuery to make information change inside a box depending on which “hot spot” gets hovered over on a picture.
Neither of these are really “hard” to do. Most “front-end” developers would probably call them routine.
Even so, they’re nice diversions from my usual drill.