Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Tailwind CSS, Flexbox, Javascript

tailwind-css
John Pugh•370
@JohnPugh688
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first project using Javascript. I hope you can take the time to have a look at my code and give me some feedback as like i've mentioned before this is all new to me. Ive spent the past 10 years working as a construction site manager with very little experience even using a computer. So for me this is a huge challenge that i'm enjoying more than i ever expected. I think on my next project i'm going to give React a go as i think this will work really well along with tailwind CSS? Anyone else use this combination let me know your thoughts and any tips for setting up my coding environment would be welcome. As always i look forward to you feedback good or bad. thanks in advance

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • BrunoMoleta•700
    @brunomoleta
    Posted over 1 year ago

    "Hola" John,

    I advise you to avoid styling the `````body```` tag. Things may get unnecessarily messy doing so.

    For starter, the body ought to have a width:100% and then, inside the header, main and ````````footertag you may use adivwith the.max-w-[1440px]````.

    Also, I don't see the need to use a section inside the header tag. You can use an a,nav and button, because the header is the section, you know?

    Another observation: The article card will lead the user to another webpage, so this shall not be a div tag, for divs have no semantic meaning.

    It's better if this tag is an article. According to MDN: The <article> HTML element represents a self-contained composition in a document, page, application, or site, which may be independently reusable. Examples include a forum post, a magazine or newspaper article, or a blog entry

    Also, I recommend this blog: JoshComeau. He writes thoroughly about front-end programming. It's worth checking from time to time.

    (If you find this comment helpful, please mark it as helpful)

    Congrats on the effort, John :)

    Best regards from Brazil

    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
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