@swyaeta

Hey, I’m Swyaeta and this is my personal portfolio website, built completely from scratch using HTML, CSS, and JS.I went full neo-brutalist on this one—think thick black borders everywhere, hard offset shadows that pop into 3D when you hover, bold uppercase headers in Orbitron, and Rajdhani for the body text. I spent a solid hour choosing the light mode colors, landing on a pink, berry, and neon yellow accent that gives major Hello Kitty energy. And because it’s 2026, it obviously has a dark mode toggle.Here’s how the pages break down: index.html (Home): The layout looks like a digital desk with scattered, tilted cards thrown around like sticky notes. The hero card with my name and tagline has extra padding to breathe, plus a massive offset shadow that makes it jump out. explore.html (About): This is where I drop my coding origin story, education, roles, skills, and hobbies. It uses a totally different layout to switch things up, complete with its own navbar and quick back buttons. contact.html (Contact Hub): The final piece. It features a top-left back button, a bright yellow navbar (Home, Learn More, Contact Hub), a live visitor counter, and the dark mode toggle tucked into the corner.

Devlog #1 Heyyy!!! i’m sweta and i’m making a SAT prep app for international students. So, most prep apps assume cultural context American students already have — idioms, references, essay phrasing. International students often lose points not from weak math, but from never having heard a phrase like “the writing was compelling.” This app gives AI-generated explanations that adapt to the student’s education system and English level.
Stack: Flutter (one app for Android/iOS/web), Dart (Flutter’s language), Firebase (handles accounts/data, no server needed), Gemini API (generates explanations).
Installing Flutter
winget didn’t have it, so I cloned it from GitHub:
git clone https://github.com/flutter/flutter.git C:\flutter
Added it to PATH so the terminal recognizes the flutter command:
$env:Path += “;C:\flutter\bin”
Ran flutter doctor to check the setup.
VS Code + Android SDK
Installed the Flutter extension (pulls in Dart too) — had to restart VS Code before commands appeared. Installed Android Studio only to get the Android SDK in the background; all real coding happens in VS Code. Fixed missing command-line tools via Android Studio’s SDK Manager, and accepted licenses with flutter doctor –android-licenses.
Skipping the emulator
Emulators eat RAM my laptop doesn’t have spare. Testing on my real phone over USB instead — enabled Developer Options + USB debugging, allowed the popup, confirmed detection with flutter devices.
First run
flutter create sat_prep_app
cd sat_prep_app
flutter run
create makes a starter project with a demo app built in. run compiles and installs it on the connected phone. Slow first build, but it worked — proof the whole chain (Flutter → SDK → phone) connected properly.
Firebase setup
Created a free Firebase project (no billing), registered an Android app, placed the generated google-services.json config into android/app/. Added packages:
flutter pub add firebase_core
flutter pub add firebase_auth
flutter pub add google_sign_in
pub add installs pre-written code instead of writing it myself. firebase_core is required for any Firebase feature, firebase_auth handles sign up/login, google_sign_in adds Google login.
Linking Flutter to Firebase
dart pub global activate flutterfire_cli
npm install -g firebase-tools
firebase login
flutterfire configure
The FlutterFire CLI needed the separate official Firebase CLI too. The last command generated firebase_options.dart, auto-configuring Android, iOS, web, macOS, and Windows at once.
Making the app use it
Added Firebase initialization to the app’s startup code, swapped the demo app for a placeholder “Sign Up Screen Coming Soon” screen. Ran it again — showed up cleanly, no crashes, confirming Firebase is wired in.
What’s next
Real Sign Up and Login screens, connected to Firebase Authentication, then (country, education system, English level, SAT goals) (i’m using my phone not a emulator)

#devlog 2
After receiving feedback from the reviewer, I have made required changes and created a public test server where anyone can try the bot live and added a permanent bot invite link to the README and added the test server link to the README

The bot is live 24/7 on Railway. Anyone can now test it by joining the test server or adding it directly to their own server using the invite link in the README.

Devlog 1 —

Heyyyy. I’m sweta .Today, I’ve built a discord bot and it’s called studbudie. Basically, the whole point of this is to be a study companion that lives in your discord server.

The idea came from the fact that during a study session you’re constantly switching context. you need a timer, you open a tab. you need motivation, you scroll through pinterest or insta. you need to remember to take a break, you forget entirely and return to study hours later. So, I wanted something that just lives in our server

Setup:
Wrote all the code in Visual Studio Code — in JavaScript, running on Node.js, with Discord.js v14 handling everything on the Discord side. dotenv to keep the token out of the repo, .gitignore set up early so nothing sensitive accidentally made it to github.
the actual coding was fine. what took forever was just getting the bot online for the first time. there’s this whole process — create the application on the discord developer portal, generate the token, figure out the permissions, run it and just sit there hoping the terminal doesn’t throw an error. it took a few tries. but when it finally connected and I typed !ping and it actually responded — that was a good moment and again i had to make it work 24/7 so i used railway and officallyyy made it a working bot and i have submitted it in top.gg so others (check it out) can use it.
To find it:
I have pushed it in github repo:
github.com/swyaeta/studbudie with an MIT license so anyone can use or build on it.

This is where most of the day went. ended up with 21 commands total. here’s the breakdown:

Timers —
!shorttimer — 10 min, for quick focused bursts when you don’t have much time
!timer — 25 min, the classic pomodoro
!longtimer — 50 min, for when you’re properly in flow and don’t want to break early
!extralongimer — 90 min, deep work, the serious one

Motivation —

!motivation — random motivational quote to push through when you’re dragging
!quote — inspirational quotes from people who actually did things

Knowledge and tips —

!tip — random study tip, stuff that’s actually useful
!fact — random science fact, good for a brain break without fully zoning out

Mental reset —

!breathe — walks you through a breathing exercise. underrated how much this helps mid session
!stress — stress relief tips for when things are getting to you

Session structure —

!focus — a checklist to get properly into focus mode before starting
!break — reminder of what a real break looks like (not just switching to youtube)
!morning — a full morning study routine to start the day right
!night — wind down routine for ending a study session properly

Exam specific —

!exam — exam prep tips, what to actually do in the days before
other —

!challenge — a small brain challenge, keeps things interesting
!celebrate — for when you finish something, because that matters

with this u can study without leaving discord!!!
!hello, !ping, !help, !introduction, !about — the standard stuff every bot needs
and thats all!! This was quite funnnn!!