updated readme and webprojects data to point to challenge
This commit is contained in:
parent
f60b524f86
commit
99b4792200
|
|
@ -0,0 +1,79 @@
|
||||||
|
# Frontend Mentor - Social proof section
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Welcome! 👋
|
||||||
|
|
||||||
|
Thanks for checking out this front-end coding challenge.
|
||||||
|
|
||||||
|
[Frontend Mentor](https://www.frontendmentor.io) challenges allow you to improve your skills in a real-life workflow.
|
||||||
|
|
||||||
|
**To do this challenge, you need a basic understanding of HTML and CSS.**
|
||||||
|
|
||||||
|
## The challenge
|
||||||
|
|
||||||
|
Your challenge is to build out this social proof section and get it looking as close to the design as possible.
|
||||||
|
|
||||||
|
You can use any tools you like to help you complete the challenge. So if you've got something you'd like to practice, feel free to give it a go.
|
||||||
|
|
||||||
|
Your users should be able to:
|
||||||
|
|
||||||
|
- View the optimal layout for the section depending on their device's screen size
|
||||||
|
|
||||||
|
Want some support on the challenge? [Join our Slack community](https://www.frontendmentor.io/slack) and ask questions in the **#help** channel.
|
||||||
|
|
||||||
|
## Where to find everything
|
||||||
|
|
||||||
|
Your task is to build out the project to the designs inside the `/design` folder. You will find both a mobile and a desktop version of the design to work to.
|
||||||
|
|
||||||
|
The designs are in JPG static format. This will mean that you'll need to use your best judgment for styles such as `font-size`, `padding` and `margin`. This should help train your eye to perceive differences in spacings and sizes.
|
||||||
|
|
||||||
|
If you would like the Sketch file in order to inspect the design in more detail it is available to buy from the challenge page on the platform.
|
||||||
|
|
||||||
|
You will find all the required assets in the `/images` folder. The assets are already optimized.
|
||||||
|
|
||||||
|
There is also a `style-guide.md` file, which contains the information you'll need, such as color palette and fonts.
|
||||||
|
|
||||||
|
## Building your project
|
||||||
|
|
||||||
|
Feel free to use any workflow that you feel comfortable with. Below is a suggested process, but do not feel like you need to follow these steps:
|
||||||
|
|
||||||
|
1. Initialize your project as a public repository on [GitHub](https://github.com/). This will make it easier to share your code with the community if you need some help. If you're not sure how to do this, [have a read through of this Try Git resource](https://try.github.io/).
|
||||||
|
2. Configure your repository to publish your code to a URL. This will also be useful if you need some help during a challenge as you can share the URL for your project with your repo URL. There are a number of ways to do this, but we recommend using [Vercel](https://bit.ly/fem-vercel). We've got more information about deploying your project with Vercel below.
|
||||||
|
3. Look through the designs to start planning out how you'll tackle the project. This step is crucial to help you think ahead for CSS classes that you could create to make reusable styles.
|
||||||
|
4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
|
||||||
|
5. Write out the base styles for your project, including general content styles, such as `font-family` and `font-size`.
|
||||||
|
6. Start adding styles to the top of the page and work down. Only move on to the next section once you're happy you've completed the area you're working on.
|
||||||
|
7. If you'd like to try making your project fully responsive, we'd recommend checking out [Sizzy](https://bit.ly/fm-sizzy). It's a great browser that makes it easy to view your site across multiple devices.
|
||||||
|
|
||||||
|
## Deploying your project
|
||||||
|
|
||||||
|
As mentioned above, there are a number of ways to host your project for free. We recommend using [Vercel](https://bit.ly/fem-vercel) as it's an amazing service and extremely simple to get set up with. If you'd like to use Vercel, here are some steps to follow to get started:
|
||||||
|
|
||||||
|
1. [Sign up to Vercel](https://bit.ly/fem-vercel-signup) and go through the onboarding flow, ensuring your GitHub account is connected by using their [Vercel for GitHub](https://vercel.com/docs/v2/git-integrations/vercel-for-github) integration.
|
||||||
|
2. Connect your project to Vercel from the ["Import project" page](https://vercel.com/import), using the "From Git Repository" button and selecting the project you want to deploy.
|
||||||
|
3. Once connected, every time you `git push`, Vercel will create a new [deployment](https://vercel.com/docs/v2/platform/deployments) and the deployment URL will be shown on your [Dashboard](https://vercel.com/dashboard). You will also receive an email for each deployment with the URL.
|
||||||
|
|
||||||
|
## Sharing your solution
|
||||||
|
|
||||||
|
There are multiple places you can share your solution:
|
||||||
|
|
||||||
|
1. Submit it on the platform so that other users will see your solution on the site. Here's our ["Complete guide to submitting solutions"](https://medium.com/frontend-mentor/a-complete-guide-to-submitting-solutions-on-frontend-mentor-ac6384162248) to help you do that.
|
||||||
|
2. Share your solution page in the **#finished-projects** channel of the [Slack community](https://www.frontendmentor.io/slack).
|
||||||
|
3. Tweet [@frontendmentor](https://twitter.com/frontendmentor) and mention **@frontendmentor** including the repo and live URLs in the tweet. We'd love to take a look at what you've built and help share it around.
|
||||||
|
|
||||||
|
## Giving feedback
|
||||||
|
|
||||||
|
Feedback is always welcome, so if you have any to give on this challenge please email hi[at]frontendmentor[dot]io.
|
||||||
|
|
||||||
|
This challenge is completely free. Please share it with anyone who will find it useful for practice.
|
||||||
|
|
||||||
|
**Have fun building!** 🚀
|
||||||
|
|
||||||
|
## Community Sponsors
|
||||||
|
|
||||||
|
A massive thank you to our community sponsors!
|
||||||
|
|
||||||
|
- [Contrast](https://bit.ly/fem-contrast) reimagines how developers inspect, collaborate, and build components off Figma designs.
|
||||||
|
- [Diversify Tech](https://bit.ly/fem-diversify-tech) is an amazing resource for underrepresented people in tech. The site features job listings for anyone seeking new opportunities. The resource section is also full of useful links to dive into!
|
||||||
|
- [Triplebyte](http://bit.ly/fem-triplebyte) can save a lot of time and stress during the job hunting process. Their free, confidential quiz makes it so that companies end up pitching you for their vacant job roles.
|
||||||
|
|
@ -1,79 +1,71 @@
|
||||||
# Frontend Mentor - Social proof section
|
# Frontend Mentor - Social proof section solution
|
||||||
|
|
||||||
|
This is a solution to the [Social proof section challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/social-proof-section-6e0qTv_bA). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
|
||||||
|
|
||||||
## Welcome! 👋
|
## Table of contents
|
||||||
|
|
||||||
Thanks for checking out this front-end coding challenge.
|
- [Frontend Mentor - Social proof section solution](#frontend-mentor---social-proof-section-solution)
|
||||||
|
- [Table of contents](#table-of-contents)
|
||||||
|
- [Overview](#overview)
|
||||||
|
- [The challenge](#the-challenge)
|
||||||
|
- [Screenshot](#screenshot)
|
||||||
|
- [Links](#links)
|
||||||
|
- [My process](#my-process)
|
||||||
|
- [Built with](#built-with)
|
||||||
|
- [What I learned](#what-i-learned)
|
||||||
|
- [Continued development](#continued-development)
|
||||||
|
- [Author](#author)
|
||||||
|
|
||||||
[Frontend Mentor](https://www.frontendmentor.io) challenges allow you to improve your skills in a real-life workflow.
|
## Overview
|
||||||
|
|
||||||
**To do this challenge, you need a basic understanding of HTML and CSS.**
|
### The challenge
|
||||||
|
|
||||||
## The challenge
|
Users should be able to:
|
||||||
|
|
||||||
Your challenge is to build out this social proof section and get it looking as close to the design as possible.
|
|
||||||
|
|
||||||
You can use any tools you like to help you complete the challenge. So if you've got something you'd like to practice, feel free to give it a go.
|
|
||||||
|
|
||||||
Your users should be able to:
|
|
||||||
|
|
||||||
- View the optimal layout for the section depending on their device's screen size
|
- View the optimal layout for the section depending on their device's screen size
|
||||||
|
|
||||||
Want some support on the challenge? [Join our Slack community](https://www.frontendmentor.io/slack) and ask questions in the **#help** channel.
|
### Screenshot
|
||||||
|
|
||||||
## Where to find everything
|
|
||||||
|
|
||||||
Your task is to build out the project to the designs inside the `/design` folder. You will find both a mobile and a desktop version of the design to work to.
|
|
||||||
|
|
||||||
The designs are in JPG static format. This will mean that you'll need to use your best judgment for styles such as `font-size`, `padding` and `margin`. This should help train your eye to perceive differences in spacings and sizes.
|
|
||||||
|
|
||||||
If you would like the Sketch file in order to inspect the design in more detail it is available to buy from the challenge page on the platform.
|
### Links
|
||||||
|
|
||||||
You will find all the required assets in the `/images` folder. The assets are already optimized.
|
- Solution URL: [Tarasis on Github](https://github.com/tarasis/tarasis.github.io/tree/main/projects/FrontendMentor/newbie/social-proof-section)
|
||||||
|
- Live Site URL: [tarasis.github.io](https://tarasis.github.io/FrontendMentor/newbie/social-proof-section)
|
||||||
|
|
||||||
There is also a `style-guide.md` file, which contains the information you'll need, such as color palette and fonts.
|
## My process
|
||||||
|
|
||||||
## Building your project
|
As usual, I started Mobile first. I setup CSS properties for colors, typography and such. After a bit I realised that the font needed was different from when I originally downloaded the starter kit for this challenge. Which meant that my variables were off.
|
||||||
|
|
||||||
Feel free to use any workflow that you feel comfortable with. Below is a suggested process, but do not feel like you need to follow these steps:
|
Once I'd finished the mobile version, I re-arranged the HTML slightly because I forgot to make a top and bottom section.
|
||||||
|
|
||||||
1. Initialize your project as a public repository on [GitHub](https://github.com/). This will make it easier to share your code with the community if you need some help. If you're not sure how to do this, [have a read through of this Try Git resource](https://try.github.io/).
|
I had little problem with the alignments for the ratings and reviews, but I did end up waisting an hour chasing desktop alignment with design image. I just couldn't quite nail it.
|
||||||
2. Configure your repository to publish your code to a URL. This will also be useful if you need some help during a challenge as you can share the URL for your project with your repo URL. There are a number of ways to do this, but we recommend using [Vercel](https://bit.ly/fem-vercel). We've got more information about deploying your project with Vercel below.
|
|
||||||
3. Look through the designs to start planning out how you'll tackle the project. This step is crucial to help you think ahead for CSS classes that you could create to make reusable styles.
|
|
||||||
4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
|
|
||||||
5. Write out the base styles for your project, including general content styles, such as `font-family` and `font-size`.
|
|
||||||
6. Start adding styles to the top of the page and work down. Only move on to the next section once you're happy you've completed the area you're working on.
|
|
||||||
7. If you'd like to try making your project fully responsive, we'd recommend checking out [Sizzy](https://bit.ly/fm-sizzy). It's a great browser that makes it easy to view your site across multiple devices.
|
|
||||||
|
|
||||||
## Deploying your project
|
I also played a bit with where the desktop version should start.
|
||||||
|
|
||||||
As mentioned above, there are a number of ways to host your project for free. We recommend using [Vercel](https://bit.ly/fem-vercel) as it's an amazing service and extremely simple to get set up with. If you'd like to use Vercel, here are some steps to follow to get started:
|
### Built with
|
||||||
|
|
||||||
1. [Sign up to Vercel](https://bit.ly/fem-vercel-signup) and go through the onboarding flow, ensuring your GitHub account is connected by using their [Vercel for GitHub](https://vercel.com/docs/v2/git-integrations/vercel-for-github) integration.
|
- Semantic HTML5 markup
|
||||||
2. Connect your project to Vercel from the ["Import project" page](https://vercel.com/import), using the "From Git Repository" button and selecting the project you want to deploy.
|
- CSS custom properties
|
||||||
3. Once connected, every time you `git push`, Vercel will create a new [deployment](https://vercel.com/docs/v2/platform/deployments) and the deployment URL will be shown on your [Dashboard](https://vercel.com/dashboard). You will also receive an email for each deployment with the URL.
|
- Flexbox
|
||||||
|
- CSS Grid (only for positioning in the middle of the page )
|
||||||
|
- Mobile-first workflow
|
||||||
|
|
||||||
## Sharing your solution
|
### What I learned
|
||||||
|
|
||||||
There are multiple places you can share your solution:
|
To check for updated files.
|
||||||
|
|
||||||
1. Submit it on the platform so that other users will see your solution on the site. Here's our ["Complete guide to submitting solutions"](https://medium.com/frontend-mentor/a-complete-guide-to-submitting-solutions-on-frontend-mentor-ac6384162248) to help you do that.
|
Don't chase perfection.
|
||||||
2. Share your solution page in the **#finished-projects** channel of the [Slack community](https://www.frontendmentor.io/slack).
|
### Continued development
|
||||||
3. Tweet [@frontendmentor](https://twitter.com/frontendmentor) and mention **@frontendmentor** including the repo and live URLs in the tweet. We'd love to take a look at what you've built and help share it around.
|
|
||||||
|
|
||||||
## Giving feedback
|
Practice practice and practice.
|
||||||
|
|
||||||
Feedback is always welcome, so if you have any to give on this challenge please email hi[at]frontendmentor[dot]io.
|
## Author
|
||||||
|
|
||||||
This challenge is completely free. Please share it with anyone who will find it useful for practice.
|
- Website - [Robert McGovern blog](https://tarasis.net)
|
||||||
|
- Frontend Mentor - [@tarasis](https://www.frontendmentor.io/profile/tarasis)
|
||||||
|
- Twitter - [@tarasis](https://www.twitter.com/tarasis)
|
||||||
|
|
||||||
**Have fun building!** 🚀
|
|
||||||
|
|
||||||
## Community Sponsors
|
|
||||||
|
|
||||||
A massive thank you to our community sponsors!
|
|
||||||
|
|
||||||
- [Contrast](https://bit.ly/fem-contrast) reimagines how developers inspect, collaborate, and build components off Figma designs.
|
|
||||||
- [Diversify Tech](https://bit.ly/fem-diversify-tech) is an amazing resource for underrepresented people in tech. The site features job listings for anyone seeking new opportunities. The resource section is also full of useful links to dive into!
|
|
||||||
- [Triplebyte](http://bit.ly/fem-triplebyte) can save a lot of time and stress during the job hunting process. Their free, confidential quiz makes it so that companies end up pitching you for their vacant job roles.
|
|
||||||
|
|
|
||||||
|
|
@ -11,6 +11,17 @@
|
||||||
"title": "Newbie",
|
"title": "Newbie",
|
||||||
"cssClass": "frontEndMentorChallenges",
|
"cssClass": "frontEndMentorChallenges",
|
||||||
"challenges": [
|
"challenges": [
|
||||||
|
{
|
||||||
|
"title": "Social Proof Section",
|
||||||
|
"url": "/FrontendMentor/newbie/social-proof-section/",
|
||||||
|
"description": "",
|
||||||
|
"techUsed": [
|
||||||
|
"html5",
|
||||||
|
"css3"
|
||||||
|
],
|
||||||
|
"screenshotURL": "/FrontendMentor/newbie/social-proof-section/screenshots/desktop.png",
|
||||||
|
"screenshotAltText": "Social Proof Challenge from FrontendMentor"
|
||||||
|
},
|
||||||
{
|
{
|
||||||
"title": "Intro Component with Signup form",
|
"title": "Intro Component with Signup form",
|
||||||
"url": "/FrontendMentor/newbie/intro-component-with-signup-form/",
|
"url": "/FrontendMentor/newbie/intro-component-with-signup-form/",
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue