Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

ReactJS, TailwindCSS and Axios

axios, react, tailwind-css
itsKrish01•420
@Itskrish01
A solution to the URL shortening API landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am excited to share that I have completed this challenge of link shorter web applications, I developed it using the ReactJS library. One of the key features I incorporated into the app was animation, which I achieved using the Framer Motion library. This added a visually engaging touch to the user interface, making the app more interactive and engaging. Additionally, I integrated data fetching using Axios, allowing for real-time updates and seamless data integration. I put a lot of effort into developing this application, and I would love to hear your feedback. Please feel free to share your thoughts and suggestions on how I can improve the app.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    visualdennis•8,375
    @visualdenniss
    Posted over 2 years ago

    Hey there,

    great job using variety of tools to complete this challenge!

    When resizing (e.g. browser width: 610px) the navigation button does not work as it is not clickable. It becomes only clickable when resized further to smaller mobile size. I noticed this problem is caused because the illustration of the image is sitting on top of it. It might seem like light colored background shape of the image is below the menu, giving the illusion of it cannot cover the menu, but in fact image is a big rectangle, so even its transparent parts are still taking up space. You might consider fixing that, one way could be decrease the z-index of container div of the image with { position: relative; z-index: -1; }

    Hope you find this feedback helpful!

    Marked as helpful
  • itsKrish01•420
    @Itskrish01
    Posted over 2 years ago

    Hello,

    I appreciate your feedback regarding the menu button and the header Image. I understand that it is not functioning properly on the tablet screen but is working on the mobile screen. I am aware of the issue and I know how to resolve it. Thank you for bringing this to my attention.

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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub