Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

Link-Share: One Link to Rule Them All

pure-css, sql, supabase, accessibility
Geo A•230
@Geo-Bold
A solution to the Link-sharing app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

This represented my final intellectual exercise before learning a framework. After a few weeks of planning I decided to diverge from the original design in the following ways: >

  • Requiring a user to create an account to use the application represents a significant emotional and time investment which may lead to a subsequent loss in traffic. To address this, I disrupted the application flow by allowing a user to interact with the app in every way without the need for creating an account. An account is only required when a user wishes to generate and share their own unique link.
  • Due in part to the divergence from the original projects logical flow as well as my personal dislike of the original UI/UX, I chose to redesign certain UI elements and include some custom assets. These changes culminate mainly in the form of a custom color scheme including brand color, navbar changes both to desktop and mobile devices as well as custom notifications.
  • This project implements data persistence using the browser's local storage as well as Supabase's database-as-a-service.
What challenges did you encounter, and how did you overcome them?

In part as an intellectual exercise and despite the performance implications, I decided to diverge from a single page application and instead implement a multipage web application. This required me to manage state across multiple pages which I achieved thanks to a Local Storage class. This separation of state from the database required further implementation of a version control system to sync data from the cloud and the client's local storage. This project also provided me my first opportunity to create and interact with a SQL database of which I have learned a great deal.

What specific areas of your project would you like help with?

My next steps include grinding leetcode as if it were ranked League of Legends as well as developing further projects in Angular. I anticipate great things in the near future and I can not wait to share them with you.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Geo A'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

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.