Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 15 days ago

Responsive Landing Page Using Css Grid, Flexbox and Bootstrap

bootstrap
Victor Nnamani•40
@VictorNnamani651
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm not exactly proud of much here but... for what it's worth, I actually just learnt while building this project that min-height/min-width and height/width in CSS aren't the same and can be used on one element or in fact, are both supposed to be used together and on the same element.

I know it's probably an obvious thing to know, but yeah, I didn't know and now I do, and I feel good about it and I also feel like a better developer (maybe I'm being too extra over a little thing, but oh well...)

hmmm... what I would do differently. I would most definitely try building the mobile view first. I would also try not to be too fancy with my code.(I'll explain this in the "What challenges did you encounter, and how did you overcome them?" section)

What challenges did you encounter, and how did you overcome them?

Ok, so, to explain what I meant when I said Previously that I would try not to be too fancy with my code.

I actually took more time than required building the footer section of this project. Yes, I know. It's like the simplest part of this whole project.

I tried writing fancy html and it became difficult for me to style(I was using both bootstrap and custom css).

How did I overcome? lol, I erased that witty junk and wrote a very simple code and voilà! It was done.

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

I can't think of any, but I actually do feel like I could do much better on this project, so I am very very open to corrections, opinions and ideas.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Victor Nnamani's solution.

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.