P
@CoderAlchemy24
Latest solutions
Latest comments
- P@kravamax
Hi! Good job, just make the design a little closer to the original. Interesting Password Strength setting, Too weak can be seen if I select only symbols, otherwise I get Weak, I thought it was a good idea! Good luck!
- @nerdynischalWhat are you most proud of, and what would you do differently next time?
I am proud of the fact that I tried using BEM technique for this project which was a bit confusing at first but hopefully will get better with time and practice. I think there might be too much nesting of divs this time, so perhaps thats something that could be better.
What challenges did you encounter, and how did you overcome them?I feel that the validation part, in specific, trying to display error messages could be done more effectively but for this project, I just used a function to toggle a message in the DOM.
P@kravamaxGood work! For a final you could add more validation. Good Luck!
- P@jfp99P@kravamax
good work, I hope you can find solution for fix card laybels and add media query for tablet. Good luck
- @nerdynischalWhat are you most proud of, and what would you do differently next time?
I am quite proud of adding the additional tablet screen design in addition to the mobile and desktop versions. Although, the organisation of the scss/css files were not the most optimal so that would be something to improve next time, i.e. plan out from the start.
What challenges did you encounter, and how did you overcome them?There were two particular areas which I sort of had to think around the box.
-
The success message - Since no server, had to use the local storage as means to update the email address in the success message.
-
The different hero images could be perhaps better implemented. I just included all of them in the html and hid each one respectively per the device width.
P@kravamaxNice work! I could recommended add style to button and input border after Tab, also add breakpoint for tablets. Good luck!
-
- @chryspenalberWhat are you most proud of, and what would you do differently next time?
I'm most proud of how I implemented a contextual share button that behaves differently on desktop and mobile screens. It was rewarding to create a clean, responsive layout that adapts well across devices.
If I were to approach the project again, I would improve the share tooltip by adding smooth animations for opening and closing transitions.
What challenges did you encounter, and how did you overcome them?Ensuring font sizes and layout elements remained fluid. I used clamp() and flexible layout units to enhance responsiveness without relying heavily on multiple breakpoints.
What specific areas of your project would you like help with?I’d appreciate guidance on handling component state and interactivity in vanilla JavaScript, particularly for adapting elements like the share button across different screen sizes in a scalable, accessible, and maintainable way, without duplicating code.
P@kravamaxGood job. I hope you can find a solution for the toast component on mobile. I would recommend you not to nest CSS selectors more than two. Good luck!
- P@antryabovWhat are you most proud of, and what would you do differently next time?
Made a container for content using grids where I named lines and aligned content, then noticed that there were some small problems with overflow and decided to postpone this matter for a little later. For now I used the good old container.
P@kravamaxGood job! I could only recommend checking the hero images at high resolution, parts of the images are stuck to the edges
