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

URL shortening API landing page

👾 Ekaterine Mitagvaria 👾•7,860
@catherineisonline
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


Hello, Frontend Mentor community! This is my solution to the URL shortening API landing page.

I appreciate all the feedback you left that helped me to improve this project. I fixed the issues I had previously and added new features per your recommendation.

I have done this project a while ago however if you are here and have any feedback, tips, or ideas to share, I will be more than glad to hear them out!

Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Omar Elbastawesy•230
    @omarelbastawesy
    Posted almost 3 years ago

    Great job :)

  • Luis Herrera•795
    @Luis15Herr
    Posted over 3 years ago

    Amazing Work :)

  • TsuneWeb•260
    @TSune-web
    Posted over 3 years ago

    Well done!

  • Ahmed Abdelaal•220
    @shrki416
    Posted over 3 years ago

    @catherineisonline great job! This looks awesome :)

  • Nicolas Gula•170
    @NicolasGula
    Posted over 3 years ago

    Awesome!

  • Jordane Gengo•590
    @jgengo-alt
    Posted over 3 years ago

    looks very good, your logo (the brushes) are a bit disappearing compared to what is expected, but that's just a detailed. It's because you used the img to also do the background-color and the border-radius: 50% instead of inserting the image in a div with those ;)

    you did very great work here! thanks for sharing

  • Muh Suryadi Triputra Rahman•380
    @msuryaditriputraR
    Posted over 3 years ago

    Awesome Work..

  • AditNovadianto•1,040
    @AditNovadianto
    Posted over 3 years ago

    @catherineisonline you did this project so nice and not have any issues there!!!

  • bikeinman•1,080
    @BikeInMan
    Posted over 3 years ago

    If @nakoyawilson 's solution works for you, then please ignore. Unlike her, I didn't get time to clone and test it.

    But I get a feeling, mainClone.classList = "search-result"; is wrong.

    May be it should be written as mainClone.className = "search-result"; or mainClone.classList.add('search-result');

    Just a thought.

    BTW, you always say, it is not about design and just practicing js, but most of your work seems to be spot on. Great work as always.

  • Nakoya Wilson•1,530
    @nakoyawilson
    Posted over 3 years ago

    Hey Catherine! I downloaded your code, changed all occurrences of sessionStorage to localStorage and deleted originalHtml = localStorage.getItem("cloneCache"); and parentNode.innerHTML = originalHtml; from the function and the data displayed for me.

    window.onload = function () {
      let mainClone = shortlyResult.cloneNode(true);
      let cloneLinkField = mainClone.querySelector(".inserted-link");
      mainClone.classList = "search-result";
      parentNode.appendChild(mainClone);
      //Retrieving
      let cloneLink = localStorage.getItem("cloneLink");
      console.log(cloneLink);
      //Injecting
      console.log(cloneLinkField);
      cloneLinkField.innerHTML = cloneLink;
    };
    
  • Ken9Code•30
    @Ken9Kodehode
    Posted over 3 years ago

    Great work!

  • Jakub Krwawicz•320
    @kerminek
    Posted over 3 years ago

    Hi, one image makes your page wider than we want it to be. Solve it using "overflow: hidden" on main container of the page. Also, if you want to keep data after refresh try to make it using cookies or simply "localstorage" :)

  • Dev Rathore•2,540
    @GitHub-dev12345
    Posted over 3 years ago

    How to make this project and where are you learn APIs. Can you share how to learn APIs.

  • Dev Rathore•2,540
    @GitHub-dev12345
    Posted over 3 years ago

    Hey Catherine nice work😊🎉

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

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

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

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

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