3 column preview card project - should be finished

This commit is contained in:
Robert McGovern 2022-09-07 13:53:51 +01:00
parent 390d8a5d12
commit 75094cc939
7 changed files with 339 additions and 196 deletions

View File

@ -0,0 +1,92 @@
# Frontend Mentor - 3-column preview card component
![Design preview for the 3-column preview card component coding challenge](./design/desktop-preview.jpg)
## 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 3-column preview card 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 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 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!** 🚀

View File

@ -1,111 +0,0 @@
# Frontend Mentor - 3-column preview card component solution
This is a solution to the [3-column preview card component challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/3column-preview-card-component-pH92eAR2-). 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
![](./screenshot.jpg)
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.**

View File

@ -1,92 +1,76 @@
# Frontend Mentor - 3-column preview card component # Frontend Mentor - 3-column preview card component solution
![Design preview for the 3-column preview card component coding challenge](./design/desktop-preview.jpg) This is a solution to the [3-column preview card component challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/3column-preview-card-component-pH92eAR2-). Frontend Mentor challenges help you improve your coding skills by building realistic projects.
## Welcome! 👋 ## Table of contents
Thanks for checking out this front-end coding challenge. - [Frontend Mentor - 3-column preview card component solution](#frontend-mentor---3-column-preview-card-component-solution)
- [Table of contents](#table-of-contents)
- [Overview](#overview)
- [The challenge](#the-challenge)
- [Screenshot](#screenshot)
- [Links](#links)
- [My process](#my-process)
- [Built with](#built-with)
- [What I learned](#what-i-learned)
- [Continued development](#continued-development)
- [Author](#author)
- [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 3-column preview card 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 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 Here are the final images for the desktop version
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. ![Desktop](./screenshots/desktop.png)
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`. and for the mobile version
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). ![Mobile](./screenshots/mobile.png)
You will find all the required assets in the `/images` folder. The assets are already optimized. ### Links
There is also a `style-guide.md` file containing the information you'll need, such as color palette and fonts. - Solution URL: [Gitea on rmcg.dev](https://git.tarasis.net/tarasis/rmcg.dev/src/branch/main/projects/FrontendMentor/newbie/3-column-preview-card-component)
- Live Site URL: [rmcg.dev](https://rmcg.dev/FrontendMentor/newbie/3-column-preview-card-component)
## Building your project ## My process
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: ### Built with
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/). - Semantic HTML5 markup
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. - CSS custom properties
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. - Flexbox
4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content. - Mobile-first workflow
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 ### What I learned
As mentioned above, there are many ways to host your project for free. Our recommend hosts are: I was rusty as I hadn't touched html/css/javascript in 7 months. Solution came together fairly quickly.
- [GitHub Pages](https://pages.github.com/) As usual I focused on mobile first, and then added some minor tweaks for desktop. (Specifically the "Learn More" button is lower on the desktop version)
- [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). I spent a little time chasing box widths, mainly it was paragraph width. Honestly I should have simply stayed with the `25ch` used for the mobile version rather than having `23.15ch` for the desktop.
## Create a custom `README.md` ### Continued development
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. Continue working through the `newbie` projects that I have, with an eye to trying to use `grid` rather than `flexbox`.
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. ## Author
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. - Website - [Blog](https://tarasis.net)
- Website - [Portfolio](https://rmcg.dev)
- Frontend Mentor - [@tarasis](https://www.frontendmentor.io/profile/tarasis)
- Twitter - [@tarasis](https://www.twitter.com/tarasis)
## Submitting your solution ## Acknowledgments
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. Just Matt front [Frontend Mentor](https://www.frontendmentor.io) for creating the site. These challenges have been an effective way of learning.
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!** 🚀

View File

@ -0,0 +1,154 @@
/*
Info:
desktop size 1440x800
mobile size 375x1502
*/
/* ! Create variables */
:root {
/* Colors: Primary */
--col-pri-bright-orange: hsl(31, 77%, 52%);
--col-pri-dark-cyan: hsl(184, 100%, 22%);
--col-pri-very-dark-cyan: hsl(179, 100%, 13%);
/* Colors: Neutral */
/* paragraphs */
--col-neu-transparent-white: hsla(0, 0%, 100%, 0.75);
/* background, headings, buttons */
--col-neu-very-light-gray: hsl(0, 0%, 95%);
/* Fonts */
--fs-body-15px: 0.9375rem;
--fw-400: 400;
--fw-700: 700;
--ff-lexend: "Lexend Deca", sans-serif;
--ff-big-shoulders: "Big Shoulders Display", cursive;
}
*,
::before,
::after {
margin: 0;
padding: 0;
box-sizing: border-box;
}
/* Provided attribution styling */
footer {
position: absolute;
bottom: 0;
width: 100%;
/* justify-content: space-around; */
}
.attribution {
font-size: 11px;
text-align: center;
}
.attribution a {
color: hsl(228, 45%, 44%);
}
html {
}
body {
min-width: 100vw;
min-height: 100vh;
display: grid;
/* place-items: center; */
justify-content: center;
align-content: center;
background-color: var(--col-neu-very-light-gray);
}
.container {
display: flex;
flex-direction: column;
}
.card {
padding: 3rem;
font-family: var(--ff-lexend);
font-size: var(--fs-body-15px);
color: var(--col-neu-very-light-gray);
}
.card:first-child {
border-radius: 8px 8px 0 0;
}
.card:last-child {
border-radius: 0 0 8px 8px;
}
.card__image {
margin-bottom: 2.1875rem;
}
.card__title {
font-family: var(--ff-big-shoulders);
font-size: 2.5rem;
text-transform: uppercase;
margin-bottom: 1.5625rem;
}
.card__body {
margin-bottom: 1.5625rem;
width: 25ch;
color: var(--col-neu-transparent-white);
line-height: 1.5625rem;
}
.card-learn-more__button {
background-color: var(--col-neu-very-light-gray);
border-radius: 25px;
padding: 12px 32px;
display: inline-block;
text-decoration: none;
color: var(--col-fg);
}
.card-learn-more__button:focus,
.card-learn-more__button:hover {
background-color: var(--col-fg);
border: 2px solid var(--col-neu-very-light-gray);
padding: 10px 30px;
color: var(--col-neu-very-light-gray);
}
.sedan-color {
background-color: var(--col-pri-bright-orange);
--col-fg: var(--col-pri-bright-orange);
}
.suv-color {
background-color: var(--col-pri-dark-cyan);
--col-fg: var(--col-pri-dark-cyan);
}
.luxury-color {
background-color: var(--col-pri-very-dark-cyan);
--col-fg: var(--col-pri-very-dark-cyan);
}
@media screen and (min-width: 900px) {
.container {
flex-direction: row;
}
.card:first-child {
border-radius: 8px 0 0 8px;
}
.card:last-child {
border-radius: 0 8px 8px 0;
}
.card__body {
/* just changed to chase design, honestly the 25ch width is fine */
width: 23.15ch;
margin-bottom: 5.25rem;
}
}

View File

@ -1,36 +1,60 @@
<!DOCTYPE html> <!DOCTYPE html>
<html lang="en"> <html lang="en">
<head> <head>
<meta charset="UTF-8"> <meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0"> <!-- displays site properly based on user's device --> <meta name="viewport" content="width=device-width, initial-scale=1.0">
<!-- displays site properly based on user's device -->
<link rel="icon" type="image/png" sizes="32x32" href="./images/favicon-32x32.png"> <link rel="icon" type="image/png" sizes="32x32" href="./images/favicon-32x32.png">
<title>Frontend Mentor | 3-column preview card component</title> <link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Big+Shoulders+Display:wght@700&family=Lexend+Deca&display=swap"
rel="stylesheet">
<!-- Feel free to remove these styles or customise in your own stylesheet 👍 --> <link rel="stylesheet" href="./css/style.css">
<style> <title>Frontend Mentor | 3-column preview card component</title>
.attribution { font-size: 11px; text-align: center; }
.attribution a { color: hsl(228, 45%, 44%); }
</style>
</head> </head>
<body> <body>
Sedans <main class="container">
<article class="card sedan-color">
<img class="card__image" src="./images/icon-sedans.svg" alt="stylized image of a sedan car">
<h2 class="card__title">Sedans</h2>
<p class="card__body">
Choose a sedan for its affordability and excellent fuel economy. Ideal for cruising in the city Choose a sedan for its affordability and excellent fuel economy. Ideal for cruising in the city
or on your next road trip. or on your next road trip.
</p>
<a href="#" class="card-learn-more__button">Learn More</a>
</article>
SUVs <article class="card suv-color">
<img class="card__image" src="./images/icon-suvs.svg" alt="stylized image of an SUV">
<h2 class="card__title">SUVs</h2>
<p class="card__body">
Take an SUV for its spacious interior, power, and versatility. Perfect for your next family vacation Take an SUV for its spacious interior, power, and versatility. Perfect for your next family vacation
and off-road adventures. and off-road adventures.
</p>
<a href="#" class="card-learn-more__button">Learn More</a>
</article>
Luxury <article class="card luxury-color">
<img class="card__image" src="./images/icon-luxury.svg" alt="stylized image of a luxury car">
<h2 class="card__title">Luxury</h2>
<p class="card__body">
Cruise in the best car brands without the bloated prices. Enjoy the enhanced comfort of a luxury Cruise in the best car brands without the bloated prices. Enjoy the enhanced comfort of a luxury
rental and arrive in style. rental and arrive in style.
</p>
<a href="#" class="card-learn-more__button">Learn More</a>
</article>
</main>
<div class="attribution"> <footer class="attribution">
Challenge by <a href="https://www.frontendmentor.io?ref=challenge" target="_blank">Frontend Mentor</a>. Challenge by <a href="https://www.frontendmentor.io?ref=challenge" target="_blank">Frontend Mentor</a>.
Coded by <a href="#">Your Name Here</a>. Coded by <a href="https://tarasis.net">Robert McGovern</a>.
</div> </footer>
</body> </body>
</html> </html>

Binary file not shown.

After

Width:  |  Height:  |  Size: 270 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 206 KiB