Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

easybank-landing-page

Antonio Filho•130
@antoniodlfilho
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What specific areas of your project would you like help with?

Tive problemas com as imagens da página principal (main). Não consegui deixá-las do jeito que queria. Além disso, na nav, não consegui colocar a borda abaixo do link. Seria necessário fazer isso com ::after? Qualquer feedback é bem-vindo. Ainda preciso fazer alguns ajustes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bernardo Poggioni•6,850
    @R3ygoski
    Posted about 1 month ago

    Olá Antonio, parabéns pela conclusão de mais um projeto aqui do FEM, ele ficou ótimo.

    Sobre suas dúvidas, vou começar pela parte do Link, você pode sim chegar ao resultado utilizando ::after ou ::before, ou até mesmo criando uma <div>. Aqui vou mostrar com o ::after.

    .nav-list {
      height: 100%; /* Fiz isso para que o li ficasse grande e ficasse fácil de posicionar o traço */
      display: flex;
      align-items: center;
    }
    
    .nav-list ul {
      height: 100%;
      /* restante das props */
    }
    
    .nav-list ul li {
      display: flex;
      align-items: center;
      position: relative;
    }
    
    li::after {
      content: ''; /* Cria o after */
      display: block; /* Define como um bloco */
      position: absolute; /* Se posiciona relativamente ao li */
      background: linear-gradient(45deg, lime, cyan); /*! Essas cores estão erradas */
      height: 6px;
      width: 100%;
      bottom: 0; /* Joga o traço para a parte debaixo do li */
      opacity: 0; /* Invisível */
    
      transition: 0.3s ease-in-out; /*<- Cosmético - Não necessário*/
    }
    
    li:hover::after {
      opacity: 1; /* Visível ao passar o mouse na li */
    }
    

    Isso já fará com que apareça.

    Agora sobre a imagem eu não sei qual problema você teve, foi sobre o tamanho da imagem? Caso tenha sido você pode apenas aumentar o max-width que isso já fará ela ficar igual a do design fornecido.

    E é isso! Novamente parabéns, caso tenha ficado qualquer dúvida, por favor comente abaixo que tentarei ajudar da melhor forma possível.

    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