From a63e37780a4db33269d87c0665d46708cc0267f4 Mon Sep 17 00:00:00 2001 From: Nitansh Shankar <167768158+BIJJUDAMA@users.noreply.github.com> Date: Fri, 6 Feb 2026 19:30:09 +0530 Subject: [PATCH 1/8] refactor: card layout and height for mobiles --- src/components/landing/CrewRewards.tsx | 31 ++++++++++++++++---------- src/components/landing/SectionCard.tsx | 4 ++-- 2 files changed, 21 insertions(+), 14 deletions(-) diff --git a/src/components/landing/CrewRewards.tsx b/src/components/landing/CrewRewards.tsx index 837af33..f5d56f3 100644 --- a/src/components/landing/CrewRewards.tsx +++ b/src/components/landing/CrewRewards.tsx @@ -5,22 +5,29 @@ import SectionCard from './SectionCard'; import DecodedText from '../shared/DecodedText'; const CrewRewardsContainer = styled.section` - min-height: 100vh; - display: flex; - align-items: center; - justify-content: center; + /* Desktop: min-height 100vh for breathing room */ + @media (min-width: 768px) { + min-height: 100vh; + display: flex; + align-items: center; + justify-content: center; + } + + /* Mobile: Auto height, normal flow */ + min-height: auto; position: relative; - padding: 2rem 0; + padding: 4rem 0; `; const RewardCard = ({ title, points, delay }: { title: string, points: string[], delay: number }) => (
Date: Thu, 12 Feb 2026 05:35:29 +0530
Subject: [PATCH 3/8] feat: Mission control page
---
pages/index.tsx | 2 +-
pages/mission-control.tsx | 273 ++++++++++++++++++
.../images/mission-control/deployment.png | Bin 0 -> 19446 bytes
.../images/mission-control/employee.png | Bin 0 -> 28913 bytes
.../assets/images/mission-control/globe.png | Bin 0 -> 1324553 bytes
.../mission-control/public-relation.png | Bin 0 -> 30175 bytes
.../images/mission-control/simulation.png | Bin 0 -> 29728 bytes
.../assets/images/mission-control/skill.png | Bin 0 -> 17511 bytes
src/components/landing/Header.tsx | 129 +--------
src/components/shared/GlitchText.tsx | 72 +++--
src/components/shared/TopBar/index.tsx | 8 +-
11 files changed, 313 insertions(+), 171 deletions(-)
create mode 100644 pages/mission-control.tsx
create mode 100644 public/assets/images/mission-control/deployment.png
create mode 100644 public/assets/images/mission-control/employee.png
create mode 100644 public/assets/images/mission-control/globe.png
create mode 100644 public/assets/images/mission-control/public-relation.png
create mode 100644 public/assets/images/mission-control/simulation.png
create mode 100644 public/assets/images/mission-control/skill.png
diff --git a/pages/index.tsx b/pages/index.tsx
index 89c6ffa..558cc72 100644
--- a/pages/index.tsx
+++ b/pages/index.tsx
@@ -11,7 +11,7 @@ import SiteView from '../src/components/SiteView';
const LandingPage = () => {
return (
+ > + Operation VAJRA has been initiated to restore command authority, analyse hostile cyber activity, and secure critical digital systems affected by external interference. +
++ > + Operation VAJRA is structured to: +
++ > + Operation VAJRA follows a progressive operational model, where participants are exposed to increasing levels of complexity and responsibility. +
++ > + The mission emphasizes: +
+
+ + Teams are inducted into the operation and granted access to Mission Control. Initial orientation and operational briefings are issued. +
+
+ + Participants undergo structured capability building through guided learning sessions and technical exercises designed to establish operational readiness. +
+
+ + Controlled simulations are conducted to evaluate preparedness, adaptability, and familiarity with mission environments. +
+
+ + Teams participate in a national-level cyber engagement designed to assess performance under time constraints and adversarial conditions. +
+
+ + Top-performing teams are deployed onsite for advanced operational challenges and final evaluation. +
++ > + Operation VAJRA is executed under the following command principles: +
++ > + Operation VAJRA is not a one-time exercise. +
++ > + It is a deliberate, long-duration operation designed to prepare participants for real-world cyber defence roles. +
++ > + Only teams that demonstrate discipline, adaptability, and technical depth will progress. +
+