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

Link-sharing app using SolidJS

solid-js
Junior Nascimento•180
@Krymancer
A solution to the Link-sharing app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Throughout the process of developing this link-sharing app challenge using Solid JS and Tailwind CSS, I encountered exciting opportunities to explore cutting-edge technologies while focusing on user-centric design. Let's delve into some key points and best practices that played a crucial role in shaping the project.

Component-Based Architecture: Leveraging Solid JS's component-based architecture, I efficiently organized the codebase into reusable components. This approach not only improved code readability but also facilitated faster development iterations.

Responsive Design: A mobile-first approach was adopted to ensure a seamless user experience across various screen sizes. Tailwind CSS's responsive utilities empowered me to create a layout that beautifully adapts to different devices, enhancing accessibility and engagement.

Drag and Drop Functionality: Implementing the drag and drop feature for reordering links was an interesting challenge. I used Solid JS's reactivity to seamlessly update the link order, making the user interface highly interactive and intuitive.

Form Validation: Integrating form validation to provide users with meaningful feedback was paramount. Solid JS's reactivity facilitated real-time validation, ensuring that link URLs and profile details adhered to the required patterns.

User Profiles: I designed the application to allow users to add profile details, including a profile picture, first name, last name, and email. Validating these details before saving them improved the overall user experience.

Link Previews: Incorporating link previews in the mobile mockup added visual appeal and context to shared links. By leveraging relevant libraries or APIs, I ensured that link metadata was fetched and displayed dynamically.

Optimal Layout: Adapting the interface to various screen sizes was achieved through Tailwind CSS's responsive design classes. This practice resulted in a seamless experience for users, regardless of the device they were using.

Interactive Elements: Ensuring hover and focus states for all interactive elements enhanced the user experience by providing visual feedback and aiding navigation.

As I aim for continuous improvement, I eagerly invite feedback from the community on specific aspects of the project. I would appreciate insights on any challenges encountered during development, areas of code where you might have suggestions for enhancement, and any questions regarding best practices when working with Tailwind CSS.

Thank you for your support and valuable feedback. Together, we can further refine and elevate this link-sharing app to meet the needs and expectations of our users!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • haroldrivas2023•0
    @haroldrivas2023
    Posted almost 2 years ago

    Hola, hice pruebas pero al poner el nombre no aparece nada, no esta vinculado ? saludos

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