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

Pod landing page using flex/gridbox in sass with some basic js

jackson•500
@Jacksonishere
A solution to the Pod request access landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This one took me a while. Feel like my markup and organization with my styles is still very iffy. Would appreciate tips and feedback. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hey, good work on this one. Both desktop and mobile layout is good, and scales well just to say.

    Suggestions would be:

    • the img on your header tag could have an alt text. You could use alt="pod" like the text on the image, because it seems it is the company's name if you think about it. This gives more meaning for other user.
    • The text PUBLISH YOUR PODCASTS EVERYWHERE. could have been wrapped inside a single h1 element. This will make your html error go away since you need a h1 on a page. You could wrap the everywhere text in a span then give it a display: block so that it will go underneath the first text like on the design. That way you avoid 2 h2 declarations.
    • on the warning message on the form. Instead of transitioning the color of it, to make it more better for screen reader, transition the visibility property. This will allow a screen reader to only read an element, if it is visibility: visible, thus removing a confusion for SR users because it will read that error message even if they successfully submitted the form, because you are only transitioning the color
    • button type="submit" is much preferable than input type="submit" I have read it somewhere that it is the preferred way now.

    Other than those, really great job. Your html structure is quite good to be honest, just needed that one h1 right :>

    Marked as helpful
  • Naveen Singh•75
    @naveensing575
    Posted almost 4 years ago

    **Missing things: Input-Placeholder & singer-image and also site is not uploaded properly on netlify!

    Besides, you have done good code formatting 👍

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

Oops! 😬

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

Log in with GitHub