renamed readme files, and copied the index and assets out for the two premium packages
This commit is contained in:
parent
97e9160ae5
commit
461c76ab61
|
|
@ -0,0 +1,94 @@
|
||||||
|
# Frontend Mentor - Interactive rating component
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Welcome! 👋
|
||||||
|
|
||||||
|
Thanks for checking out this front-end coding challenge.
|
||||||
|
|
||||||
|
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects.
|
||||||
|
|
||||||
|
**To do this challenge, you need a basic understanding of HTML, CSS and JavaScript.**
|
||||||
|
|
||||||
|
## The challenge
|
||||||
|
|
||||||
|
Your challenge is to build out this interactive rating component 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 app depending on their device's screen size
|
||||||
|
- See hover states for all interactive elements on the page
|
||||||
|
- Select and submit a number rating
|
||||||
|
- See the "Thank you" card state after submitting a rating
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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`.
|
||||||
|
|
||||||
|
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).
|
||||||
|
|
||||||
|
You will find all the required assets in the `/images` folder. The assets are already optimized.
|
||||||
|
|
||||||
|
There is also a `style-guide.md` file containing 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/). 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/).
|
||||||
|
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.
|
||||||
|
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.
|
||||||
|
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.
|
||||||
|
|
||||||
|
## Deploying your project
|
||||||
|
|
||||||
|
As mentioned above, there are many ways to host your project for free. Our recommend hosts are:
|
||||||
|
|
||||||
|
- [GitHub Pages](https://pages.github.com/)
|
||||||
|
- [Vercel](https://vercel.com/)
|
||||||
|
- [Netlify](https://www.netlify.com/)
|
||||||
|
|
||||||
|
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).
|
||||||
|
|
||||||
|
## Create a custom `README.md`
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
## Submitting your solution
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
## Sharing your solution
|
||||||
|
|
||||||
|
There are multiple places you can share your solution:
|
||||||
|
|
||||||
|
1. Share your solution page in the **#finished-projects** channel of the [Slack community](https://www.frontendmentor.io/slack).
|
||||||
|
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.
|
||||||
|
3. Share your solution on other social channels like LinkedIn.
|
||||||
|
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/).
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
|
||||||
|
|
||||||
|
## Got feedback for us?
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
This challenge is completely free. Please share it with anyone who will find it useful for practice.
|
||||||
|
|
||||||
|
**Have fun building!** 🚀
|
||||||
|
|
@ -1,113 +0,0 @@
|
||||||
# Frontend Mentor - Interactive rating component solution
|
|
||||||
|
|
||||||
This is a solution to the [Interactive rating component challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/interactive-rating-component-koxpeBUmI). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
|
|
||||||
|
|
||||||
## 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)
|
|
||||||
- [Useful resources](#useful-resources)
|
|
||||||
- [Author](#author)
|
|
||||||
- [Acknowledgments](#acknowledgments)
|
|
||||||
|
|
||||||
**Note: Delete this note and update the table of contents based on what sections you keep.**
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
### The challenge
|
|
||||||
|
|
||||||
Users should be able to:
|
|
||||||
|
|
||||||
- View the optimal layout for the app depending on their device's screen size
|
|
||||||
- See hover states for all interactive elements on the page
|
|
||||||
- Select and submit a number rating
|
|
||||||
- See the "Thank you" card state after submitting a rating
|
|
||||||
|
|
||||||
### Screenshot
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.
|
|
||||||
|
|
||||||
Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it.
|
|
||||||
|
|
||||||
Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.
|
|
||||||
|
|
||||||
**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**
|
|
||||||
|
|
||||||
### Links
|
|
||||||
|
|
||||||
- Solution URL: [Add solution URL here](https://your-solution-url.com)
|
|
||||||
- Live Site URL: [Add live site URL here](https://your-live-site-url.com)
|
|
||||||
|
|
||||||
## My process
|
|
||||||
|
|
||||||
### Built with
|
|
||||||
|
|
||||||
- Semantic HTML5 markup
|
|
||||||
- CSS custom properties
|
|
||||||
- Flexbox
|
|
||||||
- CSS Grid
|
|
||||||
- Mobile-first workflow
|
|
||||||
- [React](https://reactjs.org/) - JS library
|
|
||||||
- [Next.js](https://nextjs.org/) - React framework
|
|
||||||
- [Styled Components](https://styled-components.com/) - For styles
|
|
||||||
|
|
||||||
**Note: These are just examples. Delete this note and replace the list above with your own choices**
|
|
||||||
|
|
||||||
### What I learned
|
|
||||||
|
|
||||||
Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.
|
|
||||||
|
|
||||||
To see how you can add code snippets, see below:
|
|
||||||
|
|
||||||
```html
|
|
||||||
<h1>Some HTML code I'm proud of</h1>
|
|
||||||
```
|
|
||||||
```css
|
|
||||||
.proud-of-this-css {
|
|
||||||
color: papayawhip;
|
|
||||||
}
|
|
||||||
```
|
|
||||||
```js
|
|
||||||
const proudOfThisFunc = () => {
|
|
||||||
console.log('🎉')
|
|
||||||
}
|
|
||||||
```
|
|
||||||
|
|
||||||
If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more.
|
|
||||||
|
|
||||||
**Note: Delete this note and the content within this section and replace with your own learnings.**
|
|
||||||
|
|
||||||
### Continued development
|
|
||||||
|
|
||||||
Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.
|
|
||||||
|
|
||||||
**Note: Delete this note and the content within this section and replace with your own plans for continued development.**
|
|
||||||
|
|
||||||
### Useful resources
|
|
||||||
|
|
||||||
- [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
|
|
||||||
- [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.
|
|
||||||
|
|
||||||
**Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.**
|
|
||||||
|
|
||||||
## Author
|
|
||||||
|
|
||||||
- Website - [Add your name here](https://www.your-site.com)
|
|
||||||
- Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername)
|
|
||||||
- Twitter - [@yourusername](https://www.twitter.com/yourusername)
|
|
||||||
|
|
||||||
**Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.**
|
|
||||||
|
|
||||||
## Acknowledgments
|
|
||||||
|
|
||||||
This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.
|
|
||||||
|
|
||||||
**Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
|
|
||||||
|
|
@ -1,94 +1,113 @@
|
||||||
# Frontend Mentor - Interactive rating component
|
# Frontend Mentor - Interactive rating component solution
|
||||||
|
|
||||||
|
This is a solution to the [Interactive rating component challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/interactive-rating-component-koxpeBUmI). 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.
|
- [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)
|
||||||
|
- [Useful resources](#useful-resources)
|
||||||
|
- [Author](#author)
|
||||||
|
- [Acknowledgments](#acknowledgments)
|
||||||
|
|
||||||
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects.
|
**Note: Delete this note and update the table of contents based on what sections you keep.**
|
||||||
|
|
||||||
**To do this challenge, you need a basic understanding of HTML, CSS and JavaScript.**
|
## Overview
|
||||||
|
|
||||||
## The challenge
|
### The challenge
|
||||||
|
|
||||||
Your challenge is to build out this interactive rating component and get it looking as close to the design as possible.
|
Users should be able to:
|
||||||
|
|
||||||
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 app depending on their device's screen size
|
- View the optimal layout for the app depending on their device's screen size
|
||||||
- See hover states for all interactive elements on the page
|
- See hover states for all interactive elements on the page
|
||||||
- Select and submit a number rating
|
- Select and submit a number rating
|
||||||
- See the "Thank you" card state after submitting a rating
|
- See the "Thank you" card state after submitting a rating
|
||||||
|
|
||||||
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.
|
Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.
|
||||||
|
|
||||||
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`.
|
Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it.
|
||||||
|
|
||||||
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).
|
Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.
|
||||||
|
|
||||||
You will find all the required assets in the `/images` folder. The assets are already optimized.
|
**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**
|
||||||
|
|
||||||
There is also a `style-guide.md` file containing the information you'll need, such as color palette and fonts.
|
### Links
|
||||||
|
|
||||||
## Building your project
|
- Solution URL: [Add solution URL here](https://your-solution-url.com)
|
||||||
|
- Live Site URL: [Add live site URL here](https://your-live-site-url.com)
|
||||||
|
|
||||||
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:
|
## My process
|
||||||
|
|
||||||
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/).
|
### Built with
|
||||||
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.
|
|
||||||
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.
|
|
||||||
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.
|
|
||||||
|
|
||||||
## Deploying your project
|
- Semantic HTML5 markup
|
||||||
|
- CSS custom properties
|
||||||
|
- Flexbox
|
||||||
|
- CSS Grid
|
||||||
|
- Mobile-first workflow
|
||||||
|
- [React](https://reactjs.org/) - JS library
|
||||||
|
- [Next.js](https://nextjs.org/) - React framework
|
||||||
|
- [Styled Components](https://styled-components.com/) - For styles
|
||||||
|
|
||||||
As mentioned above, there are many ways to host your project for free. Our recommend hosts are:
|
**Note: These are just examples. Delete this note and replace the list above with your own choices**
|
||||||
|
|
||||||
- [GitHub Pages](https://pages.github.com/)
|
### What I learned
|
||||||
- [Vercel](https://vercel.com/)
|
|
||||||
- [Netlify](https://www.netlify.com/)
|
|
||||||
|
|
||||||
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).
|
Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.
|
||||||
|
|
||||||
## Create a custom `README.md`
|
To see how you can add code snippets, see below:
|
||||||
|
|
||||||
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.
|
```html
|
||||||
|
<h1>Some HTML code I'm proud of</h1>
|
||||||
|
```
|
||||||
|
```css
|
||||||
|
.proud-of-this-css {
|
||||||
|
color: papayawhip;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
```js
|
||||||
|
const proudOfThisFunc = () => {
|
||||||
|
console.log('🎉')
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
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.
|
If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more.
|
||||||
|
|
||||||
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.
|
**Note: Delete this note and the content within this section and replace with your own learnings.**
|
||||||
|
|
||||||
## Submitting your solution
|
### Continued development
|
||||||
|
|
||||||
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.
|
Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.
|
||||||
|
|
||||||
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.
|
**Note: Delete this note and the content within this section and replace with your own plans for continued development.**
|
||||||
|
|
||||||
## Sharing your solution
|
### Useful resources
|
||||||
|
|
||||||
There are multiple places you can share your solution:
|
- [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
|
||||||
|
- [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.
|
||||||
|
|
||||||
1. Share your solution page in the **#finished-projects** channel of the [Slack community](https://www.frontendmentor.io/slack).
|
**Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.**
|
||||||
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.
|
|
||||||
3. Share your solution on other social channels like LinkedIn.
|
|
||||||
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/).
|
|
||||||
|
|
||||||
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.
|
## Author
|
||||||
|
|
||||||
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
|
- Website - [Add your name here](https://www.your-site.com)
|
||||||
|
- Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername)
|
||||||
|
- Twitter - [@yourusername](https://www.twitter.com/yourusername)
|
||||||
|
|
||||||
## Got feedback for us?
|
**Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.**
|
||||||
|
|
||||||
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.
|
## Acknowledgments
|
||||||
|
|
||||||
This challenge is completely free. Please share it with anyone who will find it useful for practice.
|
This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.
|
||||||
|
|
||||||
**Have fun building!** 🚀
|
**Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
|
||||||
|
|
|
||||||
|
|
@ -0,0 +1,88 @@
|
||||||
|
# Frontend Mentor - Meet landing page
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Welcome! 👋
|
||||||
|
|
||||||
|
Thanks for purchasing this premium Frontend Mentor coding challenge.
|
||||||
|
|
||||||
|
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects. These premium challenges are perfect portfolio pieces, so please feel free to use what you create in your portfolio to show others.
|
||||||
|
|
||||||
|
**To do this challenge, you need a decent understanding of HTML & CSS.**
|
||||||
|
|
||||||
|
## The challenge
|
||||||
|
|
||||||
|
Your challenge is to build out this landing page 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 depending on their device's screen size
|
||||||
|
- See hover states for interactive elements
|
||||||
|
|
||||||
|
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 design file provided. We provide both Sketch and Figma versions of the design, so you can choose which tool you prefer to use. You can download the design file on the platform. **Please be sure not to share them with anyone else.** The design download comes with a `README.md` file as well to help you get set up.
|
||||||
|
|
||||||
|
All the required assets for this project are in the `/assets` folder. The assets are already exported for the correct screen size and optimized. Some images are reusable at multiple screen sizes. So if you don't see an image in a specific folder, it will typically be in another folder for that page.
|
||||||
|
|
||||||
|
The design system in the design file will give you more information about the various colors, fonts, and styles used in this project.
|
||||||
|
|
||||||
|
## 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. Separate the `starter-code` from the rest of this project and rename it to something meaningful for you. Initialize the codebase 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/). **⚠️ IMPORTANT ⚠️: There are already a couple of `.gitignore` files in this project. Please do not remove them or change the content of the files. If you create a brand new project, please use the `.gitignore` files provided in your new codebase. This is to avoid the accidental upload of the design files to GitHub. With these premium challenges, please be sure not to share the design files in your GitHub repo. Thanks!**
|
||||||
|
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.
|
||||||
|
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.
|
||||||
|
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.
|
||||||
|
|
||||||
|
## Deploying your project
|
||||||
|
|
||||||
|
As mentioned above, there are many ways to host your project for free. Our recommend hosts are:
|
||||||
|
|
||||||
|
- [GitHub Pages](https://pages.github.com/)
|
||||||
|
- [Vercel](https://vercel.com/)
|
||||||
|
- [Netlify](https://www.netlify.com/)
|
||||||
|
|
||||||
|
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).
|
||||||
|
|
||||||
|
## Create a custom `README.md`
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
## Submitting your solution
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
**⚠️ IMPORTANT ⚠️: With these premium challenges, please be sure not to upload the design files to GitHub when you're submitting to the platform and sharing it around. If you've created a brand new project, the easiest way to do that is to copy across the `.gitignore` provided in this starter project.**
|
||||||
|
|
||||||
|
## Sharing your solution
|
||||||
|
|
||||||
|
There are multiple places you can share your solution:
|
||||||
|
|
||||||
|
1. Share your solution page in the **#finished-projects** channel of the [Slack community](https://www.frontendmentor.io/slack).
|
||||||
|
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.
|
||||||
|
3. Share your solution on other social channels like LinkedIn.
|
||||||
|
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/).
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
|
||||||
|
|
||||||
|
## Got feedback for us?
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
**Have fun building!** 🚀
|
||||||
|
|
@ -1,111 +0,0 @@
|
||||||
# Frontend Mentor - Meet landing page solution
|
|
||||||
|
|
||||||
This is a solution to the [Meet landing page challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/meet-landing-page-rbTDS6OUR). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
|
|
||||||
|
|
||||||
## 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)
|
|
||||||
- [Useful resources](#useful-resources)
|
|
||||||
- [Author](#author)
|
|
||||||
- [Acknowledgments](#acknowledgments)
|
|
||||||
|
|
||||||
**Note: Delete this note and update the table of contents based on what sections you keep.**
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
### The challenge
|
|
||||||
|
|
||||||
Users should be able to:
|
|
||||||
|
|
||||||
- View the optimal layout depending on their device's screen size
|
|
||||||
- See hover states for interactive elements
|
|
||||||
|
|
||||||
### Screenshot
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.
|
|
||||||
|
|
||||||
Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it.
|
|
||||||
|
|
||||||
Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.
|
|
||||||
|
|
||||||
**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**
|
|
||||||
|
|
||||||
### Links
|
|
||||||
|
|
||||||
- Solution URL: [Add solution URL here](https://your-solution-url.com)
|
|
||||||
- Live Site URL: [Add live site URL here](https://your-live-site-url.com)
|
|
||||||
|
|
||||||
## My process
|
|
||||||
|
|
||||||
### Built with
|
|
||||||
|
|
||||||
- Semantic HTML5 markup
|
|
||||||
- CSS custom properties
|
|
||||||
- Flexbox
|
|
||||||
- CSS Grid
|
|
||||||
- Mobile-first workflow
|
|
||||||
- [React](https://reactjs.org/) - JS library
|
|
||||||
- [Next.js](https://nextjs.org/) - React framework
|
|
||||||
- [Styled Components](https://styled-components.com/) - For styles
|
|
||||||
|
|
||||||
**Note: These are just examples. Delete this note and replace the list above with your own choices**
|
|
||||||
|
|
||||||
### What I learned
|
|
||||||
|
|
||||||
Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.
|
|
||||||
|
|
||||||
To see how you can add code snippets, see below:
|
|
||||||
|
|
||||||
```html
|
|
||||||
<h1>Some HTML code I'm proud of</h1>
|
|
||||||
```
|
|
||||||
```css
|
|
||||||
.proud-of-this-css {
|
|
||||||
color: papayawhip;
|
|
||||||
}
|
|
||||||
```
|
|
||||||
```js
|
|
||||||
const proudOfThisFunc = () => {
|
|
||||||
console.log('🎉')
|
|
||||||
}
|
|
||||||
```
|
|
||||||
|
|
||||||
If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more.
|
|
||||||
|
|
||||||
**Note: Delete this note and the content within this section and replace with your own learnings.**
|
|
||||||
|
|
||||||
### Continued development
|
|
||||||
|
|
||||||
Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.
|
|
||||||
|
|
||||||
**Note: Delete this note and the content within this section and replace with your own plans for continued development.**
|
|
||||||
|
|
||||||
### Useful resources
|
|
||||||
|
|
||||||
- [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
|
|
||||||
- [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.
|
|
||||||
|
|
||||||
**Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.**
|
|
||||||
|
|
||||||
## Author
|
|
||||||
|
|
||||||
- Website - [Add your name here](https://www.your-site.com)
|
|
||||||
- Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername)
|
|
||||||
- Twitter - [@yourusername](https://www.twitter.com/yourusername)
|
|
||||||
|
|
||||||
**Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.**
|
|
||||||
|
|
||||||
## Acknowledgments
|
|
||||||
|
|
||||||
This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.
|
|
||||||
|
|
||||||
**Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
|
|
||||||
|
|
@ -1,88 +1,111 @@
|
||||||
# Frontend Mentor - Meet landing page
|
# Frontend Mentor - Meet landing page solution
|
||||||
|
|
||||||
|
This is a solution to the [Meet landing page challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/meet-landing-page-rbTDS6OUR). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
|
||||||
|
|
||||||
## Welcome! 👋
|
## Table of contents
|
||||||
|
|
||||||
Thanks for purchasing this premium Frontend Mentor coding challenge.
|
- [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)
|
||||||
|
- [Useful resources](#useful-resources)
|
||||||
|
- [Author](#author)
|
||||||
|
- [Acknowledgments](#acknowledgments)
|
||||||
|
|
||||||
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects. These premium challenges are perfect portfolio pieces, so please feel free to use what you create in your portfolio to show others.
|
**Note: Delete this note and update the table of contents based on what sections you keep.**
|
||||||
|
|
||||||
**To do this challenge, you need a decent understanding of HTML & CSS.**
|
## Overview
|
||||||
|
|
||||||
## The challenge
|
### The challenge
|
||||||
|
|
||||||
Your challenge is to build out this landing page and get it looking as close to the design as possible.
|
Users should be able to:
|
||||||
|
|
||||||
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 depending on their device's screen size
|
- View the optimal layout depending on their device's screen size
|
||||||
- See hover states for interactive elements
|
- See hover states for interactive elements
|
||||||
|
|
||||||
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 design file provided. We provide both Sketch and Figma versions of the design, so you can choose which tool you prefer to use. You can download the design file on the platform. **Please be sure not to share them with anyone else.** The design download comes with a `README.md` file as well to help you get set up.
|
Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.
|
||||||
|
|
||||||
All the required assets for this project are in the `/assets` folder. The assets are already exported for the correct screen size and optimized. Some images are reusable at multiple screen sizes. So if you don't see an image in a specific folder, it will typically be in another folder for that page.
|
Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it.
|
||||||
|
|
||||||
The design system in the design file will give you more information about the various colors, fonts, and styles used in this project.
|
Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.
|
||||||
|
|
||||||
## Building your project
|
**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**
|
||||||
|
|
||||||
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:
|
### Links
|
||||||
|
|
||||||
1. Separate the `starter-code` from the rest of this project and rename it to something meaningful for you. Initialize the codebase 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/). **⚠️ IMPORTANT ⚠️: There are already a couple of `.gitignore` files in this project. Please do not remove them or change the content of the files. If you create a brand new project, please use the `.gitignore` files provided in your new codebase. This is to avoid the accidental upload of the design files to GitHub. With these premium challenges, please be sure not to share the design files in your GitHub repo. Thanks!**
|
- Solution URL: [Add solution URL here](https://your-solution-url.com)
|
||||||
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.
|
- Live Site URL: [Add live site URL here](https://your-live-site-url.com)
|
||||||
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.
|
|
||||||
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.
|
|
||||||
|
|
||||||
## Deploying your project
|
## My process
|
||||||
|
|
||||||
As mentioned above, there are many ways to host your project for free. Our recommend hosts are:
|
### Built with
|
||||||
|
|
||||||
- [GitHub Pages](https://pages.github.com/)
|
- Semantic HTML5 markup
|
||||||
- [Vercel](https://vercel.com/)
|
- CSS custom properties
|
||||||
- [Netlify](https://www.netlify.com/)
|
- Flexbox
|
||||||
|
- CSS Grid
|
||||||
|
- Mobile-first workflow
|
||||||
|
- [React](https://reactjs.org/) - JS library
|
||||||
|
- [Next.js](https://nextjs.org/) - React framework
|
||||||
|
- [Styled Components](https://styled-components.com/) - For styles
|
||||||
|
|
||||||
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).
|
**Note: These are just examples. Delete this note and replace the list above with your own choices**
|
||||||
|
|
||||||
## Create a custom `README.md`
|
### What I learned
|
||||||
|
|
||||||
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.
|
Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.
|
||||||
|
|
||||||
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.
|
To see how you can add code snippets, see below:
|
||||||
|
|
||||||
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.
|
```html
|
||||||
|
<h1>Some HTML code I'm proud of</h1>
|
||||||
|
```
|
||||||
|
```css
|
||||||
|
.proud-of-this-css {
|
||||||
|
color: papayawhip;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
```js
|
||||||
|
const proudOfThisFunc = () => {
|
||||||
|
console.log('🎉')
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
## Submitting your solution
|
If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more.
|
||||||
|
|
||||||
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.
|
**Note: Delete this note and the content within this section and replace with your own learnings.**
|
||||||
|
|
||||||
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.
|
### Continued development
|
||||||
|
|
||||||
**⚠️ IMPORTANT ⚠️: With these premium challenges, please be sure not to upload the design files to GitHub when you're submitting to the platform and sharing it around. If you've created a brand new project, the easiest way to do that is to copy across the `.gitignore` provided in this starter project.**
|
Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.
|
||||||
|
|
||||||
## Sharing your solution
|
**Note: Delete this note and the content within this section and replace with your own plans for continued development.**
|
||||||
|
|
||||||
There are multiple places you can share your solution:
|
### Useful resources
|
||||||
|
|
||||||
1. Share your solution page in the **#finished-projects** channel of the [Slack community](https://www.frontendmentor.io/slack).
|
- [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
|
||||||
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.
|
- [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.
|
||||||
3. Share your solution on other social channels like LinkedIn.
|
|
||||||
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/).
|
|
||||||
|
|
||||||
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.
|
**Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.**
|
||||||
|
|
||||||
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
|
## Author
|
||||||
|
|
||||||
## Got feedback for us?
|
- Website - [Add your name here](https://www.your-site.com)
|
||||||
|
- Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername)
|
||||||
|
- Twitter - [@yourusername](https://www.twitter.com/yourusername)
|
||||||
|
|
||||||
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.
|
**Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.**
|
||||||
|
|
||||||
**Have fun building!** 🚀
|
## Acknowledgments
|
||||||
|
|
||||||
|
This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.
|
||||||
|
|
||||||
|
**Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
|
||||||
|
|
|
||||||
BIN
projects/FrontendMentor/newbie/meet-landing-page/assets/desktop/image-footer.jpg
Executable file
BIN
projects/FrontendMentor/newbie/meet-landing-page/assets/desktop/image-footer.jpg
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 37 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 133 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 133 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 32 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.0 KiB |
|
|
@ -0,0 +1 @@
|
||||||
|
<svg width="119" height="28" xmlns="http://www.w3.org/2000/svg"><g fill="none" fill-rule="evenodd"><g><circle fill="#4D96A9" cx="7" cy="21" r="7"/><circle fill="#855FB1" cx="21" cy="7" r="7"/></g><path d="M44.121 25.676V13.95c.316-.41.701-.718 1.154-.923a3.677 3.677 0 011.533-.308c.822 0 1.48.286 1.976.859.495.572.743 1.323.743 2.251v9.848h5.121v-10.56c0-.195-.005-.384-.016-.567a8.383 8.383 0 00-.047-.535c.337-.41.738-.729 1.201-.956.464-.226.98-.34 1.55-.34.821 0 1.48.286 1.975.859.495.572.743 1.323.743 2.251v9.848h5.121v-10.56c0-2.009-.606-3.661-1.817-4.957-1.212-1.296-2.767-1.944-4.663-1.944-1.096 0-2.108.206-3.035.616a6.956 6.956 0 00-2.403 1.75 6.042 6.042 0 00-2.134-1.734c-.853-.42-1.796-.632-2.829-.632-.78 0-1.523.12-2.229.357a6.264 6.264 0 00-1.944 1.069V8.539H39v17.137h5.121zM76.556 26c1.39 0 2.64-.205 3.746-.615 1.106-.41 2.186-1.07 3.24-1.977l-3.382-3.077c-.4.41-.885.729-1.455.956a5.082 5.082 0 01-1.896.34c-.97 0-1.813-.254-2.53-.762a4.508 4.508 0 01-1.58-1.96h11.918V17.61c0-1.34-.21-2.586-.632-3.742-.422-1.155-1.007-2.143-1.755-2.964a8.225 8.225 0 00-2.671-1.943c-1.033-.476-2.16-.713-3.383-.713a8.657 8.657 0 00-3.43.68 8.445 8.445 0 00-2.766 1.879 8.9 8.9 0 00-1.849 2.835 8.985 8.985 0 00-.68 3.482c0 1.23.237 2.392.712 3.482a8.93 8.93 0 001.928 2.835 8.776 8.776 0 002.893 1.879 9.404 9.404 0 003.572.68zm3.035-10.755h-6.987c.253-.864.685-1.533 1.296-2.008.612-.475 1.339-.713 2.182-.713.822 0 1.543.248 2.165.745.622.497 1.07 1.155 1.344 1.976zM95.365 26c1.391 0 2.64-.205 3.746-.615 1.107-.41 2.187-1.07 3.24-1.977l-3.382-3.077c-.4.41-.885.729-1.454.956a5.082 5.082 0 01-1.897.34c-.97 0-1.812-.254-2.529-.762a4.508 4.508 0 01-1.58-1.96h11.918V17.61c0-1.34-.211-2.586-.633-3.742-.421-1.155-1.006-2.143-1.754-2.964a8.225 8.225 0 00-2.671-1.943c-1.033-.476-2.16-.713-3.383-.713a8.657 8.657 0 00-3.43.68 8.445 8.445 0 00-2.766 1.879 8.9 8.9 0 00-1.85 2.835 8.985 8.985 0 00-.68 3.482c0 1.23.238 2.392.712 3.482a8.93 8.93 0 001.929 2.835 8.776 8.776 0 002.892 1.879 9.404 9.404 0 003.572.68zM98.4 15.245h-6.986c.253-.864.685-1.533 1.296-2.008.611-.475 1.338-.713 2.181-.713.822 0 1.544.248 2.166.745.621.497 1.07 1.155 1.343 1.976zm15.87 10.658c.484 0 1.085-.049 1.802-.146.716-.097 1.306-.221 1.77-.372V21.14c-.422.13-.811.221-1.17.275a7.639 7.639 0 01-1.138.081c-.822 0-1.396-.156-1.723-.47-.326-.313-.49-.847-.49-1.603v-6.511H118V8.539h-4.679V3l-5.12 1.134v4.405h-3.383v4.374h3.382v7.548c0 1.792.511 3.147 1.533 4.065 1.022.918 2.535 1.377 4.537 1.377z" fill="#28283D" fill-rule="nonzero"/></g></svg>
|
||||||
|
After Width: | Height: | Size: 2.5 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 48 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 31 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 266 KiB |
|
|
@ -0,0 +1,31 @@
|
||||||
|
<!DOCTYPE html>
|
||||||
|
<html lang="en">
|
||||||
|
<head>
|
||||||
|
<meta charset="UTF-8">
|
||||||
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||||
|
|
||||||
|
<link rel="icon" type="image/png" sizes="32x32" href="./assets/favicon-32x32.png">
|
||||||
|
|
||||||
|
<title>Frontend Mentor | Meet landing page</title>
|
||||||
|
</head>
|
||||||
|
<body>
|
||||||
|
Meet makes it easy to connect with others face-to-face virtually and collaborate across any device.
|
||||||
|
|
||||||
|
Download v1.3
|
||||||
|
What is it?
|
||||||
|
|
||||||
|
01
|
||||||
|
Built for modern use
|
||||||
|
|
||||||
|
Smarter meetings, all in one place
|
||||||
|
|
||||||
|
Send messages, share files, show your screen, and record your meetings — all in one
|
||||||
|
workspace. Control who can join with invite-only team access, data encryption, and data export.
|
||||||
|
|
||||||
|
02
|
||||||
|
Experience more together
|
||||||
|
Stay connected with reliable HD meetings and unlimited one-on-one and group video sessions.
|
||||||
|
|
||||||
|
Download v1.3
|
||||||
|
</body>
|
||||||
|
</html>
|
||||||
|
|
@ -0,0 +1,12 @@
|
||||||
|
Some notes from reviewing other peoples solutions:
|
||||||
|
|
||||||
|
```
|
||||||
|
text-rendering: optimizeLegibility;
|
||||||
|
-webkit-font-smoothing: antialiased;
|
||||||
|
-moz-osx-font-smoothing: grayscale;
|
||||||
|
-webkit-text-size-adjust: 100%;
|
||||||
|
```
|
||||||
|
|
||||||
|
Better responsiveness.
|
||||||
|
|
||||||
|
Add focus for keyboard users.
|
||||||
|
|
@ -0,0 +1,88 @@
|
||||||
|
# Frontend Mentor - Skilled e-learning landing page
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## Welcome! 👋
|
||||||
|
|
||||||
|
Thanks for purchasing this premium Frontend Mentor coding challenge.
|
||||||
|
|
||||||
|
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects. These premium challenges are perfect portfolio pieces, so please feel free to use what you create in your portfolio to show others.
|
||||||
|
|
||||||
|
**To do this challenge, you need a decent understanding of HTML and CSS.**
|
||||||
|
|
||||||
|
## The challenge
|
||||||
|
|
||||||
|
Your challenge is to build out this landing page 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 depending on their device's screen size
|
||||||
|
- See hover states for interactive elements
|
||||||
|
|
||||||
|
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 design file provided. We provide both Sketch and Figma versions of the design, so you can choose which tool you prefer to use. You can download the design file on the platform. **Please be sure not to share them with anyone else.** The design download comes with a `README.md` file as well to help you get set up.
|
||||||
|
|
||||||
|
All the required assets for this project are in the `/assets` folder. The assets are already exported for the correct screen size and optimized. Some images are reusable at multiple screen sizes, some are for specific layouts. We also include WEBP and PNG versions and different resolutions of the hero image, so you can choose to use whichever format and resolution you like or even look into letting the browser choose which image to use based on specific conditions. For this, you can look into [responsive images](https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images) to learn more.
|
||||||
|
|
||||||
|
The design system in the design file will give you more information about the various colors, fonts, and styles used in this project. Our fonts always come from [Google Fonts](https://fonts.google.com/).
|
||||||
|
|
||||||
|
## 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. Separate the `starter-code` from the rest of this project and rename it to something meaningful for you. Initialize the codebase 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/). **⚠️ IMPORTANT ⚠️: There are already a couple of `.gitignore` files in this project. Please do not remove them or change the content of the files. If you create a brand new project, please use the `.gitignore` files provided in your new codebase. This is to avoid the accidental upload of the design files to GitHub. With these premium challenges, please be sure not to share the design files in your GitHub repo. Thanks!**
|
||||||
|
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.
|
||||||
|
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.
|
||||||
|
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.
|
||||||
|
|
||||||
|
## Deploying your project
|
||||||
|
|
||||||
|
As mentioned above, there are many ways to host your project for free. Our recommend hosts are:
|
||||||
|
|
||||||
|
- [GitHub Pages](https://pages.github.com/)
|
||||||
|
- [Vercel](https://vercel.com/)
|
||||||
|
- [Netlify](https://www.netlify.com/)
|
||||||
|
|
||||||
|
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).
|
||||||
|
|
||||||
|
## Create a custom `README.md`
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
## Submitting your solution
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
**⚠️ IMPORTANT ⚠️: With these premium challenges, please be sure not to upload the design files to GitHub when you're submitting to the platform and sharing it around. If you've created a brand new project, the easiest way to do that is to copy across the `.gitignore` provided in this starter project.**
|
||||||
|
|
||||||
|
## Sharing your solution
|
||||||
|
|
||||||
|
There are multiple places you can share your solution:
|
||||||
|
|
||||||
|
1. Share your solution page in the **#finished-projects** channel of the [Slack community](https://www.frontendmentor.io/slack).
|
||||||
|
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.
|
||||||
|
3. Share your solution on other social channels like LinkedIn.
|
||||||
|
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/).
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
|
||||||
|
|
||||||
|
## Got feedback for us?
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
**Have fun building!** 🚀
|
||||||
|
|
@ -1,111 +0,0 @@
|
||||||
# Frontend Mentor - Skilled e-learning landing page solution
|
|
||||||
|
|
||||||
This is a solution to the [Skilled e-learning landing page challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/skilled-elearning-landing-page-S1ObDrZ8q). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
|
|
||||||
|
|
||||||
## 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)
|
|
||||||
- [Useful resources](#useful-resources)
|
|
||||||
- [Author](#author)
|
|
||||||
- [Acknowledgments](#acknowledgments)
|
|
||||||
|
|
||||||
**Note: Delete this note and update the table of contents based on what sections you keep.**
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
### The challenge
|
|
||||||
|
|
||||||
Users should be able to:
|
|
||||||
|
|
||||||
- View the optimal layout depending on their device's screen size
|
|
||||||
- See hover states for interactive elements
|
|
||||||
|
|
||||||
### Screenshot
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.
|
|
||||||
|
|
||||||
Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it.
|
|
||||||
|
|
||||||
Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.
|
|
||||||
|
|
||||||
**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**
|
|
||||||
|
|
||||||
### Links
|
|
||||||
|
|
||||||
- Solution URL: [Add solution URL here](https://your-solution-url.com)
|
|
||||||
- Live Site URL: [Add live site URL here](https://your-live-site-url.com)
|
|
||||||
|
|
||||||
## My process
|
|
||||||
|
|
||||||
### Built with
|
|
||||||
|
|
||||||
- Semantic HTML5 markup
|
|
||||||
- CSS custom properties
|
|
||||||
- Flexbox
|
|
||||||
- CSS Grid
|
|
||||||
- Mobile-first workflow
|
|
||||||
- [React](https://reactjs.org/) - JS library
|
|
||||||
- [Next.js](https://nextjs.org/) - React framework
|
|
||||||
- [Styled Components](https://styled-components.com/) - For styles
|
|
||||||
|
|
||||||
**Note: These are just examples. Delete this note and replace the list above with your own choices**
|
|
||||||
|
|
||||||
### What I learned
|
|
||||||
|
|
||||||
Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.
|
|
||||||
|
|
||||||
To see how you can add code snippets, see below:
|
|
||||||
|
|
||||||
```html
|
|
||||||
<h1>Some HTML code I'm proud of</h1>
|
|
||||||
```
|
|
||||||
```css
|
|
||||||
.proud-of-this-css {
|
|
||||||
color: papayawhip;
|
|
||||||
}
|
|
||||||
```
|
|
||||||
```js
|
|
||||||
const proudOfThisFunc = () => {
|
|
||||||
console.log('🎉')
|
|
||||||
}
|
|
||||||
```
|
|
||||||
|
|
||||||
If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more.
|
|
||||||
|
|
||||||
**Note: Delete this note and the content within this section and replace with your own learnings.**
|
|
||||||
|
|
||||||
### Continued development
|
|
||||||
|
|
||||||
Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.
|
|
||||||
|
|
||||||
**Note: Delete this note and the content within this section and replace with your own plans for continued development.**
|
|
||||||
|
|
||||||
### Useful resources
|
|
||||||
|
|
||||||
- [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
|
|
||||||
- [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.
|
|
||||||
|
|
||||||
**Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.**
|
|
||||||
|
|
||||||
## Author
|
|
||||||
|
|
||||||
- Website - [Add your name here](https://www.your-site.com)
|
|
||||||
- Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername)
|
|
||||||
- Twitter - [@yourusername](https://www.twitter.com/yourusername)
|
|
||||||
|
|
||||||
**Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.**
|
|
||||||
|
|
||||||
## Acknowledgments
|
|
||||||
|
|
||||||
This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.
|
|
||||||
|
|
||||||
**Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
|
|
||||||
|
|
@ -1,88 +1,111 @@
|
||||||
# Frontend Mentor - Skilled e-learning landing page
|
# Frontend Mentor - Skilled e-learning landing page solution
|
||||||
|
|
||||||
|
This is a solution to the [Skilled e-learning landing page challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/skilled-elearning-landing-page-S1ObDrZ8q). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
|
||||||
|
|
||||||
## Welcome! 👋
|
## Table of contents
|
||||||
|
|
||||||
Thanks for purchasing this premium Frontend Mentor coding challenge.
|
- [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)
|
||||||
|
- [Useful resources](#useful-resources)
|
||||||
|
- [Author](#author)
|
||||||
|
- [Acknowledgments](#acknowledgments)
|
||||||
|
|
||||||
[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects. These premium challenges are perfect portfolio pieces, so please feel free to use what you create in your portfolio to show others.
|
**Note: Delete this note and update the table of contents based on what sections you keep.**
|
||||||
|
|
||||||
**To do this challenge, you need a decent understanding of HTML and CSS.**
|
## Overview
|
||||||
|
|
||||||
## The challenge
|
### The challenge
|
||||||
|
|
||||||
Your challenge is to build out this landing page and get it looking as close to the design as possible.
|
Users should be able to:
|
||||||
|
|
||||||
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 depending on their device's screen size
|
- View the optimal layout depending on their device's screen size
|
||||||
- See hover states for interactive elements
|
- See hover states for interactive elements
|
||||||
|
|
||||||
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 design file provided. We provide both Sketch and Figma versions of the design, so you can choose which tool you prefer to use. You can download the design file on the platform. **Please be sure not to share them with anyone else.** The design download comes with a `README.md` file as well to help you get set up.
|
Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.
|
||||||
|
|
||||||
All the required assets for this project are in the `/assets` folder. The assets are already exported for the correct screen size and optimized. Some images are reusable at multiple screen sizes, some are for specific layouts. We also include WEBP and PNG versions and different resolutions of the hero image, so you can choose to use whichever format and resolution you like or even look into letting the browser choose which image to use based on specific conditions. For this, you can look into [responsive images](https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images) to learn more.
|
Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it.
|
||||||
|
|
||||||
The design system in the design file will give you more information about the various colors, fonts, and styles used in this project. Our fonts always come from [Google Fonts](https://fonts.google.com/).
|
Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.
|
||||||
|
|
||||||
## Building your project
|
**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**
|
||||||
|
|
||||||
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:
|
### Links
|
||||||
|
|
||||||
1. Separate the `starter-code` from the rest of this project and rename it to something meaningful for you. Initialize the codebase 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/). **⚠️ IMPORTANT ⚠️: There are already a couple of `.gitignore` files in this project. Please do not remove them or change the content of the files. If you create a brand new project, please use the `.gitignore` files provided in your new codebase. This is to avoid the accidental upload of the design files to GitHub. With these premium challenges, please be sure not to share the design files in your GitHub repo. Thanks!**
|
- Solution URL: [Add solution URL here](https://your-solution-url.com)
|
||||||
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.
|
- Live Site URL: [Add live site URL here](https://your-live-site-url.com)
|
||||||
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.
|
|
||||||
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.
|
|
||||||
|
|
||||||
## Deploying your project
|
## My process
|
||||||
|
|
||||||
As mentioned above, there are many ways to host your project for free. Our recommend hosts are:
|
### Built with
|
||||||
|
|
||||||
- [GitHub Pages](https://pages.github.com/)
|
- Semantic HTML5 markup
|
||||||
- [Vercel](https://vercel.com/)
|
- CSS custom properties
|
||||||
- [Netlify](https://www.netlify.com/)
|
- Flexbox
|
||||||
|
- CSS Grid
|
||||||
|
- Mobile-first workflow
|
||||||
|
- [React](https://reactjs.org/) - JS library
|
||||||
|
- [Next.js](https://nextjs.org/) - React framework
|
||||||
|
- [Styled Components](https://styled-components.com/) - For styles
|
||||||
|
|
||||||
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).
|
**Note: These are just examples. Delete this note and replace the list above with your own choices**
|
||||||
|
|
||||||
## Create a custom `README.md`
|
### What I learned
|
||||||
|
|
||||||
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.
|
Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.
|
||||||
|
|
||||||
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.
|
To see how you can add code snippets, see below:
|
||||||
|
|
||||||
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.
|
```html
|
||||||
|
<h1>Some HTML code I'm proud of</h1>
|
||||||
|
```
|
||||||
|
```css
|
||||||
|
.proud-of-this-css {
|
||||||
|
color: papayawhip;
|
||||||
|
}
|
||||||
|
```
|
||||||
|
```js
|
||||||
|
const proudOfThisFunc = () => {
|
||||||
|
console.log('🎉')
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
## Submitting your solution
|
If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more.
|
||||||
|
|
||||||
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.
|
**Note: Delete this note and the content within this section and replace with your own learnings.**
|
||||||
|
|
||||||
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.
|
### Continued development
|
||||||
|
|
||||||
**⚠️ IMPORTANT ⚠️: With these premium challenges, please be sure not to upload the design files to GitHub when you're submitting to the platform and sharing it around. If you've created a brand new project, the easiest way to do that is to copy across the `.gitignore` provided in this starter project.**
|
Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.
|
||||||
|
|
||||||
## Sharing your solution
|
**Note: Delete this note and the content within this section and replace with your own plans for continued development.**
|
||||||
|
|
||||||
There are multiple places you can share your solution:
|
### Useful resources
|
||||||
|
|
||||||
1. Share your solution page in the **#finished-projects** channel of the [Slack community](https://www.frontendmentor.io/slack).
|
- [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
|
||||||
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.
|
- [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.
|
||||||
3. Share your solution on other social channels like LinkedIn.
|
|
||||||
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/).
|
|
||||||
|
|
||||||
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.
|
**Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.**
|
||||||
|
|
||||||
The more specific you are with your questions the more likely it is that another member of the community will give you feedback.
|
## Author
|
||||||
|
|
||||||
## Got feedback for us?
|
- Website - [Add your name here](https://www.your-site.com)
|
||||||
|
- Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername)
|
||||||
|
- Twitter - [@yourusername](https://www.twitter.com/yourusername)
|
||||||
|
|
||||||
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.
|
**Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.**
|
||||||
|
|
||||||
**Have fun building!** 🚀
|
## Acknowledgments
|
||||||
|
|
||||||
|
This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.
|
||||||
|
|
||||||
|
**Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**
|
||||||
|
|
|
||||||
Binary file not shown.
|
After Width: | Height: | Size: 1.0 KiB |
|
|
@ -0,0 +1 @@
|
||||||
|
<svg width="56" height="56" xmlns="http://www.w3.org/2000/svg"><defs><linearGradient x1="50%" y1="0%" x2="50%" y2="100%" id="a"><stop stop-color="#FF6F48" offset="0%"/><stop stop-color="#F02AA6" offset="100%"/></linearGradient></defs><g fill="none" fill-rule="evenodd"><circle fill="url(#a)" cx="28" cy="28" r="28"/><path d="M33.97 20.678c.565-.498.893-1.21.906-1.962A2.706 2.706 0 0 0 32.16 16a2.794 2.794 0 0 0-1.66.603 2.825 2.825 0 0 0-.854 1.962 2.69 2.69 0 0 0 4.325 2.113Zm-8.752.453c0 .05-.05.05-.1.1v.05a6.308 6.308 0 0 0-2.919 1.41c-.503.473-.958.995-1.358 1.559-1.006 1.408 1.358 2.766 2.315 1.358 1.257-1.762 2.816-2.264 4.527-1.71a141.96 141.96 0 0 0-2.717 5.181c-1.107 2.163-3.47 3.874-5.786 2.566a1.402 1.402 0 1 0-1.508 2.364 6.826 6.826 0 0 0 8.704-1.66c.05 0 .153.05.2.05 1.5.624 2.907 1.454 4.177 2.466.603.502 1.66 3.065 2.263 4.376a1.392 1.392 0 0 0 2.113.452c.393-.382.476-.982.202-1.456-.705-1.456-1.862-4.427-2.818-5.135a31.566 31.566 0 0 0-2.364-1.762l.1-.1a16.972 16.972 0 0 0-1.006-.605c.856-1.609 1.711-3.168 2.616-4.728 2.11.667 4.415.19 6.087-1.258.517-.46.973-.984 1.358-1.56.956-1.257-.905-2.515-2.012-1.66a.709.709 0 0 0-.153.202 4.36 4.36 0 0 1-2.013 1.66c-.05.05-.1.05-.1.1h-.051a4.146 4.146 0 0 1-3.622-.452l.101-.101h.05a.383.383 0 0 0-.201-.1 9.292 9.292 0 0 0-.956-.554 7.258 7.258 0 0 0-5.134-1.056l.005.003Z" fill="#FFF" fill-rule="nonzero"/></g></svg>
|
||||||
|
After Width: | Height: | Size: 1.4 KiB |
|
|
@ -0,0 +1 @@
|
||||||
|
<svg width="56" height="56" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><defs><linearGradient x1="50%" y1="0%" x2="50%" y2="100%" id="a"><stop stop-color="#FF6F48" offset="0%"/><stop stop-color="#F02AA6" offset="100%"/></linearGradient><path d="M35 22h-2c0-2.76-2.24-5-5-5s-5 2.24-5 5h-2c-1.1 0-1.99.9-1.99 2L19 36c0 1.1.9 2 2 2h14c1.1 0 2-.9 2-2V24c0-1.1-.9-2-2-2Zm-7-3c1.66 0 3 1.34 3 3h-6c0-1.66 1.34-3 3-3Zm0 10c-2.76 0-5-2.24-5-5h2c0 1.66 1.34 3 3 3s3-1.34 3-3h2c0 2.76-2.24 5-5 5Z" id="b"/></defs><g fill="none" fill-rule="evenodd"><circle fill="url(#a)" cx="28" cy="28" r="28"/><use fill="#FFF" xlink:href="#b"/></g></svg>
|
||||||
|
After Width: | Height: | Size: 663 B |
|
|
@ -0,0 +1 @@
|
||||||
|
<svg width="56" height="56" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><defs><linearGradient x1="50%" y1="0%" x2="50%" y2="100%" id="a"><stop stop-color="#FF6F48" offset="0%"/><stop stop-color="#F02AA6" offset="100%"/></linearGradient><path d="M26 28c-1.1 0-2 .9-2 2s.9 2 2 2 2-.9 2-2-.9-2-2-2Zm-4-4c-1.1 0-2 .9-2 2s.9 2 2 2 2-.9 2-2-.9-2-2-2Zm0 8c-1.1 0-2 .9-2 2s.9 2 2 2 2-.9 2-2-.9-2-2-2Zm12-8c1.1 0 2-.9 2-2s-.9-2-2-2-2 .9-2 2 .9 2 2 2Zm-4 8c-1.1 0-2 .9-2 2s.9 2 2 2 2-.9 2-2-.9-2-2-2Zm4-4c-1.1 0-2 .9-2 2s.9 2 2 2 2-.9 2-2-.9-2-2-2Zm-4-4c-1.1 0-2 .9-2 2s.9 2 2 2 2-.9 2-2-.9-2-2-2Zm-4-4c-1.1 0-2 .9-2 2s.9 2 2 2 2-.9 2-2-.9-2-2-2Z" id="b"/></defs><g fill="none" fill-rule="evenodd"><circle fill="url(#a)" cx="28" cy="28" r="28"/><use fill="#FFF" xlink:href="#b"/></g></svg>
|
||||||
|
After Width: | Height: | Size: 813 B |
|
|
@ -0,0 +1 @@
|
||||||
|
<svg width="56" height="56" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><defs><linearGradient x1="50%" y1="0%" x2="50%" y2="100%" id="a"><stop stop-color="#FF6F48" offset="0%"/><stop stop-color="#F02AA6" offset="100%"/></linearGradient><path d="M16 0H2C.9 0 0 .9 0 2v14c0 1.1.9 2 2 2h14c1.1 0 2-.9 2-2V2c0-1.1-.9-2-2-2Zm0 16L9 8v8H2l7-8V2h7v14Z" id="b"/></defs><g fill="none" fill-rule="evenodd"><circle fill="url(#a)" cx="28" cy="28" r="28"/><use fill="#FFF" xlink:href="#b" transform="translate(19 19)"/></g></svg>
|
||||||
|
After Width: | Height: | Size: 550 B |
|
|
@ -0,0 +1 @@
|
||||||
|
<svg width="56" height="56" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><defs><linearGradient x1="50%" y1="0%" x2="50%" y2="100%" id="a"><stop stop-color="#FF6F48" offset="0%"/><stop stop-color="#F02AA6" offset="100%"/></linearGradient><path d="m31 18 1.83 2H36c1.1 0 2 .9 2 2v12c0 1.1-.9 2-2 2H20c-1.1 0-2-.9-2-2V22c0-1.1.9-2 2-2h3.17L25 18h6Zm-3 5c-2.76 0-5 2.24-5 5s2.24 5 5 5 5-2.24 5-5-2.24-5-5-5Zm0 1.8a3.2 3.2 0 1 1 0 6.4 3.2 3.2 0 0 1 0-6.4Z" id="b"/></defs><g fill="none" fill-rule="evenodd"><circle fill="url(#a)" cx="28" cy="28" r="28"/><use fill="#FFF" xlink:href="#b"/></g></svg>
|
||||||
|
After Width: | Height: | Size: 626 B |
Binary file not shown.
|
After Width: | Height: | Size: 73 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 279 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 54 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 72 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 42 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 135 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
|
|
@ -0,0 +1 @@
|
||||||
|
<svg width="112" height="29" xmlns="http://www.w3.org/2000/svg"><g fill="#13183F"><path d="M9.684 28.432c-2.16 0-4.038-.51-5.634-1.53S1.368 24.508.792 22.78l3.96-1.872c.504 1.056 1.188 1.884 2.052 2.484.864.6 1.824.9 2.88.9.768 0 1.356-.156 1.764-.468.408-.312.612-.744.612-1.296 0-.288-.072-.534-.216-.738-.144-.204-.36-.39-.648-.558a4.593 4.593 0 0 0-1.08-.432l-3.348-.936C5.16 19.408 3.924 18.67 3.06 17.65c-.864-1.02-1.296-2.226-1.296-3.618 0-1.224.312-2.292.936-3.204.624-.912 1.5-1.626 2.628-2.142 1.128-.516 2.424-.774 3.888-.774 1.92 0 3.606.45 5.058 1.35 1.452.9 2.478 2.166 3.078 3.798l-3.996 1.872c-.288-.816-.81-1.47-1.566-1.962s-1.614-.738-2.574-.738c-.696 0-1.242.144-1.638.432-.396.288-.594.684-.594 1.188 0 .264.072.504.216.72.144.216.378.408.702.576.324.168.726.324 1.206.468l3.132.936c1.632.48 2.88 1.206 3.744 2.178.864.972 1.296 2.166 1.296 3.582 0 1.224-.318 2.292-.954 3.204-.636.912-1.518 1.626-2.646 2.142s-2.46.774-3.996.774ZM20.52 28V.748h5.4v17.46l-2.016-.648 8.676-9.216h6.66l-7.128 7.92L39.204 28h-6.12l-5.94-9.972 3.132-.792-6.012 6.552 1.656-3.132V28zM41.616 28V8.344h5.4V28h-5.4Zm0-21.42v-5.4h5.4v5.4h-5.4ZM50.976 28V.748h5.4V28zM60.336 28V.748h5.4V28zM79.164 28.432c-2.088 0-3.9-.462-5.436-1.386a9.578 9.578 0 0 1-3.564-3.726c-.84-1.56-1.26-3.288-1.26-5.184 0-1.968.438-3.72 1.314-5.256a9.821 9.821 0 0 1 3.546-3.636c1.488-.888 3.168-1.332 5.04-1.332 1.56 0 2.94.246 4.14.738 1.2.492 2.214 1.182 3.042 2.07a9.115 9.115 0 0 1 1.89 3.078c.432 1.164.648 2.43.648 3.798 0 .384-.018.762-.054 1.134-.036.372-.102.69-.198.954H73.548v-3.96h11.664l-2.556 1.872c.24-1.032.228-1.95-.036-2.754s-.726-1.44-1.386-1.908c-.66-.468-1.47-.702-2.43-.702-.936 0-1.74.228-2.412.684-.672.456-1.176 1.128-1.512 2.016-.336.888-.468 1.968-.396 3.24-.096 1.104.036 2.076.396 2.916.36.84.912 1.494 1.656 1.962.744.468 1.644.702 2.7.702.96 0 1.782-.192 2.466-.576a4.147 4.147 0 0 0 1.602-1.584l4.32 2.052c-.384.96-.99 1.8-1.818 2.52-.828.72-1.806 1.278-2.934 1.674-1.128.396-2.364.594-3.708.594Zm21.78 0c-1.92 0-3.636-.456-5.148-1.368a9.932 9.932 0 0 1-3.582-3.708c-.876-1.56-1.314-3.288-1.314-5.184 0-1.92.444-3.654 1.332-5.202a10.112 10.112 0 0 1 3.6-3.69c1.512-.912 3.204-1.368 5.076-1.368 1.44 0 2.718.27 3.834.81s1.998 1.302 2.646 2.286l-.828 1.08V.748h5.4V28h-5.04v-3.6l.504 1.116c-.672.96-1.584 1.686-2.736 2.178-1.152.492-2.4.738-3.744.738Zm.648-4.86c.984 0 1.848-.228 2.592-.684a4.715 4.715 0 0 0 1.746-1.908c.42-.816.63-1.752.63-2.808 0-1.056-.21-1.992-.63-2.808a4.715 4.715 0 0 0-1.746-1.908c-.744-.456-1.608-.684-2.592-.684s-1.866.234-2.646.702a4.877 4.877 0 0 0-1.818 1.908c-.432.804-.648 1.734-.648 2.79s.216 1.992.648 2.808a4.721 4.721 0 0 0 1.818 1.908c.78.456 1.662.684 2.646.684Z"/></g></svg>
|
||||||
|
After Width: | Height: | Size: 2.7 KiB |
|
|
@ -0,0 +1 @@
|
||||||
|
<svg width="112" height="29" xmlns="http://www.w3.org/2000/svg"><g fill="#FFF"><path d="M9.684 28.432c-2.16 0-4.038-.51-5.634-1.53S1.368 24.508.792 22.78l3.96-1.872c.504 1.056 1.188 1.884 2.052 2.484.864.6 1.824.9 2.88.9.768 0 1.356-.156 1.764-.468.408-.312.612-.744.612-1.296 0-.288-.072-.534-.216-.738-.144-.204-.36-.39-.648-.558a4.593 4.593 0 0 0-1.08-.432l-3.348-.936C5.16 19.408 3.924 18.67 3.06 17.65c-.864-1.02-1.296-2.226-1.296-3.618 0-1.224.312-2.292.936-3.204.624-.912 1.5-1.626 2.628-2.142 1.128-.516 2.424-.774 3.888-.774 1.92 0 3.606.45 5.058 1.35 1.452.9 2.478 2.166 3.078 3.798l-3.996 1.872c-.288-.816-.81-1.47-1.566-1.962s-1.614-.738-2.574-.738c-.696 0-1.242.144-1.638.432-.396.288-.594.684-.594 1.188 0 .264.072.504.216.72.144.216.378.408.702.576.324.168.726.324 1.206.468l3.132.936c1.632.48 2.88 1.206 3.744 2.178.864.972 1.296 2.166 1.296 3.582 0 1.224-.318 2.292-.954 3.204-.636.912-1.518 1.626-2.646 2.142s-2.46.774-3.996.774ZM20.52 28V.748h5.4v17.46l-2.016-.648 8.676-9.216h6.66l-7.128 7.92L39.204 28h-6.12l-5.94-9.972 3.132-.792-6.012 6.552 1.656-3.132V28zM41.616 28V8.344h5.4V28h-5.4Zm0-21.42v-5.4h5.4v5.4h-5.4ZM50.976 28V.748h5.4V28zM60.336 28V.748h5.4V28zM79.164 28.432c-2.088 0-3.9-.462-5.436-1.386a9.578 9.578 0 0 1-3.564-3.726c-.84-1.56-1.26-3.288-1.26-5.184 0-1.968.438-3.72 1.314-5.256a9.821 9.821 0 0 1 3.546-3.636c1.488-.888 3.168-1.332 5.04-1.332 1.56 0 2.94.246 4.14.738 1.2.492 2.214 1.182 3.042 2.07a9.115 9.115 0 0 1 1.89 3.078c.432 1.164.648 2.43.648 3.798 0 .384-.018.762-.054 1.134-.036.372-.102.69-.198.954H73.548v-3.96h11.664l-2.556 1.872c.24-1.032.228-1.95-.036-2.754s-.726-1.44-1.386-1.908c-.66-.468-1.47-.702-2.43-.702-.936 0-1.74.228-2.412.684-.672.456-1.176 1.128-1.512 2.016-.336.888-.468 1.968-.396 3.24-.096 1.104.036 2.076.396 2.916.36.84.912 1.494 1.656 1.962.744.468 1.644.702 2.7.702.96 0 1.782-.192 2.466-.576a4.147 4.147 0 0 0 1.602-1.584l4.32 2.052c-.384.96-.99 1.8-1.818 2.52-.828.72-1.806 1.278-2.934 1.674-1.128.396-2.364.594-3.708.594Zm21.78 0c-1.92 0-3.636-.456-5.148-1.368a9.932 9.932 0 0 1-3.582-3.708c-.876-1.56-1.314-3.288-1.314-5.184 0-1.92.444-3.654 1.332-5.202a10.112 10.112 0 0 1 3.6-3.69c1.512-.912 3.204-1.368 5.076-1.368 1.44 0 2.718.27 3.834.81s1.998 1.302 2.646 2.286l-.828 1.08V.748h5.4V28h-5.04v-3.6l.504 1.116c-.672.96-1.584 1.686-2.736 2.178-1.152.492-2.4.738-3.744.738Zm.648-4.86c.984 0 1.848-.228 2.592-.684a4.715 4.715 0 0 0 1.746-1.908c.42-.816.63-1.752.63-2.808 0-1.056-.21-1.992-.63-2.808a4.715 4.715 0 0 0-1.746-1.908c-.744-.456-1.608-.684-2.592-.684s-1.866.234-2.646.702a4.877 4.877 0 0 0-1.818 1.908c-.432.804-.648 1.734-.648 2.79s.216 1.992.648 2.808a4.721 4.721 0 0 0 1.818 1.908c.78.456 1.662.684 2.646.684Z"/></g></svg>
|
||||||
|
After Width: | Height: | Size: 2.6 KiB |
|
|
@ -0,0 +1,52 @@
|
||||||
|
<!DOCTYPE html>
|
||||||
|
<html lang="en">
|
||||||
|
<head>
|
||||||
|
<meta charset="UTF-8">
|
||||||
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||||
|
|
||||||
|
<link rel="icon" type="image/png" sizes="32x32" href="./assets/favicon-32x32.png">
|
||||||
|
|
||||||
|
<title>Frontend Mentor | Skilled e-learning landing page</title>
|
||||||
|
</head>
|
||||||
|
<body>
|
||||||
|
|
||||||
|
Get Started
|
||||||
|
|
||||||
|
Maximize skill, minimize budget
|
||||||
|
|
||||||
|
Our modern courses across a range of in-demand skills will give you the
|
||||||
|
knowledge you need to live the life you want.
|
||||||
|
|
||||||
|
Get Started
|
||||||
|
|
||||||
|
Check out our most popular courses!
|
||||||
|
|
||||||
|
Animation
|
||||||
|
Learn the latest animation techniques to create stunning motion
|
||||||
|
design and captivate your audience.
|
||||||
|
Get Started
|
||||||
|
|
||||||
|
Design
|
||||||
|
Create beautiful, usable interfaces to help shape the future of
|
||||||
|
how the web looks.
|
||||||
|
Get Started
|
||||||
|
|
||||||
|
Photography
|
||||||
|
Explore critical fundamentals like lighting, composition, and focus
|
||||||
|
to capture exceptional photos.
|
||||||
|
Get Started
|
||||||
|
|
||||||
|
Crypto
|
||||||
|
All you need to know to get started investing in crypto. Go from beginner
|
||||||
|
to advanced with this 54 hour course.
|
||||||
|
Get Started
|
||||||
|
|
||||||
|
Business
|
||||||
|
A step-by-step playbook to help you start, scale, and sustain your business
|
||||||
|
without outside investment.
|
||||||
|
Get Started
|
||||||
|
|
||||||
|
Get Started
|
||||||
|
|
||||||
|
</body>
|
||||||
|
</html>
|
||||||
Loading…
Reference in New Issue