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

Typemaster Pre Launch Landing Page

drallas•375
@Drallas
A solution to the Typemaster pre-launch landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was a nice project, a bit more time consuming than I expected before starting.

Perhaps also because it was the first project that i used SASS; never used it before.

Feedback is welcome:

  • How can the responsiveness be improved, i struggle a bit deciding when to break!
  • Any tips on my SASS Usage.
  • I couldn't get the orange overlay exactly the same as the design, how can it do it different.
  • Any tips what how to improve the site in general.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Hey, there is an issue about the structure.

    • Okay, when I visited it, there seems to have 2 scrollbars on the right, the and I inspect your element and the overflow-x: hidden causes this that was declared on your .wrapper selector. I tried removing it and it fixes it.

    • Another issue, a big issue is that, there is a huge white blank spaces in your layout, in different sections there is. As I look in your grid, since you used grid in here, and saw your row grid-template-rows: 100% 100% 100% styled like this. Okay now this is a big problem like, since you are getting 100% but from where? At this instance, it is from the viewport since your grid, have no parent container. You could just remove this if you are just placing them in rows right or your declare it like this one grid-template-rows: repeat(3,auto);. That way, they are placed in different rows, and the size of the rows varies according to the height of the item that will be placed, hence auto.

    • I look into your sass and it seems okay, though when using scss it is better to use @use instead of @import so that there will be a namespace added to them, and them treating them as a module. But it's fine for now, I too use @import in scss since I cannot use other @ methods of sass since I am just using live sass compiler in vs code, but when I do my freelances, I go in best practices and uses my gulp for it.

    Refactoring those codes will be a great idea^^

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub