Frontend Engineer Quest

🙌  Thank you for participating in this quest! Are you ready for an adventure? Let's get started!

Why do we have quests? We use them to:

1. To understand your skill level and how you approach tasks. We want to make sure that you have the core skills to set you up for success as a future uizard 🧙, while still giving you plenty of room to take on challenges.

2. For you to decide if it’s the right role for you. It’s important to us that you’ll love what you’ll do and be able to explore new ideas and opportunities.

✅ Instructions for Your Quest:

• Complete the quest and submit your solution. You’re welcome to submit it as soon as you are done, we evaluate submissions continuously.

• Email us the solution by sending a single zip-file with the source code (without node_modules folder). If you have issues sending it as an attachment, please use a service like wetransfer to upload the zip and send the download link.

• After you hand in the challenge, we will review your submission and get back to you with next steps by email.

⛰ The Quest: Build a Basic Editor

For the quest, you will build a very basic design editor using React. Users must be able to add, drag, and remove elements in the editor.

There are many different ways to scope and implement a solution. We recommend keeping it simple.

• Use React to render the elements in the DOM (do not use canvas).

• The editor should not persist state (no API, no local storage).

• Performance is not important – the editor only needs to be capable of handling a handful of elements.

If you’re comfortable with TypeScript, we encourage you to use it, but it is not a requirement.

Requirements

• You must use the create-react-app utility to set up the project.

• You must build the drag-functionality yourself. Do not use libraries such as react-draggable.

Reference Solution

As inspiration, we have attached a short video of a reference solution.

Getting Started

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.