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

Link Sharing App (NextJS, Typescript, Supabase, Drizzle, TailwindCSS)

next, supabase, tailwind-css, typescript, tanstack-query
David•1,200
@David-Henery4
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 was the first time I had used react-query and I was surprised to see how well it worked with NextJS and how I could use it to prefetch the data on the server and not just use it on the client.

One thing I would do differently would to be plan exactly how I want to approach the state and how I want to build the project in general before getting started. I had originally wanted to use the react context API to handle the state, but then switched to react-query to handle the state, and because of this I feel the code became a lot messier than it needed to be.

What challenges did you encounter, and how did you overcome them?

One of the main challenges of this project was how to handle image file uploads, how to preview them, store them in a database, then retrieve it and render it.

In in the end it wasn't to bad to implement. I managed to do it through a lot of researching, reading & trail and error.

This has definitely sparked an interest in me and I want to learn more about how to handle & use different file types, not just images, in future applications I build.

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

One of the main areas I always find myself struggling with is architecture and I always feel like the way I arrange the folders and files isn't the most clean way of doing things and can get messy, especially when the app begins to scale.

I will have to do some research in the future in how to better organise and structure my overall projects.

If anyone has any tips or any resource material that you feel like can help, please let know or If you have any feedback about the project itself, let me know also, any and all feedback will be greatly appreciated, Thank you! 👍👍👍

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 David'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 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.