Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

url-shortening-api-master (vanillia css/js)

accessibility
P
enzmrg 💫•920
@enzo-mir
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


🕓≈ 6h Api : search for an other api beacause cleanuri Api doesn't work there is a problem with cors as if you use the no-cors mode it's maybe broken :(

  • I used instead url-shortener-service
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • ThabisoMagwaza•280
    @ThabisoMagwaza
    Posted over 1 year ago

    This is very nice solution. I'm impressed that you managed to do it with vanilla html and CSS.

    I woud, however, caution against straying from the design when implementing such challenges. It's an interesting test of your attention to detail when you attempt to get the final application to look as close to the design as possible.

    These are some of the areas I've identified where you strayed from the design:

    1. Some button and links hover states are incorrect
    2. The font sizes and whitespaces are not as per design
    3. The hero image is quite small compared to the design

    Additionally, I'd look into disabling the button when call to the url shortening is in progress. I found myself mistakenly clicking the button twice. It would also help to have some kind of loading indicator.

    I'm sure you can find some more. I suggest that you look throught the design again while paying close attention to the whitespace, hover and active stetes.

    You have an impressive grasp of CSS and I'm sure you'll benefit from the challenge!

    Marked as helpful
  • Gioant•160
    @Gioant
    Posted over 1 year ago

    Looks pretty good. Preview is working for me. Nice responsiveness! the only thing I would consider improving is the error handling for the form input.

    For example, the first time a user enters your website and wants to shorten a link they see a box.

    How come, even when the user does not enter anything (simply just focusing or clicking on the input) to type something.. they are already presented with an error?😅

    I understand you want to emphasize to them that they should put a link but the user didn't even start typing yet.

    That's what labels and placeholders are for. You already have a placeholder (that is good!)

    Instead, It would be better to show the same error when the user enters an input that is not valid (not a valid link). Not before.

    Marked as helpful
  • P
    enzmrg 💫•920
    @enzo-mir
    Posted over 1 year ago

    Preview is broken ! If someone can help me to fix it ?

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

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

Oops! 😬

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

Log in with GitHub