Could you also make it dynamic? For instance, it should highlight the current day (e.g., if today is Monday, it highlights Monday in blue). It's not a big deal, but it will help refresh your understanding of JavaScript's Date concept.
What are you most proud of, and what would you do differently next time?
Sass/scss
FlexBox and grid
Position reltive and absolute and playing with alignement
and pay attention to some little details
yes ...It was beneficial and fun to take on this challenge.
Any feedback Please...
What are you most proud of, and what would you do differently next time?
I'm proud of finishing the project.
What challenges did you encounter, and how did you overcome them?
I found it challenging to figure out how to make custom input work without a button. I decided to create a button for custom input for an easy user experience.
What specific areas of your project would you like help with?
To enhance it even more, consider using an unordered list (<ul>) instead of a <div> for displaying a list of links. This is more semantically correct, improves accessibility, makes the content easier to maintain and style, and provides more flexibility.
Here's an example of how you might adjust your code:
What challenges did you encounter, and how did you overcome them?
I have a lot of problems with Angular's testing suites, I can't figure out for the life of me how to setup tests properly, it seems that it breaks on the fetch() statement to the rest api, and I have no clue how to fix it, so I did the only reasonable thing: delete all test files.
What are you most proud of, and what would you do differently next time?
Functionality and Usability:
The tip calculator efficiently calculates tip amounts and totals per person, making it a useful tool for users. The clear layout and intuitive design enhance the user experience.
Data Validation:
Using zod for schema validation ensures that the inputs are correct, which strengthens the reliability of the application. This is particularly important in applications that handle numerical data.
Responsive Design:
Utilizing Tailwind CSS allows for the creation of a responsive design that works well on both mobile and desktop devices. You can be proud of having designed an accessible and visually appealing interface.
State Management:
You have effectively managed state with React hooks, demonstrating a good understanding of the lifecycle and state management in React.
What are you most proud of, and what would you do differently next time?
This was a long but fun challenge. Added a small on hover animation. While writing this, probably i should give the body a max-width but that will affect especially the background image. I will consider it next time.
What specific areas of your project would you like help with?
Any feedback is appreciated but i would especially like to get feedback about accesibility, semantics and grid.
What are you most proud of, and what would you do differently next time?
I love coding but it can be overwhelming with the the options available. Frameworks, libraries and components no doubt make coding more efficient and less time consuming, I often wonder since most of the tools available use the base of HTML, CSS and JavaScript could a page be made with using just those three and still be efficient. I've discovered you can do it (efficiently even). Of course, there isn't much content and for the most part the page is made up of lists and paragraphs which made it easy to stick with the basics (expect for using sass/scss - which I cannot live without).
What challenges did you encounter, and how did you overcome them?
I didn't encounter too much of a challenge building the page. For me, it was a great way to review the basics. That being said, it would be great to rework the challenge this time allowing the user to enter their own recipe and at the very least save for future use.
What specific areas of your project would you like help with?
I am open to any advice regarding my solution. Would love to hear the communities thoughts in general.
What are you most proud of, and what would you do differently next time?
proud that:
I made it almost identical to the design given
-I used flex and grid to place my elements
what I would dodifferently next time:
-I would opt for the more adequate property that matches the layout requirements, Since
this time I used grid even though flex is more approriate just to try the grid property.
What challenges did you encounter, and how did you overcome them?
The challenge was quite simple and enjoyable.
The main challenge was placing the elements correctly but using flex made everything easier and smoother.
What specific areas of your project would you like help with?
Actually I am wondering about this part : See hover and focus states for all interactive elements on the page.
which elements should be with hover and focus states? I think I missed that part
What are you most proud of, and what would you do differently next time?
I am proud of my experience during the challenge and how I handled the initial loading of the advice generator app by adding a skeleton loader. I am also glad that I was able to address the user stories for the challenge.
Looking ahead, I would like to write cleaner code, speed up my workflow, and make my work perform better and be more accessible.
What challenges did you encounter, and how did you overcome them?
I did not face any major troubles in completing the challenge, as I was able to check off the user stories for the challenge, and also stayed on time.
Note: Once the design comparison is adjusted, this line will be removed.
What specific areas of your project would you like help with?
I would appreciate some feedback and code review on the overall challenge.
Great, I checked all your code, very clean and readable, awesome.
However, I couldn't figure out how you implemented the skeleton. There was no mention of the skeleton in the JavaScript code, and I didn't see any functionality to toggle it or interact with it when data is fetched.