Skip to content

jakehalliday/my-team-site

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Frontend Mentor - myteam website

Design preview for the myteam website coding challenge

Welcome! 👋

Thanks for purchasing this premium Frontend Mentor coding challenge.

Frontend Mentor challenges allow you to improve your skills in a real-life workflow. These premium challenges are perfect portfolio pieces, so please do feel free to use what you build in your portfolio to show others.

To do this challenge, you need a solid understanding of HTML and CSS and a basic understanding of JavaScript.

The challenge

Your challenge is to build out this multi-page website 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 each page depending on their device's screen size
  • See hover states for all interactive elements throughout the site
  • See the correct content for each team member on the About page when the + icon is clicked
  • Receive an error message when the contact form is submitted if:
    • The Name, Email Address or Message fields are empty should show "This field is required"
    • The Email Address is not formatted correctly should show "Please use a valid email address"

Want some support on the challenge? Join our Slack community and ask questions in the #help channel.

Where to find everything

Your task is to build out the project to the designs inside the /designs folder. You'll see that the original Sketch design file has been included in the project.

If you don't have Sketch you can use Sketch Cloud Inspector to view the design in the browser. To learn more and get set up with it please take a look at the README in the /designs folder.

You will also find mobile, tablet, desktop, and active state designs in JPG format if you wish to use them.

All the required assets for this project are in the /images folder. The assets are already optimized and ready to be used.

The design system 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. This will make it easier to share your code with the community if you need some help. If you're not sure how to do this, have a read through of this Try Git resource. IMPORTANT: There are already a couple of .gitignore files in this project. Please do not remove them or change the content of the files. This is to avoid the accidental upload of the designs to GitHub. With these premium challenges, please be sure not to share the JPG designs or the Sketch design in your GitHub repo. Thanks!
  2. Configure your repository to publish your code to a URL. This will also be useful if you need some help during a challenge as you can share the URL for your project with your repo URL. There are a number of ways to do this, but we recommend using Vercel. We've got more information about deploying your project with Vercel below.
  3. Look through the designs to start planning out how you'll tackle the project. This step is crucial to help you think ahead for CSS classes that you could create to make reusable styles.
  4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
  5. Write out the base styles for your project, including general content styles, such as font-family and font-size.
  6. Start adding styles to the top of the page and work down. Only move on to the next section once you're happy you've completed the area you're working on.

Deploying your project

As mentioned above, there are a number of ways to host your project for free. We recommend using Vercel as it's an amazing service and extremely simple to get set up with. If you'd like to use Vercel, here are some steps to follow to get started:

  1. Sign up to Vercel and go through the onboarding flow, ensuring your GitHub account is connected by using their Vercel for GitHub integration.
  2. Connect your project to Vercel from the "Import project" page, using the "From Git Repository" button and selecting the project you want to deploy.
  3. Once connected, every time you git push, Vercel will create a new deployment and the deployment URL will be shown on your Dashboard. You will also receive an email for each deployment with the URL.

Sharing your solution

There are multiple places you can share your solution:

  1. Submit it on the platform so that other users will see your solution on the site. You'll find all of your "In Progress" challenges on your profile page. Once submitted, other users will be able to give you feedback, which could help improve your code for the next project. If you'd like feedback, please don't forget to ask some questions when submitting and mention what you'd like feedback on. The more specific you can be the better.
  2. Share your repository and live URL in the #finished-projects channel of the Slack community. With these premium challenges please be sure not to upload the JPG designs or the Sketch design to GitHub when you're sharing it around.
  3. Tweet @frontendmentor and mention @frontendmentor including the repo and live URLs in the tweet. We'd love to take a look at what you've built and help share it around.

Giving feedback

Feedback is always welcome, so if you have any to give on this challenge please email hi[at]frontendmentor[dot]io.

Have fun building! 🚀

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published