Closed Gizmotronn closed 2 weeks ago
Layout:
return (
<div className="mx-12">
{/* Desktop Layout */}
<div className="hidden md:grid md:grid-cols-5 md:grid-rows-3 md:gap-4 md:relative md:h-full">
<div className="md:row-span-1 md:col-span-5 md:flex md:items-center md:justify-center p-12">
{renderContent()}
</div>
<div className="md:row-span-1 md:col-span-5 md:flex md:items-center md:justify-center"></div>
<div className="md:row-span-1 md:col-span-5 md:flex md:items-center md:justify-center p-12 mb-12">
{renderAutomatonContent()}
</div>
</div>
{/* Mobile Layout */}
<div className="grid grid-cols-1 grid-rows-auto gap-4 md:hidden relative min-h-screen">
<div>01</div>
<div>02</div>
<div>04</div>
<div className="col-span-1 flex justify-center items-end pb-5">
{renderContent()}
</div>
<div>05</div>
<div>08</div>
<div className="col-span-1 flex justify-center items-end pb-5">
{renderAutomatonContent()}
</div>
<div>09</div>
<div>10</div>
<div>11</div>
</div>
</div>
);
This seems to be a good plan.
See in
pages/planets/[id].tsx
:While in the main
<Layout>
component incomponents/Section/Layout.tsx
:This could cause problems, I just noticed this when I was creating the route for individual sectors. We need to define a coherent syntax for mobile configuration before this new repo gets messy.
<awaiting jira/plane linked issue tag>