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

Laravel sharing app that uses webform for login and signup

laravel, sass/scss, vite, typescript
Ilya Andreev•880
@NeoScripter
A solution to the Contact form 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?

It was my first Laravel project. I drastically modified the initial project, using the design and colors for the entire app. I'm very proud that I manage to host this app and make it work properly. It dinamically displays the shares and time of submission, it allows the users to edit their shares and profile pictures, sets permissions correctly, validates the webform input and displays errors. This app is connected to a real hosting, but it doesn't have an SSL certificate, which makes it show as unsafe. The link to the actual Laravel app: http://shares.ru.swtest.ru/

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

A lot. I had to figure out how to use Laravel migrations, how to set up database on a hosting. I couldn't connect to my hosting by SSH despite entering the password correctly. After many hours of struggling, I came up with a solution to create an SSH key file and upload it directly to the hosting, which made it unneccessary to enter the password. After that, I coundn't install Composer on the server as PHP version was too old and I couldn't use the new one for some reason. After that, the migrations didn't work properly. I could go on and on, but after all, I overcame all these hardships and now my website works!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    webdevbynight•530
    @webdevbynight
    Posted 6 months ago

    The solution does not seem to match the challenge or is concerning another challenge.

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