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

Responsive landing page, built using ReactJS, CSS Grid and Flexbox

react, pure-css
Kuvashnee Naidoo•450
@KuvashneeNaidoo
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 proud of building a mobile-friendly navigation menu with a hamburger icon and mastering Flexbox and Grid for a responsive layout. I used React's useState hook for menu state management, ensuring a dynamic experience. For the future, I plan to implement a slider for the photo gallery, focusing on state management to control the active image and adding navigation buttons for a smoother user experience.

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

One aspect I spent some time on was refining the positioning of elements using Flexbox and Grid. I experimented with various layout configurations, adjusting properties like display, justify-content, align-items etc. I also utilised browser developer tools to test responsiveness across different screen sizes, ensuring a consistent and adaptable design.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Stevan-Dev•660
    @Stv-devl
    Posted 4 months ago

    Hi,

    I like your React components, they are clean and have well-structured JSX.

    I have some advice for you :

    • You can keep each component in its own folder and include its CSS file there. This makes it easier to reuse the components.

    • Consider placing your images and other assets (like font) in the public folder.

    • It’s a good practice to use the map to display elements in React :

    const PhotoGallery = () => {
      const images = [
        { src: MilkBottles, alt: "milk-bottles" },
        { src: Orange, alt: "orange-on-table" },
        { src: Cone, alt: "ice-cream-cone" },
        { src: SugarCubes, alt: "sugar-cubes" },
      ];
    
      return (
        <section className="gallery-section">
          <div className="gallery-grid-container">
            {images.map((image, index) => (
              <img key={index} src={image.src} alt={image.alt} />
            ))}
          </div>
        </section>
      );
    };
    
    export default PhotoGallery;
    
    const Testimonials = () => {
      // 1. Define an array of testimonials
      const testimonialsData = [
        {
          image: Emily,
          alt: "Emily",
          review: "We put our trust in Sunnyside and they delivered, making sure our needs were met and deadlines were always hit.",
          name: "Emily R.",
          occupation: "Marketing Director",
        },
        {
          image: Thomas,
          alt: "Thomas",
          review: "Sunnyside’s enthusiasm coupled with their keen interest in our brand’s success made it a satisfying and enjoyable experience.",
          name: "Thomas S.",
          occupation: "Chief Operating Officer",
        },
        {
          image: Jennie,
          alt: "Jennie",
          review: "Incredible end result! Our sales increased over 400% when we worked with Sunnyside. Highly recommended!",
          name: "Jennie F.",
          occupation: "Business Owner",
        },
      ];
    
      return (
        <section className="testimonials-section">
          <h1 className="testimonials-heading">Client Testimonials</h1>
          <div className="testimonials-grid-container">
            {testimonialsData.map(({ image, alt, review, name, occupation }, index) => (
              <div key={index}>
                <img src={image} alt={alt} />
                <p className="review">{review}</p>
                <p className="name">{name}</p>
                <p className="occupation">{occupation}</p>
              </div>
            ))}
          </div>
        </section>
      );
    };
    
    export default Testimonials;
    

    Good continuation

    Marked as helpful
  • Marzia Jalili•8,410
    @MarziaJalili
    Posted 3 months ago

    A tiny suggestion:

    I'm kinda planning to create a study group on Google Chats let me know if you're interensted to be added there. Let's beat Elon Musk together.

    😂😂😂

    Here's my email:

    astronomyfancy@gmail.com

    Throw me a hi on Google Chats, if you are willing to be a part of the devastation.

    😎😎😎

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

Oops! 😬

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

Log in with GitHub