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

Practicing workflow, automation, organization, best practices, mobile

Matthew•295
@CodingDatum
A solution to the Fylo dark theme landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey fam! I mostly wanted a project to work on to apply new workflow habits I'm trying to cultivate. I used webpack for the first time here, and got to be very organized with my folders and css/js files. Utilized BEM naming conventions. Practiced OOP (albeit the only functionality I implemented was a reveal on scroll class), with emphasis on reusability. I used a mobile-first approach here so as to allow the desktop to do the heavy lifting when necessary. I would still like to lazy load the images, and add better responsiveness to them, but wanted to wrap it up to begin a real-world project. Obviously I wasn't pixel perfect in terms of adhering to design standards, but I had fun! And I learned!!! Any and all comments welcome please and thanks!

EDIT: Also where is everyone getting their social media icons because I can't find any decent ones for free...

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nick•760
    @Nick331102
    Posted almost 4 years ago

    Hello,

    When the social media icons aren't included in the image file you can get them at font awesome. Font awesome is free

    Marked as helpful

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