Feature/reactui sidenav

[AleksandarDev]

[DorijanH]

Did you choose native browser APIs over "Next.js's way" for any specific reason? I see that you're using Next's useSearchParams, so I think maybe you could integrate Next.js's routing all the way for consistency and reactivity

For example:

const router = useRouter();
const pathname = usePathname();
const params = useSearchParams();
const selectedItem = params.get('item');
const show = params.get('show') === 'true';

function setShow(show: boolean) {
    const params = new URLSearchParams(searchParams);
    params.set('show', show.toString());
    
    router.push(`${pathname}?${params.toString()}`);
    // router.push(`${pathname}?${params.toString()}`, { shallow: true }); If you don't want to run data fetching methods again
}

[DorijanH]

I think you could shorten this a bit by using callback function on a useMediaQuery hook that accepts the theme as the first argument, if you don't need that theme object anywhere else:

const isMobile = useMediaQuery((theme) => theme.breakpoints.down('md'));

[DorijanH]

Do you need this theme object?

[DorijanH]

Do you need this theme object?