DEV Community

Frontend Challenge v24.03.20 Frontend Challenge v24.03.20

Challenge ends soon!

Submit your entry now

DAYS
:
HOURS
:
MINUTES
:
SECONDS

Frontend Challenge v24.03.20

View Entries

Flex your CSS, JS, and writing skills with our first ever DEV Frontend Challenge!

Challenge Status: Ended Ended
Join our next Challenge

We are excited to launch our first official DEV Challenge: The Frontend Challenge!

Running through March 31, this challenge will be an opportunity to show off your creativity, build your profile, earn badges, and in general, have a lot of fun.

We have three prompts for this first challenge – you can participate in just one or all three. Multiple submissions under the same prompt are also welcome, but be sure to follow our submission guidelines.

For this challenge, each prompt will have one winner. Winners will receive an exclusive DEV badge of honor, and a gift from the DEV Shop. Participants with a valid submission will receive a completion badge.

Read on to learn how to participate, and don’t forget to read our FAQ. Good luck!

Key Dates

  • Contest start: March 20, 2024
  • Submissions due: March 31, 2024
  • Winners announced: April 02, 2024

Badge Rewards

DEV Frontend Challenge Participant
DEV Frontend Challenge Participant
DEV Frontend Challenge Winner
DEV Frontend Challenge Winner

Winners

Congratulations to our Frontend Challenge v24.03.20 winners! Read the full announcement post here.

CSS Art Challenge

Glam Up My Markup

One Byte Explainer

Challenge Prompts

CSS Art Challenge

Wow us by taking your favorite snack and turning it into CSS art. Your submission should not use any JavaScript, should flex your creativity in CSS, and should look delicious. Your submission will include markup, may include SVG, etc. but should mostly show off your skills in CSS.

Judging Criteria:

  • Creativity
  • Effective use of CSS
  • Aesthetic outcome

Glam Up My Markup

Use CSS and JavaScript to make the below HTML markup beautiful, interactive, and useful. Your submission should be more fun and interactive than the HTML we provide, but also be usable and accessible. You should not directly edit the HTML provided, unless it is via JavaScript. We expect style and substance. You may add basic boilerplate, including meta tags etc. for presentation purposes.

<section id="camp-activities-inquiry">
    <h1>Camp Activities Inquiry</h1>
    <form action="/submit-form" method="POST">
        <label for="activity-select">Which camp activities are you most looking forward to?</label>
        <select id="activity-select" name="activity">
            <option value="">--Please choose an option--</option>
            <option value="hiking">Hiking</option>
            <option value="canoeing">Canoeing</option>
            <option value="fishing">Fishing</option>
            <option value="crafts">Crafts</option>
            <option value="archery">Archery</option>
        </select>

        <label for="food-allergies">Food Allergies (if any)</label>
        <textarea id="food-allergies" name="food_allergies" rows="4" cols="50"></textarea>

        <label for="additional-info">Additional things the counselor should know</label>
        <textarea id="additional-info" name="additional_info" rows="4" cols="50"></textarea>

        <button type="submit">Submit</button>
    </form>
</section>

Judging Criteria:

  • Accessibility
  • Usability and user experience
  • Creativity
  • Code quality

One Byte Explainer

Explain a browser API or feature in 256 characters or less.

Pick any browser API (e.g. "fetch", "DOM", "Geolocation") and explain consisely what it does, perhaps how it works, and why someone might tap into using it. You have 256 characters — less than a tweet — to get your point across so the challenge is keeping it simple.

You can’t cover all the details in 256 characters, but can you pick out the most important ones? We are flexible about the definition of API or feature here as long as it is within the spirit of the request.

Judging Criteria:

  • Accuracy of explainer
  • Effectiveness of communication
  • Creativity

Frontend Challenge v24.03.20 FAQ

Participation

Can I submit to multiple prompts?

Yes, you are welcome to submit to multiple prompts.

Can I submit to a prompt more than once?

Yes, you can submit multiple submissions per prompt but you’ll need to publish a separate post for each submission.

  • In the event that you may win two or more prompts, and your submission is very close with another participant, we will favor the other participant.
  • In the event that you do win two or more prompts, you will only receive one winner badge.

Can I work on a team?

Yes, you can work on teams up to four people.

  • If you collaborate with anyone, you’ll need to list their DEV handles in your submission post so we can award a badge to your entire team! Please only publish one submission per team.
  • DEV does not handle prize-splitting, so in the event that your submission wins the shop gift, you will need to split that amongst yourselves. Thank you for understanding!

How old do I have to be to participate?

Participants need to be 18+ in order to participate.

If I live in X, am I eligible to participate?

For eligibility rules, see our official challenge rules.

Submission

Can my submission include open source code?

Riffing on open source code and borrowing and improving on previous work/ideas is encouraged but it’s important your changes are significant enough to ensure your submission is valid.

When does riffing become plagiarism?

It will depend, but transparency is important, license compatibility is important. You can use someone else’s code to give you a jumpstart to demonstrate your ideas on top of someone else’s base, but not just re-package the base.

It should be clear to the judges what you added to the project in terms of the code and conceptual inspiration. This means, you should clearly state what you were building on and what elements are original to this new submission.

When building on existing code, we expect a significant change that adds something tangible to the output. i.e. a new animation, and new sprite, a new function, a new presentation. Not just changes to the source - i.e. changing colours, changing one sprite, changing one function.

What happens if my submission is considered plagiarized or invalid?

Anything deemed to be plagiarism will not be eligible for prizes. Incidental plagiarism may simply result in your disqualification from the challenge (regardless of the number of other valid submissions you have published). Egregious plagiarism will result in your suspension from DEV entirely. Any non-generic, non-trivial usage of prior work, including open source code must be credited in your submission.

Do submissions have to be in English?

Non-english submissions are eligible for a completion badge but not eligible for prizes due to the current limitations of our judges. We will not be judging on mastery of the English language, so please don’t let this deter you from submitting if you are not a native English speaker! We hope to evolve this in the future to be more accommodating.

Do I need a license for my code?

We strongly recommend including a license for your code, here are some you may consider: MITApacheBSD-2BSD-3, or Commons Clause.

Can I use AI?

Use of AI is allowed as long as all other rules are followed. We want to give you a chance to show off your skills in realistic scenarios. If you use AI tools to help you achieve your submission, all the power to you.

How do I embed my project directly into my DEV post?

Our editor supports many types of embeds, including: Stackbliz, Glitch, Github, etc. You can typically use the {% embed https://... %} syntax directly in the post. Click here for more information on our markdown support.

  • For CodePen, you will need to use this syntax: {% codepen http://... %}
  • For CodeSandbox, you will need to use this syntax: {% codesandbox http://... %}

Judging and Prizing

Can there be ties?

In the event of a tie in scoring between judges, the judges will select the entry that received the highest number of positive reactions on their DEV post to determine the winner.

How will I know if I won?

Winners will be announced in a DEV post on the winner announcement date noted in our key dates section.

When will winners receive their Forem Shop gift?

The DEV Team will contact you via the email associated with your DEV profile within, at most, 10 business days of the announcement date to share the details of the shop gift.

When will I receive my DEV badge?

Both participation and winner badges will be awarded, in most cases, the same day as the winner announcement.

Frontend Challenge v24.03.20 Rules

NO PURCHASE NECESSARY. Open only to 18+. Contest entry period ends March 31st, 11:59 PM PT. Contest is void where prohibited or restricted by law or regulation. All entires must be submitted during the content period. For Official Rules, see Frontend Challenge v24.03.20 Contest Rules and General Contest Official Rules.