Design comparison
Solution retrospective
This is my first time working with an API but it's really simple although it took two hours to realize what promises meant to these machines(They are too loyal to their promises and they expect you do same).
Once I figured I needed to get the object tokens to know the key/value pair so I know what data to request, it was easy. Although I spent some minutes wondering why the advice won't change but it's the way the API is not that I did something wrong.
I believe I had no problems with positioning doing this as everything was centered.
If there's any where I can improve on this, let me know. I'm thinking maybe I should make an advice display on DOM load but I figured my little animation on the button which took me a whole 30min may not be discovered. So, you'll have to press that button to get an advice.
Community feedback
- @hnasser44Posted over 1 year ago
Hello! The animation on the button is really nice and neat. I would highly recommend exploring flexbox for creating flexible and responsive layouts and understanding how to position elements using absolute and relative positioning. Also, it's generally best to avoid setting explicit heights for elements unless it's absolutely necessary. Keep up the great work!
Marked as helpful1@ifarontiPosted over 1 year ago@hnasser44 Thank you so much for your feedback. I'm currently reading up on CSS flexbox, thanks to your recommendation. Thanks once more..
1
Please log in to post a comment
Log in with GitHub
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord