You are browsing as a guest. Sign up (or log in) to start making projects!

SK

@SK

Joined June 6th, 2026

  • 7Devlogs
  • 5Projects
  • 1Ships
  • 0Votes
I am currently a first year btech student. I would really appreciate if you check out projects made by me!
Open comments for this post

49m 49s logged

Devlog1: My Codespace go kaboom

I was editing index.css of the vite just to test out different application of things and then i went to check out another website deployment and when i returned it, the connection was lost so I reloaded the page and then everything was gone and a similar pop up that’s in the screenshot popped.

So all the files were gone and then retried installing the vite modules and bootsrap from the terminal it says command not found. I asked github chat nearby that check why vite is not getting installed so it said to install node, then i realised lets create a new repository.

Reason- Github codespace already provides environment for these things which we generally have to install on a desktop , so installing one will again create a huge mess and will also affect deployment indirectly.

All the progress is gone but its never too late to start again

Devlog1: My Codespace go kaboom

I was editing index.css of the vite just to test out different application of things and then i went to check out another website deployment and when i returned it, the connection was lost so I reloaded the page and then everything was gone and a similar pop up that’s in the screenshot popped.

So all the files were gone and then retried installing the vite modules and bootsrap from the terminal it says command not found. I asked github chat nearby that check why vite is not getting installed so it said to install node, then i realised lets create a new repository.

Reason- Github codespace already provides environment for these things which we generally have to install on a desktop , so installing one will again create a huge mess and will also affect deployment indirectly.

All the progress is gone but its never too late to start again

Replying to @SK

0
Open comments for this post

16m 46s logged

Deployment Debugging and Re-Certification Journey

Today’s ship turned into a deployment debugging session rather than a coding session.

I had already completed my React + Vite calculator and deployed it on Render. After submitting it for review, I received feedback that Render free-tier links are not accepted because they may become unavailable in the future.

To solve this, I decided to migrate the project to GitHub Pages and began setting up a new deployment workflow.

The migration wasn’t smooth. Although GitHub Pages reported that the site was live, opening the link only showed a blank white screen. After checking the repository structure, deployment settings, and project configuration, I traced the issue to the Vite base path configuration.

Once the base path was corrected, I rebuilt the project, redeployed it, and tested the site again.

Success — the calculator loaded correctly and the GitHub Pages deployment worked as expected.

This experience taught me that shipping a project isn’t only about writing code. Understanding deployment, hosting platforms, project structure, and debugging production issues is just as important.

The calculator is now successfully hosted, ready for re-certification, and I’m ready to move on to building and shipping the next project.

Deployment Debugging and Re-Certification Journey

Today’s ship turned into a deployment debugging session rather than a coding session.

I had already completed my React + Vite calculator and deployed it on Render. After submitting it for review, I received feedback that Render free-tier links are not accepted because they may become unavailable in the future.

To solve this, I decided to migrate the project to GitHub Pages and began setting up a new deployment workflow.

The migration wasn’t smooth. Although GitHub Pages reported that the site was live, opening the link only showed a blank white screen. After checking the repository structure, deployment settings, and project configuration, I traced the issue to the Vite base path configuration.

Once the base path was corrected, I rebuilt the project, redeployed it, and tested the site again.

Success — the calculator loaded correctly and the GitHub Pages deployment worked as expected.

This experience taught me that shipping a project isn’t only about writing code. Understanding deployment, hosting platforms, project structure, and debugging production issues is just as important.

The calculator is now successfully hosted, ready for re-certification, and I’m ready to move on to building and shipping the next project.

Replying to @SK

0
Open comments for this post

1h 9m 24s logged

DevLog #2 — Bringing the Archive to Life

Progress Update

This development phase focused on transforming the initial concept of Mystery Files into a fully navigable investigation archive. The core desktop environment is now complete, featuring draggable windows, a live system clock, and dedicated modules for Case Files, Suspects, Evidence, and Timeline.

Building the Investigation

The first case, The Midnight Ledger, has been established as the foundation of the project. Suspects, clues, and timeline events have been organized into separate investigation modules, allowing users to explore the mystery piece by piece rather than through a traditional linear story.

Design Direction

A major focus was creating an atmosphere that feels authentic and immersive. The dark visual theme, floating windows, and case-management layout were designed to make the experience resemble a real investigative database rather than a conventional website.

Current State

The project now functions as a complete detective-themed desktop application with a clear structure, consistent design language, and a working investigation system. While the mystery itself is only beginning to unfold, the archive is now ready for future expansion and interactive features.

Looking Ahead

The next phase will focus on deeper interactivity, stronger connections between evidence and suspects, and additional case content. With the foundation now in place, the goal is to evolve Mystery Files from a static archive into a true investigative experience.

Main charachter - JUNE MERCER

DevLog #2 — Bringing the Archive to Life

Progress Update

This development phase focused on transforming the initial concept of Mystery Files into a fully navigable investigation archive. The core desktop environment is now complete, featuring draggable windows, a live system clock, and dedicated modules for Case Files, Suspects, Evidence, and Timeline.

Building the Investigation

The first case, The Midnight Ledger, has been established as the foundation of the project. Suspects, clues, and timeline events have been organized into separate investigation modules, allowing users to explore the mystery piece by piece rather than through a traditional linear story.

Design Direction

A major focus was creating an atmosphere that feels authentic and immersive. The dark visual theme, floating windows, and case-management layout were designed to make the experience resemble a real investigative database rather than a conventional website.

Current State

The project now functions as a complete detective-themed desktop application with a clear structure, consistent design language, and a working investigation system. While the mystery itself is only beginning to unfold, the archive is now ready for future expansion and interactive features.

Looking Ahead

The next phase will focus on deeper interactivity, stronger connections between evidence and suspects, and additional case content. With the foundation now in place, the goal is to evolve Mystery Files from a static archive into a true investigative experience.

Main charachter - JUNE MERCER

Replying to @SK

0
Open comments for this post

1h 8m 15s logged

DevLog #1 — The Beginning of Mystery Files

Why I Started This Project

When I first began building my personalOS project, I considered creating a traditional portfolio-style experience. While that approach would have worked, it didn’t feel particularly memorable.

I wanted to build something that people would want to explore.

Something that felt less like a website and more like stepping into a story.

That idea eventually became Mystery Files — a fictional detective archive where users investigate clues, examine evidence, review suspects, and reconstruct events surrounding an unsolved case known as The Midnight Ledger.

The Vision

My goal is not simply to create a collection of web pages.

I want the project to feel like a real investigative system.

When someone opens the site, I want them to feel as though they have been granted access to a restricted detective database. Every window, every piece of evidence, every suspect profile, and every timeline entry should contribute to a larger mystery waiting to be solved.

Rather than telling users a story directly, I want them to uncover it themselves.

Building the Foundation

This development phase focused on creating the core structure that everything else will be built upon.

The operating-system style interface is now functional and serves as the central hub for the investigation.

Current features include:

✓ Desktop-style environment

✓ Draggable application windows

✓ Open and close window controls

✓ Investigation-themed navigation

✓ Live system clock

✓ Multi-window workflow

✓ Responsive information panels

The Midnight Ledger

To give the project a strong narrative foundation, I created the first case file: The Midnight Ledger.

The case revolves around the mysterious disappearance of an important museum ledger during a stormy night.

At first glance, the crime appears simple.

However, as evidence accumulates and timelines begin to overlap, multiple suspects emerge, each with motives, opportunities, and secrets of their own.

The truth remains hidden somewhere within the investigation.

Investigation Modules

To organize information, I introduced several dedicated sections:

📁 Case Files

The central location for case briefings, background information, and investigation summaries.

🧾 Suspects

Profiles containing motives, alibis, and relationships to the case.

🔍 Evidence

Collected clues and physical items connected to the investigation.

⏱️ Timeline

A chronological reconstruction of important events leading up to the crime.

Design Direction

A large amount of time was spent shaping the atmosphere of the project.

I wanted the interface to feel professional, mysterious, and immersive.

The dark color palette, floating windows, information cards, and investigation-focused layout were all chosen to support that goal.

Every design decision was made with one question in mind:

“Does this feel like a real detective system?”

Challenges Along the Way

One of the biggest challenges was finding the balance between storytelling and usability.

A mystery is only interesting if information is revealed gradually, but a website must still be easy to navigate.

Designing separate investigative windows proved to be an effective solution, allowing information to remain organized while preserving the feeling of exploring a case file.

Looking Ahead

Although this is only the first development log, the foundation is now in place.

For now, Mystery Files exists as the opening chapter of a much larger story.

The archive has been created.

The evidence has been collected.

The suspects have been identified.

The only thing missing is the truth.

DevLog #1 — The Beginning of Mystery Files

Why I Started This Project

When I first began building my personalOS project, I considered creating a traditional portfolio-style experience. While that approach would have worked, it didn’t feel particularly memorable.

I wanted to build something that people would want to explore.

Something that felt less like a website and more like stepping into a story.

That idea eventually became Mystery Files — a fictional detective archive where users investigate clues, examine evidence, review suspects, and reconstruct events surrounding an unsolved case known as The Midnight Ledger.

The Vision

My goal is not simply to create a collection of web pages.

I want the project to feel like a real investigative system.

When someone opens the site, I want them to feel as though they have been granted access to a restricted detective database. Every window, every piece of evidence, every suspect profile, and every timeline entry should contribute to a larger mystery waiting to be solved.

Rather than telling users a story directly, I want them to uncover it themselves.

Building the Foundation

This development phase focused on creating the core structure that everything else will be built upon.

The operating-system style interface is now functional and serves as the central hub for the investigation.

Current features include:

✓ Desktop-style environment

✓ Draggable application windows

✓ Open and close window controls

✓ Investigation-themed navigation

✓ Live system clock

✓ Multi-window workflow

✓ Responsive information panels

The Midnight Ledger

To give the project a strong narrative foundation, I created the first case file: The Midnight Ledger.

The case revolves around the mysterious disappearance of an important museum ledger during a stormy night.

At first glance, the crime appears simple.

However, as evidence accumulates and timelines begin to overlap, multiple suspects emerge, each with motives, opportunities, and secrets of their own.

The truth remains hidden somewhere within the investigation.

Investigation Modules

To organize information, I introduced several dedicated sections:

📁 Case Files

The central location for case briefings, background information, and investigation summaries.

🧾 Suspects

Profiles containing motives, alibis, and relationships to the case.

🔍 Evidence

Collected clues and physical items connected to the investigation.

⏱️ Timeline

A chronological reconstruction of important events leading up to the crime.

Design Direction

A large amount of time was spent shaping the atmosphere of the project.

I wanted the interface to feel professional, mysterious, and immersive.

The dark color palette, floating windows, information cards, and investigation-focused layout were all chosen to support that goal.

Every design decision was made with one question in mind:

“Does this feel like a real detective system?”

Challenges Along the Way

One of the biggest challenges was finding the balance between storytelling and usability.

A mystery is only interesting if information is revealed gradually, but a website must still be easy to navigate.

Designing separate investigative windows proved to be an effective solution, allowing information to remain organized while preserving the feeling of exploring a case file.

Looking Ahead

Although this is only the first development log, the foundation is now in place.

For now, Mystery Files exists as the opening chapter of a much larger story.

The archive has been created.

The evidence has been collected.

The suspects have been identified.

The only thing missing is the truth.

Replying to @SK

0
Ship

I built a fully functional calculator using React, Vite, and Bootstrap. The calculator supports basic arithmetic operations such as addition, subtraction, multiplication, and division with a clean and responsive user interface.
The most challenging part was managing the calculator logic, handling user inputs correctly, and ensuring calculations were performed accurately while maintaining the application state in React.
I am proud of successfully creating a working calculator from scratch and implementing a responsive design using Bootstrap. This project helped me strengthen my understanding of React components, state management, event handling, and modern frontend development practices. Through this project, I learned how to build interactive user interfaces with React, organize components efficiently, and deploy applications using GitHub and Render.
To test the project, users can enter numbers using the calculator buttons, perform arithmetic operations, clear inputs, and verify that the displayed results are calculated correctly.

  • 4 devlogs
  • 5h
Try project → See source code →
Open comments for this post

2h 40m 10s logged

Completed the code for project calculator

Completed the code for project calculator

Replying to @SK

0
Open comments for this post

1h 1m 8s logged

I am currently working on the functioning of react by implementing html, js and css in it.

I am currently working on the functioning of react by implementing html, js and css in it.

Replying to @SK

0

Followers

Loading…