Closed hzz4343 closed 1 week ago
I want this
@NadiiaTysh you're in!
Add me please here too @khnatiuk
@Eugenia821 you're in!
I have a challenge with my laptop π₯΄ I've done something based on @NadiiaTysh code:
Login check: I've added a check using the useEffect hook to redirect any user that isn't logged in as "CBH".
Responsive layout: Tailwind's flex, md:flex-row, and gap-2 utilities create a flexible and responsive design that adjusts between portrait and landscape orientations.
Basic navigation: I used tags for fake interactions and navigation, as required by the task.
Styling: Basic Tailwind styling has been applied to give a skeleton look while maintaining readability and ease of interaction
Code to test on Saturday morning:
import React, { useEffect } from 'react'; import { useRouter } from 'next/router';
export default function OrgDashboard() { const router = useRouter(); const currentUser = 'CBH'; // Replace with dynamic user logic as needed
// Redirect non-CBH users to home useEffect(() => { if (currentUser !== 'CBH') { router.push('/'); // Redirect to home if user is not CBH } }, [currentUser, router]);
return (
); }
@khnatiuk we need help with PR please π
@NadiiaTysh I'm sending a code wizard your way. :)
@Builder-s-League/code-wizard can you verify and close this?
This
π° Appetite π°
π€ Problem Statement
Make a breadboard for each screen in the fat-marker sketch. Every place and affordance should be accounted for, but don't focus on making it look pretty. This should be essentially a bare HTML file, with no JS, and only CSS if required for basic layouts. Implement fake navigation and interactions using normal
<a>
tags. This purely for getting an interactive "skeleton" up, and seeing in real life whether this design would work, or has any major problems. Please see this page for more info on what your breadboard should be like (and, if you want understand the fat-marker sketch and places affordances drawing better, please see this page).π§ͺ Required Tests
None (but the Code Wizard will review whether or not your code warrants some tests! Review the Code & Testing Guidelines for more info)
β οΈ Careful about:
π€ Technologies focused on in this feature