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

Responsive Url Shortening App - Built with React (Vite)

react, vite, framer-motion
KiddAlexx•150
@KiddAlexx
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


Description

This was my first project using React. I recently completed Scrimba’s basic React course, and this was a great project to follow up with and practice everything I had learnt.

As well as meeting the requirements for the challenge, I also added an additional feature that allow users to delete any result from the list.

Questions

  • I’d love some feedback on the organisation of the project, its component split, state management etc. As this is the first time creating a project in React I was not sure if I was following best practices etc.
  • I found myself nesting a lot of flex containers, and wonder if this is an inefficient way of doing things.
  • For the url form validation, I only utilised shrcodes built in error handling, but this is not very robust, as it essentially accepts any entry which has some characters split with a period. I want to in the future implement some better form validation, and I am curious if anyone has any specific advice when it comes to URL’s.
  • I also added the svg’s directly in the JSX, to be able to work with them more easily, but find this to be very messy. I read that you can convert them to React components or even use a plugin such as Vite’s Plugin for SVGR. I’m wondering what people find to be the best way to work with SVG’s in React.

Of course any feedback at all is much appreciated, thanks :)

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 KiddAlexx'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 1st-party linked stylesheets, and styles within <style> tags.

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.