All solutions

Served as an introduction to 11ty templating.

Plan to redo without 11ty, as a dynamic locally-served form-based application with node.js

This one went pretty smooth.

Never used the 'fetch' function before, still not sure I understand whats going on there.

Some of the quotes have me lolling

Had a bit of a time getting the radio buttons to select correctly, that is, getting their styling to change upon hover but also figuring out how - in lieu of styling <input>s (which isn't possible) - I would go about applying style but still ultimately relying on the <input> for the form submission.

Figured out a way to make the form <inputs> not visible, but still interactive, while also changing the <label> styling - the thing that IS showing, as needed.

Having trouble getting footer p to respect the reduced font-size setting @ 475px

Used flexbox mostly..

I used 'vw' settings (calculated from rem settings) in order to accomplish element scaling.. I wanted to keep the scaling continuous/interactive instead of just hitting a breakpoint and having a whole slew of settings suddenly change. Not sure if this is a good approach or not since I know it has to be calculated continuously too

Had a little bit of trouble getting the button to not get 'springy' the 1180 and 1064px breakpoints re-adjusting its width/switching to being a flex item, added some transition to soften it

Used a combo of flex and grid

Looking for suggestions

More good practice.. Looking for input!

Updated RE footer & <a>

Still Mobile Friendly, v3 fixed the attribution links, adjusted mobile container img

Looking for any feedback on updated Challenge 2!

Looking for feedback on updated QR Component