Skip to content

ilhye/AWSCC-CodeQuest-Frontend

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

31 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

πŸš€ 30 Days of Frontend πŸš€

Welcome to 30 Days of Frontend! πŸš€ Join us on this thrilling month-long adventure into the world of web development. Whether you're a seasoned designer 🎨 with years of experience or an inquisitive newcomer πŸ€“ eager to dive in, get ready to unravel the wonders of frontend development πŸ”. We'll delve into the essential concepts of HTML, CSS, JavaScript, and more.

But this isn't just about theory and technical terms – we'll apply our newfound knowledge by crafting engaging and practical projects πŸ› οΈ that showcase the magic of frontend development. It's a hands-on learning journey designed to not only enhance your skills but also spark your creativity. So, are you prepared to embark on this captivating coding adventure with us?


πŸ‘€ What's Inside It

This repository contains the following main folders:

  1. frontend-lessons folder: consisting of all the files in every day of CodeQuest. (See πŸ“… β”Š Table of Contents below)

  2. projects folder: consisting of all the necessary projects the participants need to submit to complete CodeQuest. Projects


πŸ“… β”Š Table of Contents


πŸ’« Getting Started

Use this template to create your own repository with existing directory structure and files to participate in our CodeQuest: 30 Days of Frontend.

  1. On GitHub.com, navigate to the main page of this repository and click the Use this template button.

    Use this template

  2. Name it with the same name as this repository (AWSCC-CodeQuest-Frontend), and make it public.

    NOTE: The repository name should be in the format of AWSCC-CodeQuest-Frontend (Do not copy exactly the same name as in the image below)

    Alt text

  3. On the lower right, click Create repository.

    Alt text

    and it should generate the repository in your account.

    NOTE: The repository name should be in the format of AWSCC-CodeQuest-Frontend (Do not copy exactly the same name as in the image below)

    Alt text

  4. After creating a repository, copy the repository URL and paste it in our CodeQuest Tracker Sheet in your corresponding row.

    Note: If you are having trouble with the CodeQuest Tracker Sheet, do not hesitate to directly message any DSWD officers or email us at awscloudclub.pupmnl.dswd@gmail.com

  5. Finally, clone the repository by clicking the Code button on the top right side of the repository's main page and clicking the Open with GitHub Desktop button to redirect to your GitHub Desktop application.

    Alt text

  6. And just click the Clone button to clone it to your computer.

    Alt text


βœ‰οΈ Submissions

CodeQuest is made to provide participants an immersive, hands-on coding experience by guiding them through the creation of small projects. Every day of CodeQuest contains a particular knowledge that is essential to build the foundations of your frontend development skills.

We encourage you to share your progress in πŸ“ˆβ”Šcodequest-progress to serve as motivation for others and to open up discussions and reviews to gain further insights about a particular topic.

example:

Day: 10-11 of Frontend

Topic: HTML and CSS project

Highlights: I learned how to use HTML and CSS to create a portfolio website.

Attachments: (optional)

To finish our CodeQuest: 30 Days of Frontend, you need to submit 4 projects for your completion to be acknowledged:

.
β”œβ”€β”€ projects
β”‚   β”œβ”€β”€ 01-blog-post     # HTML project (day 3 & 9)
β”‚   β”œβ”€β”€ 02-your-own-portfolio     # CSS project (day 10-11)
β”‚   β”œβ”€β”€ 03-rock-paper-scissors       # HTML and CSS project (day 24-25)
β”‚   β”œβ”€β”€ 04-number-game       # final project (day 26-30)
└── ...

Note: There are exercises/challenges included in some days that you are not required to submit but is encouraged to try to test how much knowledge you've gained after finishing each day!

Enjoy coding!~

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published