Skip to content

Commit 6e17134

Browse files
committed
update qr-code-component-main
1 parent cd573de commit 6e17134

File tree

8 files changed

+40
-172
lines changed

8 files changed

+40
-172
lines changed

qr-code-component-main/README-template.md

Lines changed: 0 additions & 103 deletions
This file was deleted.

qr-code-component-main/README.md

Lines changed: 39 additions & 68 deletions
Original file line numberDiff line numberDiff line change
@@ -1,87 +1,58 @@
1-
# Frontend Mentor - QR code component
1+
# Frontend Mentor - QR code component solution
22

3-
![Design preview for the QR code component coding challenge](./preview.jpg)
3+
This is a solution to the [QR code component challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/qr-code-component-iux_sIO_H). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
44

5-
## Welcome! 👋
5+
## Table of contents
66

7-
Thanks for checking out this front-end coding challenge.
7+
- [Overview](#overview)
8+
- [Screenshot](#screenshot)
9+
- [Links](#links)
10+
- [My process](#my-process)
11+
- [Built with](#built-with)
12+
- [What I learned](#what-i-learned)
13+
- [Continued development](#continued-development)
14+
- [Author](#author)
815

9-
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects.
1016

11-
**To do this challenge, you need a basic understanding of HTML and CSS.**
17+
## Overview
1218

13-
## The challenge
19+
### Screenshot
1420

15-
Your challenge is to build out this QR code component and get it looking as close to the design as possible.
21+
![desktop](screenshot/desktop.png)
22+
![mobile](screenshot/mobile.png)
1623

17-
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.
1824

19-
Want some support on the challenge? [Join our community](https://www.frontendmentor.io/community) and ask questions in the **#help** channel.
25+
### Links
2026

21-
## Where to find everything
27+
- Solution URL: [Add solution URL here](https://your-solution-url.com)
28+
- Live Site URL: [Add live site URL here](https://desire4tech.github.io/Frontend-projects/)
2229

23-
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.
30+
## My process
2431

25-
The designs are in JPG static format. Using JPGs will mean that you'll need to use your best judgment for styles such as `font-size`, `padding` and `margin`.
32+
### Built with
2633

27-
If you would like the design files (we provide Sketch & Figma versions) to inspect the design in more detail, you can [subscribe as a PRO member](https://www.frontendmentor.io/pro).
34+
- Semantic HTML5 markup
35+
- CSS custom properties
36+
- Flexbox
2837

29-
You will find all the required assets in the `/images` folder. The assets are already optimized.
38+
### What I learned
3039

31-
There is also a `style-guide.md` file containing the information you'll need, such as color palette and fonts.
40+
I learned how to add shadow, how to make an item centered and responsive.
3241

33-
## Building your project
42+
```css
43+
.proud-of-this-css {
44+
display: flex;
45+
flex-direction: column;
46+
align-items: flex-start;
47+
box-shadow: 0px 25px 25px 0px rgba(0, 0, 0, 0.05);
48+
}
49+
```
50+
### Continued development
3451

35-
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:
52+
I would still be interested in working with the display properties and box-shadow as well.
3653

37-
1. Initialize your project as a public repository on [GitHub](https://github.com/). Creating a repo will make it easier to share your code with the community if you need help. If you're not sure how to do this, [have a read-through of this Try Git resource](https://try.github.io/).
38-
2. Configure your repository to publish your code to a web address. 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, and we provide some recommendations below.
39-
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 to create reusable styles.
40-
4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
41-
5. Write out the base styles for your project, including general content styles, such as `font-family` and `font-size`.
42-
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.
54+
## Author
4355

44-
## Deploying your project
45-
46-
As mentioned above, there are many ways to host your project for free. Our recommended hosts are:
47-
48-
- [GitHub Pages](https://pages.github.com/)
49-
- [Vercel](https://vercel.com/)
50-
- [Netlify](https://www.netlify.com/)
51-
52-
You can host your site using one of these solutions or any of our other trusted providers. [Read more about our recommended and trusted hosts](https://medium.com/frontend-mentor/frontend-mentor-trusted-hosting-providers-bf000dfebe).
53-
54-
## Create a custom `README.md`
55-
56-
We strongly recommend overwriting this `README.md` with a custom one. We've provided a template inside the [`README-template.md`](./README-template.md) file in this starter code.
57-
58-
The template provides a guide for what to add. A custom `README` will help you explain your project and reflect on your learnings. Please feel free to edit our template as much as you like.
59-
60-
Once you've added your information to the template, delete this file and rename the `README-template.md` file to `README.md`. That will make it show up as your repository's README file.
61-
62-
## Submitting your solution
63-
64-
Submit your solution on the platform for the rest of the community to see. Follow our ["Complete guide to submitting solutions"](https://medium.com/frontend-mentor/a-complete-guide-to-submitting-solutions-on-frontend-mentor-ac6384162248) for tips on how to do this.
65-
66-
Remember, if you're looking for feedback on your solution, be sure to ask questions when submitting it. The more specific and detailed you are with your questions, the higher the chance you'll get valuable feedback from the community.
67-
68-
## Sharing your solution
69-
70-
There are multiple places you can share your solution:
71-
72-
1. Share your solution page in the **#finished-projects** channel of the [community](https://www.frontendmentor.io/community).
73-
2. 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.
74-
3. Share your solution on other social channels like LinkedIn.
75-
4. Blog about your experience building your project. Writing about your workflow, technical choices, and talking through your code is a brilliant way to reinforce what you've learned. Great platforms to write on are [dev.to](https://dev.to/), [Hashnode](https://hashnode.com/), and [CodeNewbie](https://community.codenewbie.org/).
76-
77-
We provide templates to help you share your solution once you've submitted it on the platform. Please do edit them and include specific questions when you're looking for feedback.
78-
79-
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
80-
81-
## Got feedback for us?
82-
83-
We love receiving feedback! We're always looking to improve our challenges and our platform. So if you have anything you'd like to mention, please email hi[at]frontendmentor[dot]io.
84-
85-
This challenge is completely free. Please share it with anyone who will find it useful for practice.
86-
87-
**Have fun building!** 🚀
56+
- Website - [Joy Effiong](https://desire4tech.github.io/Frontend-projects/)
57+
- Frontend Mentor - [@Desire4tech](https://www.frontendmentor.io/profile/Desire4tech)
58+
- Twitter - [@Clazzical_Joy](https://www.twitter.com/Clazzical_Joy)
-24.1 KB
Binary file not shown.
-24.5 KB
Binary file not shown.

qr-code-component-main/preview.jpg

-33.1 KB
Binary file not shown.
79.3 KB
Loading
49.9 KB
Loading

qr-code-component-main/style.css

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@ body {
99
background-color: hsl(0, 0%, 100%);
1010
border-radius: 20px;
1111
margin: 200px auto 200px auto;
12-
padding: 16px 16px 40px;
1312
box-shadow: 0px 25px 25px 0px rgba(0, 0, 0, 0.05);
13+
padding: 16px 16px 40px;
1414
display: flex;
1515
flex-direction: column;
1616
align-items: flex-start;

0 commit comments

Comments
 (0)