Skip to content
  • Learning paths
  • Challenges
  • Solutions
  • Articles
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Vanilla PHP, Javascript Object Oriented Programming

animation, mysql, php
Chris Paschall•440
@ChrisP1108
A solution to the Link-sharing app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


NOTE: The live site url is: https://www.link-sharing-app.online

The live site url field wasn't allowing me to enter it in given its syntax.

For this project, I sought to improve my knowledge of Object Oriented programming. I utilized PHP, MySql, and the foundational front-end tools (HTML, CSS, Javascript). No frameworks were used, and the project did utilize some newer CSS features(CSS nesting) so older browsers may not display it correctly(all browsers currently support this, so it will get better over time.) This was built out into a full stack application.

I'll definitely say writing everything plain vanilla did cause it to take longer to complete, but I learned a great deal about object oriented concepts, such as public, private properties and methods, instantiating classes, and inheritance. This improved knowledge will definitely help me better understand the wordflow of frameworks better in the future.

I deployed this project through Hostinger, so learning how to migrate a sign custom coded to a live site and changing the configuration on the .env file information to connect to MySql on Hostinger was a good learning experience when deploying a site.

With the knowledge I have gained, if I were to start another project like this, I would probably utilize Laravel (backend PHP) and Vue.JS (frontend Javascript) in the future to build a full stack application like this, since PHP seems to be an easy backend programming language to work with(and it's supported among a lot of domain hosts).

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 Chris Paschall'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.