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

URL Shortening Page (Pair Programming Project, SCSS, JS)

accessibility, sass/scss
Aman Singh Bhogal•1,010
@asbhogal
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


This is a pair programming project with Kay. (ofthewildfire)

Changes to the design have intentionally been made to adhere to accessibility standards, as the mockups were failing background/foreground contrast ratio checks. A different theme styling was subsequently integrated page-wide whilst maintaining consistency of wireframe structure.

Lighthouse Scores: 100 | 100 | 100 | 100

Below is a brief list of the contributions made by both parties as well as planned iterations for future build versions:

Kay:

  • Integration of markup incl. elements and structure
  • Integration of responsive styling of elements
  • Improvements to accessibility (styling)
  • Integration of JavaScript logic, incl.:
  • URL shortener API calls
  • Migration to Short.io API
  • clipboardAPI
  • localStorage
  • Responsive navbar toggling
  • Reviewing of build through iterative processes and providing suggestions

Aman:

  • Initialisation of Vite environment and configurations (incl. CSS source-mapping)
  • Refactoring of JS and SCSS
  • Changes to styling and flow incl. navbar structure and layout
  • Changes to design system/theme, markup and styles to meet accessibility standards
  • Addition of README.md
  • Deployment to Vercel

Planned Iterations:

  • Changes to responsive background images - replace CSS background-image with <picture> elements
  • Add explicit height and width to respective images
  • Further clean-up of duplicate code
  • Removal of comments for cleaner readability
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 Aman Singh Bhogal'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.