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

Responsive Design Porfolio - React - StyledComponents - Swiper.js

react, styled-components, accessibility
David•7,960
@DavidMorgade
A solution to the Single-page design portfolio challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello and welcome to my Design Portfolio Solution

This challenge was pretty much a CSS full practice.

Features of the Solution:

  • Resources I used:
  1. Create React App: Maybe you can think that is probably over-kill, but in this case, I want to practice my CSS with styled-components, this challenge can be purely done with HTML, CSS and JS.

  2. Styled-components: As I said in the previous paragraph, I am trying to practice my styled-components skills, also trying to improve my CSS.

  3. CSS Grid: For the design skills layout, I think is the best possible solution to do it!

  4. Flex-box: For making it a more easy-responsive project, the containers are all flexbox, except some cases that are done with CSS Grid.

  5. Swiper.js: For the sliders I did use a external Library called Swiper.js, making it more easy to build sliders and also has support for almost every framework!, I did create 3 different slides for each breakpoint (Mobile: Cube effect, Tablet: Pagination effect and Desktop: Normal Slider), you can check more info of this components on my README.md file

  • Breakpoints:
  1. 375px for Mobile
  2. 768px for Tablet
  3. 1440px for Desktop

Questions to FEM community:

  1. I would really appreciate if you can test the page and test the UI breakpoints and the Slider, If you have any suggestions, I would try to implement them if possible!
  2. ¿Do you think the cube effect is good for mobile devices?, ¿Would you stick to the challenge sliders or maybe use another kind of effect?.

If you want to checkout more info about this project, checkout the GitHub repository and the README.MD file

As always, any feedback is welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on David'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 1st-party linked stylesheets, and styles within <style> tags.

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.