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

URL Shortening API page with only JS

NicholasChristopherBlake•130
@NicholasChristopherBlake
A solution to the URL shortening API landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlos Damian Perez•1,930
    @caarlosdamian
    Posted over 1 year ago

    Great job on your project! Your effort in implementing this functionality using plain JavaScript is commendable and showcases your programming skills. It's evident that you've put thought and dedication into making it work seamlessly.

    However, I noticed that your API keys are visible in the repository. While I appreciate your transparency and openness in sharing your code, it's crucial to prioritize security. Exposing API keys in a public repository can pose a significant risk. I recommend considering a more secure approach, such as using a .env file to store sensitive information like API keys. This way, you can keep your credentials confidential and avoid any potential security issues.

    Incorporating best practices for handling sensitive information will not only enhance the security of your project but also demonstrate your commitment to producing robust and reliable code. It's a good habit to develop early on in your coding journey.

    Once again, kudos on your achievements so far! Your willingness to learn and improve is evident, and I look forward to seeing more of your impressive work in the future. Keep up the excellent work and happy coding!

    Marked as helpful

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