All solutions

What are you most proud of, and what would you do differently next time?

I'm pretty happy with the auto-calculation that occurs once all required fields have valid data. I think the validation process could probably be better, but this works pretty well for what's needed here. I contemplated clearing out the custom tip percentage when another option was selected, but opted to leave it alone.

What challenges did you encounter, and how did you overcome them?

The only real challenge I encountered here was disabling the reset button when pressed. I eventually just gave up and let it always be enabled, which is probably better UX anyways.

Otherwise, no real challenges, just digging more into a couple JS events, and slowly finding a better flow for naming things and organizing the JS. I don't think this is perfect, but I think it's better than what I've done previously, at least.

What specific areas of your project would you like help with?

Any feedback is greatly appreciated.

What are you most proud of, and what would you do differently next time?

Overall, I'm pretty happy with what I came up with here. I'm not totally sold on the markup I used and how I'm referring to the various dynamic bits in javascript, but that's mostly due to the constraints of the challenge. I think in the future, when I approach a problem like this, I might explore using web components or otherwise break things up into something more maintainable.

What challenges did you encounter, and how did you overcome them?

No real challenges here to take note of. Working through how to match the styling of the cards/tiles was interesting, but just took time and experimentation to find something that worked well.

What specific areas of your project would you like help with?

Any feedback is welcome!

I'm not sure how I feel about the some of the markup I settled on. It works, but I feel like there's probably a better approach, which could help with the javascript side of things as well.

What are you most proud of, and what would you do differently next time?

I'm pretty happy with the modal display in chrome, but I'm disappointed the transition doesn't seem to work in firefox. The mobile experience could probably be better, but I'm content with what's here.

Most of this was pretty easy to throw together, and I'm mostly happy with what I came up with.

What challenges did you encounter, and how did you overcome them?

The success modal on mobile gave me some grief. I've gotten more comfortable with flexbox, but it seems it's maybe not the best solution for that component. I'm happy with what I was able to get to work, but I'm disappointed it required some margin magic rather than being able to rely on align/justify settings.

What specific areas of your project would you like help with?

Any feedback is appreciated!

What are you most proud of, and what would you do differently next time?

I'm pretty happy with the transitions for the display of the share links, and with the general layout of the code. There's a few things I'd like to look at doing a little differently for better consistency (like the layout of the footer of the card when the links show up). Maybe something to look at in the future.

What challenges did you encounter, and how did you overcome them?

Getting the image aligned right was a bit of a nightmare. I tried a bunch of things, most of which I don't remember, until I managed to get it looking right.

The pointy bit on the desktop view of the share links was new for me, but turned out to be pretty easy to implement.

What specific areas of your project would you like help with?

Any feedback is appreciated. Thanks!

What are you most proud of, and what would you do differently next time?

I really like the effect I was able with a box-shadow that uses the testimonial card's colors, and the fairly fluid responsive layout at any resolution.

What challenges did you encounter, and how did you overcome them?

The biggest challenge I had here was the layout for the author name and avatar. I would have liked a little less markup, but I think what I came up with works pretty well.

What specific areas of your project would you like help with?

Any feedback is appreciated. Thanks!

What are you most proud of, and what would you do differently next time?

I'm happy I was able to get something that works pretty well and is pretty fluid. The layout flows pretty nice from desktop resolution down a small-ish mobile display size.

What challenges did you encounter, and how did you overcome them?

The only real challenge I ran into here was working with flexbox and getting the 3 column layout working for the desktop display. I was able to get it working well by way of using a couple wrappers, but I'd really like to find a way to do this without needing to mess with the html.

What specific areas of your project would you like help with?

Any feedback is welcome. Especially with regards to what I mentioned above.

What are you most proud of, and what would you do differently next time?

Not much to call out here, in my opinion, but I'm pretty happy with the use of semantic HTML and general css names. I tried to limit how specific the styling was to the content, so it could, in theory, be used for other types of content, but using the same style/coloring.

What challenges did you encounter, and how did you overcome them?

The only real challenge I had to work through here was the working through making the design responsive. I ended up relying on fixed dimensions. I'm mostly happy with what's here, but I would really like to figure out how to allow for a bit more dynamic resizing of the content while preserving aspect-ratio of images and such.

What specific areas of your project would you like help with?

Any feedback is welcome. I'm far from an expert in frontend dev, but I'm definitely getting more confident from working through these projects.

What are you most proud of, and what would you do differently next time?

I was able to get the layout to be pretty responsive down to a fairly small mobile size. It does eventually break down, but I think it fails at a point that's narrow enough not to really care about.

I'm not sure how to feel about how I handled the nutrition info. I like how it looks, but I'm not sure a bunch of divs is the right solution, but it felt better than using a table, since there's nothing inherently tabular about that data.

What challenges did you encounter, and how did you overcome them?

The only real challenge I ran into here was how to deal with the nutrition info in a grid. I ended up just styling it with a grid and some css magic. I'm pretty happy with the css side of things, but not so sure on the html. Everything else wasn't too difficult.

What specific areas of your project would you like help with?

As I've mentioned in previous projects, any feedback is greatly appreciated. I have many years experience in backend development and such, but frontend experience has been pretty light.

Suggestions on how to better markup the nutrition data would be most welcome.

What are you most proud of, and what would you do differently next time?

I managed to get nearly pixel perfect matching with the design, but then I decided to follow some advice on a previous project of trying to use rem instead of px for widths and such. I did end up leaving px for the widths, but transitioned all the other px values that made sense to be rem to rem, and it still looks pretty good. I want to get better at responsive resizing, and I might try approaching things like the social links as a grid next time to provide a better resize experience.

What challenges did you encounter, and how did you overcome them?

I ran into some odd behavior when testing responsive layouts and the top of content being cutoff. Turns out I forgot margin: auto. I ended up comparing behavior from previous challenges to try and figure out why it wasn't working as intended.

What specific areas of your project would you like help with?

Nothing in particular, and feedback is greatly appreciated. Still working on fully grasping how to do UI well, and trying to keep accessibility in mind, though it hasn't yet been a focus.

What are you most proud of, and what would you do differently next time?

I'm pretty happy with the HTML markup used, and tried to utilized semantic rules as much as possible. I think there might be a bit more that could be done, but I'm happy with what I came up with. Getting the layout right has always been a struggle for me, but I feel like what I ended up with is pretty decent here.

What challenges did you encounter, and how did you overcome them?

Layout is still a challenge, but I'm slowly understanding how things work together. I struggled a bit with the alignment of the card content, and had resolved to using a grid layout. I ended up changing that up at the last moment to use flexbox instead, and relied on a fixed padding size.

What specific areas of your project would you like help with?

Any feedback is welcome. I have 10+ years as a backend developer, and a couple decades in general programming experience, but UI and CSS/HTML has always been a weak point.

What are you most proud of, and what would you do differently next time?

Just getting familiar with CSS/HTML layout stuff. I forgot what I wrote here initially, and accidentally overwrote it all with the blog preview card submission.

What challenges did you encounter, and how did you overcome them?

No real challenges here other than getting more familiar with CSS/HTML.

What specific areas of your project would you like help with?

Any feedback is welcome. I have 10+ years as a backend developer, and a couple decades in general programming experience, but UI and CSS/HTML has always been a weak point.