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

Single Page Portfolio / React/EmailJS

react
Andrei•560
@Xeotheosis
A solution to the Single-page developer portfolio challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Issues I can't figure out for the life of me:

  • how to change the svg icons color;
  • how to change the size of the hero image dynamically based on screen size;
  • how to position absolutely the circle/rings pattern without messing up the size of their container.

If anyone can help me with this, I'd be forever in your debt. You can also send me an email by using the Contact section on the project :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • cuftamaster•80
    @cuftamaster
    Posted almost 2 years ago

    -use inline svg, if u look at a svg in a text editor, like visual studio code, u will see that it is a vector graphic writen with vector graphic rules, paste that in your html, and than u can target its properties in css

    a svg:hover path { fill: #556B2F; }

    -tutorial on the topic link

    -overflow hidden, basically

    but u have some problems with layouts in general, below 1560px the your grid system breaks down, u can fix that by playing around with fr-s, gap-s, centering the content of the grid ect.. i know grid is powerful and can do a lot of complicated stuff, but overall you could have used flex for the whole thing as it is much easier and quicker to work with

    put some transitions on links

    the profile img should be able to "stack", meaning it should be either positioned absolutely, or a flex item

    i hope this helps u at least a little bit. best regards!

    Marked as helpful
  • Hanana•180
    @meantoes
    Posted almost 2 years ago

    hi! congrats on finishing this project!

    tbh, I have no idea how u write the code but if I can see the HTML file, I think u need more dividers for each section so u can set them with different sizes and displays.

    here's how I'd do it:

    • div for the hero:
    .hero {
    display: grid;
    grid-template-column: 2fr 1fr
    }
    
    • div for skills:
    .skills {
    display: flex;
    flex-wrap: wrap;
    }
    
    /* add class skill for each item */
    .skill {
    width: calc(100% / 2 - 20px); /* adjust for each screen sizes */
    }
    
    • div for projects' grid:
    .project-grid {
    display: grid;
    grid-template-column: 1fr 1fr; /* adjust for each screen sizes */
    }
    
    • div for contact and input (create two different grids for each):
    .contact {
    display: flex;
    flex-direction: row; /* adjust for each screen sizes */
    justify-content: space-between;
    }
    

    dont forget to add margin for each divs. or in the main-container if u put them in a container.

    hope this helps🙌🏻 have a great day⭐

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