@yeagerist

In this session I wrote the readme file for Nexus.
I also made Nexus deployable and hosted through github pages. I took help from the guide for this process. Finally Nexus is live now

Two major updates at once this time..
–I’ve completed the daily task feature which was previously only a skeleton. Now you can add your tasks and mark it checked as in the pic after youve completed it.
–I’ve also added the focus timer for you lots to get over-stimulated :) . For now, only I can choose the timer time which I’ve chosen 5 mins. You can pause and resume the timer. (adding this feature reminded me I’m good at maths ><)

I made the shortcuts section responsive and usuable.
You can add a new shortcut with its link and it’ll update in the main page.
It vanishes just after a reload tho ><
Finally functions like an actual new tab page now

As promised,
Nexus has its own analog clock now..
This design was what I initially envisioned. The previous version was just a placeholder for my html section.
This one little update took a lot cus my math wasn’t mathing at all. After trials and error, I looked up some reference and finally managed a live-working one.
Hope yall like the update

Nexus gets little life now..
I’ve added some JS functions for date and time functionality. The page even greets you as per your time of the day. Also added a feature for remaining time of the day to boost up your morale haha.
I also embedded lucide for header icons and implemented the relevant CSS.
Well, finally it’s now a html+css+js thing but still need to add more..
(dw i’ll replace that dirty thing with an analog clock later)

Nexus has its own look now.
This session was supposed to be CSS along with JS but i figured i could just separate the logs for them.
SO this is just the part for visual foundation.
I’d envisioned a dark purpulish theme and pre-designed the layout in canva but implementing that in actual code was really troublesome.
I’ve been trying to make the page fit-to-screen with all the sections unhindered but cant seem to manage it idk why.
for now I’ve just decreased the box size of shortcuts and workspace to make it fit but later after actual content is added idk how I’m gonna manage that.
If anyone can help, I’d be glad.
Here’s the current look after CSS foundation.

NEXUS- All in ONE

–I’ve kicked off my new stardance mission - Give your website a pulse with “Nexus” which is a custom new-tab-style dashboard designed to make opening a new tab little more useful.
I’ve spent the first hour of work setting up the project with Vite and Vanilla JS and planning the main sections and look of page in Canva and implementing it in html.

So yes, The UI is still a skeleton right now, but the foundation is in place.
Next up, I’ll be giving my page a little life with CSS and JS

HellOS guys//
Finally the work is done.
For the code part, I added the maximize, shorter and window_click functions and that’s it.
Other than that, I added a README file and deployed it through github pages and added the live link.

HellOS guys..
Today I’ve done lots and lots work.
I added CSS for the whole thing( app openings, default window, os menu and all)
Now just making the thing device responsive is left.
But mainly, Ive added some functions for app closing and opening as well. Finally, its now a html + css + js thing and here’s the first look.

HellOS guys (zehahaha).
So this me trying for the first time to make my very own version of OS. I’ve made a few sites before but nothing this kind ever.
What I’ve done up untill now is-
I structured the html as I’ve envisioned my webOS to be. I added little web icons and all from shortcut icon.
I’ve imagined a main OS page and drafted one out on canva but I won’t be revealing that rn.
This time, just see how the structure is.
(No CSS, No JS yet)

Rewrote the READMe from sctrach and tuned up the CSS a bit cus they asked ¯_(ツ)_/¯

it seems the css wasnt responding well in feed page after the hosting.
took me some time but i’ve fixed the code and it works as expected now :)

just improved the Readme a bit
nothing much nothing more
showed for review and now adjusted as per the recommendations.
Now the next thing is finally the shipping of project
Optimistic to hear your says on this😄😄

I spent some time cleaning up the frontend code and styles to make the app faster and easier to maintain.

Split up bloated pages: Broke down massive files like Item Detail, Recovery Requests, Feed, and Navbar into smaller subcomponents (modals, media previews, contact info, filters). Now editing one UI block won’t risk breaking the whole page.

Fixed React state quirks: Switched Feed categories to derive directly with useMemo to skip extra re-renders, fixed initial edit form state, and added cleanup guards on API calls so navigating away doesn’t trigger memory leak warnings.

Cleaned up the CSS: Replaced duplicated skeleton loaders and empty-state styles across 5 files with shared rules in index.css. Swapped hardcoded colors and overlays across all stylesheets for theme tokens so dark and light modes behave properly everywhere.

Finally got the main workflow of Lost&Found working!
The posting flow and matching system are connected now, so users can actually post lost or found items and the backend can go through the matching logic to find possible matches. I also finished up the remaining bits around resolving cases, notifications, and the other backend connections.
I’ve now made the project deployable too. The frontend is hosted on Vercel and the backend is running on Render, and I’ve connected the two so the live app can actually communicate with the backend.
There are obviously still things I can improve later, but for now the main workflow is working properly and the project is finally ready to ship.

Been working on connecting the rest of the backend now.
I got the resolving part done so when someone gets their item back, they can mark the case as resolved and it gets taken out of the active feed instead of sitting there like it’s still available. I also worked on the privacy policy agreement during signup, making sure that gets properly handled instead of just being a checkbox that does nothing.
Apart from that I’ve connected the remaining reports, notifications, matching and user posts so they all actually talk to the backend properly. Most of the main stuff is pretty much done now, just a few small things left to fix and test.

After that it should finally be ready to ship. Next devlog is basically going to be getting everything ready for deployment😋