All solutions

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

In regards to styling using TailwindCSS, I'm improving my notions of when it comes to what should be gathered/organized in the tailwind.config file, and what shouldn't. I'm also enjoying my improvement when it comes to debugging front-end code; I'm getting quicker.

For the next project, I may not use SvelteKit; I ended up "over engineering", as I just had to build a landing page. Svelte only would have been enough. For the next project, I also want to create a more accessible structure; I still have to improve my "accessibility senses/notions".

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

For the first time, I used CSS key-frames + transitions; well, by reading their functioning logic, I was able to apply a smooth transition for the mobile drop-down menu. Working with the slider buttons also wasn't that easy, as, depending on the screen size, it has to appear on one section rather than another. I ended up creating two very similar structures, and, depending on the size of the screen, I changes their display value to either show or hide on desktop/mobile screens; I probably should improve that.

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

I'd love tips on how to structure a smooth slider/carousel, using pure CSS; I struggled on this front. I'd also enjoy comments on the CSS units I ended up using; I may have chosen not the ideal units for different jobs.

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

Well, I'm proud to not really have had significant difficulties when creating this intermediate-level challenge.

I'm quite happy that I have used Svelte/SvelteKit for the first time; of course, I still don't have significant hands-on experience to compare against another framework like React, but, for this 1st experience, Svelte was simpler to get things done, especially considering state change/observability, than what I'm used to in ReactJS land.

For the next projects, I'm intending on not using so much of pixels as the base unit of sizing; there are a few other units, especially 'em' and 'rem', and I intend on using them, for the cases in which it makes sense.

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

Keeping the aspect ratio of the crew screen images; it was challenging because I had to deal with different images with different dimensions, and how I could handle that wasn't obvious at first glance.

Deploying a Svelte app to production took a few tries as well, it was particularly annoying to do that on GitHub Pages; on Netlify, the deploy process was way smoother.

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

For people with experience using Svelte, I'd love for you to take a look at how I have used the framework; nothing fancy for now.

I'd also enjoy feedback on my TailwindCSS usage; guess I could've gathered more cross-page styling in the tailwind.config file, in order for greater reuse.

My use of pixels throughout the project; I'm still to really understand the use cases for other size units, so comments on that would also be helpful.

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

Well, I did everything using pure HTML5, CSS3 and JavaScript, no library needed, and I feel good about that. I feel like, for the vast majority of projects, that's simply enough.

Regarding a different approach, well, I'd probably use the BEM pattern to better organize my CSS stuff. I'd probably try a mobile-first approach as well.

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

Validating the user input and replacing the info cards was something not obvious at first glance, but gladly JS nowadays offer, built-in in its DOM API, methods that easily get the job done (for more details, check out the README of this project, on Github).

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

I used pixels as the main unit of measurement, for most of the sizing I did; not sure if using em, or rem, for example, are generally better approaches.

I could've used more fitting methods, maybe, when validating the user input.

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

Well, it was a very simple problem, so I don't think there's much room for improvement. Overall, I'd say that I could keep an eye on accessibility principles, since I'm aware of none of them. I'm not sure if I used the correct HTML semantic tags for the job, so that would, maybe, be something I'd change.

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

None

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

I used a tag for the bottom text, but I'm not sure if that was a good decision. Also, In order to align the QR code image, I used a wrapping for the job, but probably I could've centered the , in the top section, without using an extra .