Skip to content

Commit d98bbf0

Browse files
Update README.md
1 parent 00666be commit d98bbf0

File tree

1 file changed

+13
-12
lines changed

1 file changed

+13
-12
lines changed

README.md

+13-12
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@
33
> Check out our 2022 coding challenge [here](https://github.com./Aerolab/frontend-developer-coding-challenge/tree/2022)
44
55
* [Overview](#Overview)
6+
* [Design resources](#Design-resources)
67
* [Tech Stack](#Tech-Stack)
78
* [IGDB API](#IGDB-API)
89
* [Requirements](#Requirements)
9-
* [Design resources](#Design-resources)
1010
* [Delivery](#Delivery)
1111
* [About Aerolab and career opportunities](#Aerolab)
1212

@@ -16,21 +16,26 @@ Your task is to create a web application that allows users to search for and dig
1616

1717
> You’re welcome to use any additional libraries you find helpful for the challenge.
1818
19-
![wireframes](docs/aerolab-coding-challenge-wireframes.png)
19+
![image](https://github.com./user-attachments/assets/92b96f68-561e-4326-8e8d-72dec6251b9d)
20+
21+
## Design resources
22+
> [!IMPORTANT]
23+
> Access the [Figma design here](https://www.figma.com/design/3O7BxHFnSSawJeny3lXWkE/Aerolab-Frontend-Developer-Coding-Challenge---Public?node-id=16996-5165&t=uLiMR18T28Jegm4s-4) to complete the challenge.
24+
> Prioritizing responsive/mobile design is essential; the desktop design is optional but we expect at least a clean and polished appearance.
2025
2126
## Tech Stack
2227

2328
We recommend using the following technologies to align with the tools we use at Aerolab and to ensure an efficient and scalable solution for this challenge. These tools will help you meet performance, usability, and maintainability standards:
2429

2530

2631
### Recommended Tools
27-
- TypeScript for type safety and data modeling.
28-
- Next.js (App Router) for server-side rendering and routing.
32+
- `TypeScript` for type safety and data modeling.
33+
- `Next.js` (App Router) for server-side rendering and routing.
2934
- Tailwind CSS or CSS Modules for styling.
30-
- Radix, shadcn, NextUI, MUI for UI components.
31-
- Vercel for deployment.
32-
- Postman or HTTPie for API request testing.
33-
- (Optional) React Testing Library for testing.
35+
- `Radix`, `shadcn`, `NextUI`, `MagicUI`, `MUI` for UI components.
36+
- `Vercel` for deployment.
37+
- `Postman` or `HTTPie` for API request testing.
38+
- (Optional) `React Testing Library` for testing.
3439

3540
> Yes, you can use AI to enhance any part of the project, or even integrate it into your solution.
3641
@@ -94,10 +99,6 @@ The design should look polished, with consistent styling throughout. Remember, c
9499
- (Optional) Implement a login system with Supabase or similar.
95100
- (Optional) Add unit or integration tests.
96101

97-
## Design resources
98-
> [!IMPORTANT]
99-
> The design is still in progress, and we’ll share the final Figma file once it’s ready. In the meantime, you can work from [wireframes](https://www.figma.com/design/3O7BxHFnSSawJeny3lXWkE/Aerolab-Frontend-Developer-Coding-Challenge---Public?node-id=16692-3191&t=4j9KGkZuF4bA2zbD-4) to complete the challenge. You’re welcome to use any component library, such as shadcn, or even create your own custom designs.
100-
101102
## Delivery
102103

103104
This needs to ship. You should upload the project to a public link (we recommend [Vercel](https://vercel.com/)). You should also upload it to Github so we can review the code.

0 commit comments

Comments
 (0)