Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

URL shortening API landing page

node, react, tailwind-css, typescript, express
Sophie•430
@ippotheboxer
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


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

I'm proud of how accurate the design is and how the website is functioning as intended, with both a backend and frontend hosted on render. I'm proud I got it to work with the local storage, it did take some trial and error.

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

First of all I struggled with the local storage, basically I had to change the way it was being stored multiple times so that I could have an array to map through the values. At first I only had a frontend, however the request to clean URI was not working, This was because of CORS policy, so I had to change it to include a backend and this made it work. I also got a bit stuck on hosting it on render since I used vite and not create-react-app, but searching around and Chatgpt helped out a lot.

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

For most of my components, I am wrapping them in a wrapper div, however I don't think this is the most efficient way of doing the design and I would like some feedback on this. Also I was originally storing the URL links that show up in a separate component, however I couldn't get the "copy/copied" button to work with this, so I had to remove the component and just map through the div, I would like some advice on how to pass the props (particularly the active button index and setting it onClick) because I couldn't work out how to achieve this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Sophie's solution.

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.