All solutions

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

I'm proud of how I passed down the set state method to the form component so that the state data can be updated there and shared with the input elements for validation.

Next time, I'd draw a rectangle around elements with values that update the UI. So that way, I can be more strategic in the development process.

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

It was difficult to decide how I'd share the state values and validate the data inputs. Initially, I used the Context API to share stateful values across child components.

And then I added a 'updateDate' prop to the form element so I can update the state from within the component and have the changes reflected in the input fields.

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

Are there hooks I could've used to increase performance and deal with memory management?

I want to be notified of any update that's better than the current approach.

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

I love how the project can easily be modified later on without having to go over everything from scratch. It's well written and maintainable.

If I were to rebuild the project again, I'd name the components with more clarity.

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

It wasn't that much of a struggle, but getting the tag amounts to hover over the chart bar wasn't easy. I had no choice but to resort to absolute positioning.

It wasn't easy to create the bar sizes based on how they look like in the design image. But I still used my best judgement.

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

I'd love to know more about how I could've made the app more accessible by following best practices and using accessibility related properties/attributes.

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

I'm proud of the project's structure and the way I organized everything. It's really nice that I was able to avoid adding unnecessary complexities.

I wish I would style the project without writing much boilerplate in SASS.

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

I've found that it was particularly difficult to set up the routing and pass the data from the signup component to the success component.

I solved this by using the navigate's hook state to send the data from one component to another.

It was also difficult to display an error message indicating that a user has entered invalid email format.

I solved it by using state and checking for the input's invalid value with the 'checkValidity' method. I updated the state based on the input element's invalid status.

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

I'd love to know how I could've approached the styling. I feel like it's a little too cluttered and cramped the way it is now.

If anyone knows best practices for styling the project with Saas, I'd really love to know.

Any feedback or suggestions are most welcome!

I'd truly appreciate any honest feedback on how to improve workflow and be more productive.

I struggled the most with learning how to set up my own workflow and making sure that everything is organized and clean. But I still believe that there are some areas that could use more improvement. If anyone knows more best practices that I haven't used in the project, please let me know!

How would you recommend turning a mockup into HTML code?