|
39574
|
Music Player by @Pathaks_OP | Stardance
|
Pathaks_OP
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Music Player by @Pathaks_OP | Stardance
|
1792731043.1470656
|
1793335843.1470656
|
|
17001
|
Untitled by @ImNotIvy | Stardance
|
ImNotIvy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ImNotIvy | Stardance
|
1792731042.2987106
|
1793335842.2987106
|
|
13998
|
My very own WebOS by @amk9809 | Stardance
|
amk9809
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @amk9809 | Stardance
|
1792731041.4603038
|
1793335841.4603038
|
|
8372
|
Printer Vendo by @rul3zero | Stardance
|
rul3zero
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Printer Vendo by @rul3zero | Stardance
|
1792731040.6249046
|
1793335840.6249046
|
|
38574
|
Untitled project by @aygerim | Stardance
|
aygerim
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @aygerim | Stardance
|
1792731039.7873297
|
1793335839.7873297
|
|
37724
|
yber Smart Clock Air Quality, Pomodoro Alarm by @T yber Smart Clock Air Quality, Pomodoro Alarm by @TRIX | Stardance...
|
TRIX
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: yber Smart Clock Air Quality, Pomodoro Alar Title: yber Smart Clock Air Quality, Pomodoro Alarm by @TRIX | Stardance...
|
1792731038.9547327
|
1793335838.9547327
|
|
6830
|
AI ascii art maker by @spawnedshoyo | Stardance
|
spawnedshoyo
|
1
|
17.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-06T22:42:10Z", "hours": 17.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I built this ASCII Art Maker as a fun project to explore image processing and ASCII conversion. The tool lets you either generate images from text prompts using AI or upload your own images, then converts them to ASCII art. Feel free to suggest ideas for my next project! I’m always looking for new challenges and interesting things to build.", "repo": "https://github.com/RandomAiPerson/AsciiGenerator", "demo": "https://randomaiperson.github.io/AsciiGenerator/"}]...
|
[{"post_id": 23786, "ts": "202 [{"post_id": 23786, "ts": "2026-07-06T22:39:56Z", "hours": 16.6358, "text": "I built this ASCII Art Maker as a fun project to explore image processing and ASCII conversion. The tool lets you either generate images from text prompts using AI or upload your own images, then converts them to ASCII art. Feel free to suggest ideas for my next project! I’m always looking for new challenges and interesting things to build."}]...
|
Title: AI ascii art maker by @spawnedshoyo | Stard Title: AI ascii art maker by @spawnedshoyo | Stardance
Devlogs:
I built this ASCII Art Maker as a fun project to explore image processing and ASCII conversion. The tool lets you either generate images from text prompts using AI or upload your own images, then converts them to ASCII art. Feel free to suggest ideas for my next project! I’m always looking for new challenges and interesting things to build.
Ships:
I built this ASCII Art Maker as a fun project to explore image processing and ASCII conversion. The tool lets you either generate images from text prompts using AI or upload your own images, then converts them to ASCII art. Feel free to suggest ideas for my next project! I’m always looking for new challenges and interesting things to build....
|
1793249438.5757017
|
1793335838.5757017
|
|
6399
|
My awesome macropad! by @Belar | Stardance
|
Belar
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Belar | Stardance
|
1792731038.0921018
|
1793335838.0921018
|
|
15025
|
berryOS by @SysError06 | Stardance
|
SysError06
|
1
|
6.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-16T05:02:27Z", "hours": 6.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "webOS, directly ran inside your browser (desktop app coming soon?) What is it? - berryOS is a “simple” webOS that allows you to have your own little Catppuccin inspired operating system right inside your browser! It offers a notes app, welcome page and a settings app (more apps to come). What I learnt - I found this project as a good way to learn SvelteKit, as ReactJS has gotten me very pissed off, and SvelteKit seemed like a good alternative to React as it has no heavy virtual DOM. Overall, SvelteKit seems like a choice I don’t regret, as it does everything I need it to do! What’s coming next - Proper alt tabbing system, persistent settings, more apps, desktop icons, terminal, browser (possibly), desktop and more!", "repo": "https://github.com/UltimatePlayer97/berryOS", "demo": "https://ultimateplayer97.github.io/berryOS/"}]...
|
[{"post_id": 9028, "ts": "2026 [{"post_id": 9028, "ts": "2026-06-15T01:58:35Z", "hours": 0.7714, "text": "Custom desktop and accent colors! I added a modular color picker component in the Personalization settings panel. Clicking a preset or using the native eye-dropper custom color tool instantly updates buttons, icons, switches, and highlights across the entire OS. I also implemented a FileReader data-stream pipeline. Users can upload any .jpg, .png, or .webp file from their local machine, converting it to a base64 string to update the active desktop background immediately. Also, if a user doesn’t have a custom wallpaper, the default desktop gradient now intelligently samples the chosen accent color, blending a low-opacity hue directly into the dark/light background."}, {"post_id": 8522, "ts": "2026-06-14T05:24:11Z", "hours": 1.3242, "text": "Alt tabbing (sort of). A lot of this time was spent refactoring the window system to use a windows object. To start off, I tried adding a navigator.connection API to try and identify cellular vs wifi vs ethernet structures, however as of reading the MDN docs it turns out its not a very common API, with Firefox dropping it as of Firefox 31, and Safari never having it in the first place, I ended up switching to the onLine/offLine property, which is supported by all mainstream browsers. Also Alt + tab is currently slightly broken, as it does not yet show a window preview, as well as not properly focusing the chosen window, however this is something I will tackle later on, as I plan on adding custom wallpaper support now."}, {"post_id": 7985, "ts": "2026-06-13T09:59:58Z", "hours": 0.7036, "text": "(flashbang warning) Light mode! Changes CSS values to respect the theme detection, also tries auto detect light/dark mode based on browser settings. Oh yes also changed up the topbar to look better (looks alot more like macOS now which I may change in the future.)"}, {"post_id": 7948, "ts": "2026-06-13T08:08:40Z", "hours": 0.4956, "text": "Simple stuff this time around, just made the desktop look more like macOS, will probably edit though so it doesn’t look TOO similar. Will add the ability to change dark/light mode and background next!"}, {"post_id": 7933, "ts": "2026-06-13T07:29:29Z", "hours": 1.5186, "text": "So, A LOT of time was spent on this, a lot more than I anticipated. Firstly, I added a new settings app (which currently only has like one setting) that uses shadcn’s components for switches, buttons, sliders, etc. This was because I did NOT want to make my own components from scratch. Quick look at the docs, I added my necessary components, and CSS theming. I had a slight issue with setting raw CSS variables on .dark blocks weren’t syncing up properly with unedited shadcn svelte components due to Tailwind’s V4 theme compiler rules. Configuring custom colors directly in the @theme inline block in layout.css seemed to fix this. I also migrated the dock into its own components (Dock.svelte), allowing for better scalability. Overall, pretty happy with this session, as now I can seamlessly add settings, add components, app, and all. The new task is to clean up the desktop, making it more visually appealing to the eyes."}, {"post_id": 7394, "ts": "2026-06-12T10:05:11Z", "hours": 0.4731, "text": "Not much was doen apart from porting the gh pages to SvelteKit Was done by making a deploy.yml workflow that builds the website and deploys it to GitHub Pages. Next plan of action is cleaning up desktop to make it more pleasing on the eyes"}, {"post_id": 7165, "ts": "2026-06-11T23:30:15Z", "hours": 0.5956, "text": "Sigh….. I got bored I hate vanilla html and javascript, so…. I switched my webOS entirely to SvelteKit. This change should help me add components easier, also can add better stuff, I have also switched from base CSS to TailwindCSS, which is what I’m more used to. What I plan on doing is making every app its own svelte page, making it really easy to add apps. Overall nothing changed for now, I just spent the time porting over to SvelteKit."}, {"post_id": 6765, "ts": "2026-06-11T10:24:32Z", "hours": 0.5825, "text": "First devlog of berryOS! This is part of the webOS mission, however I am already pretty experienced in web devving so I kinda improvised on some stuff. I got an app dock, windows, topbar, time and a background!"}]...
|
Title: berryOS by @SysError06 | Stardance
Devlogs Title: berryOS by @SysError06 | Stardance
Devlogs:
First devlog of berryOS! This is part of the webOS mission, however I am already pretty experienced in web devving so I kinda improvised on some stuff. I got an app dock, windows, topbar, time and a background!
Sigh….. I got bored I hate vanilla html and javascript, so…. I switched my webOS entirely to SvelteKit. This change should help me add components easier, also can add better stuff, I have also switched from base CSS to TailwindCSS, which is what I’m more used to. What I plan on doing is making every app its own svelte page, making it really easy to add apps. Overall nothing changed for now, I just spent the time porting over to SvelteKit.
Not much was doen apart from porting the gh pages to SvelteKit Was done by making a deploy.yml workflow that builds the website and deploys it to GitHub Pages. Next plan of action is cleaning up desktop to make it more pleasing on the eyes
So, A LOT of time was spent on this, a lot more than I anticipated. Firstly, I added a new settings app (which currently only has like one setting) that uses shadcn’s components for switches, buttons, sliders, etc. This was because I did NOT want to make my own components from scratch. Quick look at the docs, I added my necessary components, and CSS theming. I had a slight issue with setting raw CSS variables on .dark blocks weren’t syncing up properly with unedited shadcn svelte components due to Tailwind’s V4 theme compiler rules. Configuring custom colors directly in the @theme inline block in layout.css seemed to fix this. I also migrated the dock into its own components (Dock.svelte), allowing for better scalability. Overall, pretty happy with this session, as now I can seamlessly add settings, add components, app, and all. The new task is to clean up the desktop, making it more visually appealing to the eyes.
Simple stuff this time around, just made the desktop look more like macOS, will probably edit though so it doesn’t look TOO similar. Will add the ability to change dark/light mode and background next!
(flashbang warning) Light mode! Changes CSS values to respect the theme detection, also tries auto detect light/dark mode based on browser settings. Oh yes also changed up the topbar to look better (looks alot more like macOS now which I may change in the future.)
Alt tabbing (sort of). A lot of this time was spent refactoring the window system to use a windows object. To start off, I tried adding a navigator.connection API to try and identify cellular vs wifi vs ethernet structures, however as of reading the MDN docs it turns out its not a very common API, with Firefox dropping it as of Firefox 31, and Safari never having it in the first place, I ended up switching to the onLine/offLine property, which is supported by all mainstream browsers. Also Alt + tab is currently slightly broken, as it does not yet show a window preview, as well as not properly focusing the chosen window, however this is something I will tackle later on, as I plan on adding custom wallpaper support now.
Custom desktop and accent colors! I added a modular color picker component in the Personalization settings panel. Clicking a preset or using the native eye-dropper custom color tool instantly updates buttons, icons, switches, and highlights across the entire OS. I also implemented a FileReader data-stream pipeline. Users can upload any .jpg, .png, or .webp file from their local machine, converting it to a base64 string to update the active desktop background immediately. Also, if a user doesn’t have a custom wallpaper, the default desktop gradient now intelligently samples the chosen accent color, blending a low-opacity hue directly into the dark/light background.
Ships:
webOS, directly ran inside your browser (desktop app coming soon?) What is it? - berryOS is a “simple” webOS that allows you to have your own little Catppuccin inspired operating system right inside your browser! It offers a notes app, welcome page and a settings app (more apps to come). What I learnt - I found this project as a good way to learn SvelteKit, as ReactJS has gotten me very pissed off, and SvelteKit seemed like a good alternative to React as it has no heavy virtual DOM. Overall, SvelteKit seems like a choice I don’t regret, as it does everything I need it to do! What’s coming next - Proper alt tabbing system, persistent settings, more apps, desktop icons, terminal, browser (possibly), desktop and more!...
|
1793249437.3445404
|
1793335837.3445404
|
|
32983
|
LoLOS by @alinurLoL228 | Stardance
|
alinurLoL228
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: LoLOS by @alinurLoL228 | Stardance
|
1792731037.2351472
|
1793335837.2351472
|
|
38355
|
WarioWare Game by @Sky_ | Stardance
|
Sky_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: WarioWare Game by @Sky_ | Stardance
|
1792731036.3897913
|
1793335836.3897913
|
|
31359
|
Frictionless by @rhianna | Stardance
|
rhianna
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @rhianna | Stardance
|
1792731035.5281365
|
1793335835.5281365
|
|
44349
|
CGM Pattern Analyzer by @tripathi_saumil | Stardan CGM Pattern Analyzer by @tripathi_saumil | Stardance...
|
tripathi_saumil
|
1
|
2.71
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-08T07:45:35Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a completely free continuous glucose monitor analyzing device that is compatible with data from a Dexcom G6 and G7. This project is able to closely analyze trends and identify phenomena found commonly in said trends. Honestly, the most challenging part was definitely getting the API to work. Lots of the other things weren’t easy but they definitely weren’t as hard and API key installation. I would say I’m most proud of that honestly. One major thing to know about this project is that I’m using only free resources, so I kind of don’t have a lot of calls available on my API per day. It should be able to work at least 5-8 times depending on how much data is used.", "repo": "https://github.com/SaumilT67/cgm_pattern_analyzer", "demo": "https://cgm-pattern-analyzer-mb3c.vercel.app"}]...
|
[{"post_id": 75469, "ts": "202 [{"post_id": 75469, "ts": "2026-09-30T05:41:33Z", "hours": 1.46, "text": "Changed a lot of the html to give it a better look. I think it looks way better since I did it myself. The creme and teal color way is kind of nice honestly, and new button on the top bar to reset everything is also pretty sick. It’s supposed to be like a drop of blood to represent like a finger prick. I plan to do improve the prompt calling in the future because it’s a little bare right now. I also need to somehow make the API calling faster because the wait time is quire slow. Honestly I think I need to spend money for that. I realized a lot of people can’t really use this either so I might need to make a mock CSV and add it so people can try it out. Next update I’ll probably add a downloadable one people can use."}, {"post_id": 68384, "ts": "2026-09-15T01:13:45Z", "hours": 0.2508, "text": "Changed up the HTML a little to make it less AI"}, {"post_id": 43142, "ts": "2026-08-08T07:40:57Z", "hours": 0.4389, "text": "Finally got this up on a demo url that works with my API #lesguooooooo"}, {"post_id": 43108, "ts": "2026-08-08T06:12:29Z", "hours": 1.0294, "text": "This is my CGM Pattern Analyzer. Basically what it does is that it uses an API to analyze lots of data (and I mean a lot like 24/7 data from 90 days that records every 5 minutes (for any non-cgm wearers ;))). I’ve used it with my own data and it works well. It makes sure not to diagnose patients because that would be kinda bad, but it helps analyze patterns and common phenomena with diabetic patients. It took lots of work but we did it!"}]...
|
Title: CGM Pattern Analyzer by @tripathi_saumil | Title: CGM Pattern Analyzer by @tripathi_saumil | Stardance
Devlogs:
This is my CGM Pattern Analyzer. Basically what it does is that it uses an API to analyze lots of data (and I mean a lot like 24/7 data from 90 days that records every 5 minutes (for any non-cgm wearers ;))). I’ve used it with my own data and it works well. It makes sure not to diagnose patients because that would be kinda bad, but it helps analyze patterns and common phenomena with diabetic patients. It took lots of work but we did it!
Finally got this up on a demo url that works with my API #lesguooooooo
Changed up the HTML a little to make it less AI
Changed a lot of the html to give it a better look. I think it looks way better since I did it myself. The creme and teal color way is kind of nice honestly, and new button on the top bar to reset everything is also pretty sick. It’s supposed to be like a drop of blood to represent like a finger prick. I plan to do improve the prompt calling in the future because it’s a little bare right now. I also need to somehow make the API calling faster because the wait time is quire slow. Honestly I think I need to spend money for that. I realized a lot of people can’t really use this either so I might need to make a mock CSV and add it so people can try it out. Next update I’ll probably add a downloadable one people can use.
Ships:
I made a completely free continuous glucose monitor analyzing device that is compatible with data from a Dexcom G6 and G7. This project is able to closely analyze trends and identify phenomena found commonly in said trends. Honestly, the most challenging part was definitely getting the API to work. Lots of the other things weren’t easy but they definitely weren’t as hard and API key installation. I would say I’m most proud of that honestly. One major thing to know about this project is that I’m using only free resources, so I kind of don’t have a lot of calls available on my API per day. It should be able to work at least 5-8 times depending on how much data is used....
|
1793249435.5036354
|
1793335835.5036354
|
|
13067
|
Untitled project by @rajdeepm | Stardance
|
rajdeepm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @rajdeepm | Stardance
|
1792731034.699601
|
1793335834.699601
|
|
37734
|
My very own WebOS by @SkilledBtLzy | Stardance
|
SkilledBtLzy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @SkilledBtLzy | Starda Title: My very own WebOS by @SkilledBtLzy | Stardance...
|
1792731033.8574288
|
1793335833.8574288
|
|
25626
|
My first slack bot! by @naif | Stardance
|
naif
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @naif | Stardance
|
1792731032.9885495
|
1793335832.9885495
|
|
7458
|
My first slack bot! by @solarlunarr | Stardance
|
solarlunarr
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @solarlunarr | Stard Title: My first slack bot! by @solarlunarr | Stardance...
|
1792731032.1155777
|
1793335832.1155777
|
|
25136
|
Untitled by @araadh3111 | Stardance
|
araadh3111
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @araadh3111 | Stardance
|
1792731031.26348
|
1793335831.26348
|
|
8060
|
My awesome macropad! by @adittyanischal | Stardanc My awesome macropad! by @adittyanischal | Stardance...
|
adittyanischal
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @adittyanischal | S Title: My awesome macropad! by @adittyanischal | Stardance...
|
1792731030.4055738
|
1793335830.4055738
|
|
8238
|
Heaven demands death' by @lebiraja2007_9699 | Heaven demands death' by @lebiraja2007_9699 | Stardance...
|
lebiraja2007_9699
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Heaven demands death' by @lebiraja2007_ Title: Heaven demands death' by @lebiraja2007_9699 | Stardance...
|
1792731029.4607577
|
1793335829.4607577
|
|
31534
|
Untitled by @Anq | Stardance
|
Anq
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Anq | Stardance
|
1792731028.6087608
|
1793335828.6087608
|
|
44334
|
Nahida4479-Website by @Nahida4479 | Stardance
|
Nahida4479
|
1
|
3.05
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-05T22:57:44Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I built my personal website, featuring a project section and my GitHub account image.", "repo": "https://github.com/Nahida4479/Nahida4479-Website", "demo": "https://nahida4479.github.io/Nahida4479-Website/"}]...
|
[{"post_id": 42128, "ts": "202 [{"post_id": 42128, "ts": "2026-08-06T18:31:18Z", "hours": 1.0481, "text": "#Devlog4 Create About Me category"}, {"post_id": 41618, "ts": "2026-08-05T22:46:13Z", "hours": 0.9022, "text": "#Devlog3 My Github account image and floating title"}, {"post_id": 41592, "ts": "2026-08-05T21:45:01Z", "hours": 0.8614, "text": "#Devlog2 My project category and new background."}, {"post_id": 41547, "ts": "2026-08-05T20:37:22Z", "hours": 0.4972, "text": "#Devlog1 Website name and account image."}]...
|
Title: Nahida4479-Website by @Nahida4479 | Stardan Title: Nahida4479-Website by @Nahida4479 | Stardance
Devlogs:
#Devlog1 Website name and account image.
#Devlog2 My project category and new background.
#Devlog3 My Github account image and floating title
#Devlog4 Create About Me category
Ships:
I built my personal website, featuring a project section and my GitHub account image....
|
1793249428.0249872
|
1793335828.0249872
|
|
3862
|
Untitled by @hello4312 | Stardance
|
hello4312
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @hello4312 | Stardance
|
1792731027.7545352
|
1793335827.7545352
|
|
13123
|
My very own WebOS by @Hapis | Stardance
|
Hapis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Hapis | Stardance
|
1792731026.900149
|
1793335826.900149
|
|
11920
|
Dinosaur game by @ardeno99 | Stardance
|
ardeno99
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Dinosaur game by @ardeno99 | Stardance
|
1792731026.0649753
|
1793335826.0649753
|
|
7929
|
My first slack bot! by @delete | Stardance
|
delete
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @delete | Stardance
|
1792731025.1952605
|
1793335825.1952605
|
|
14132
|
My awesome macropad! by @LukeG | Stardance
|
LukeG
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @LukeG | Stardance
|
1792731024.3565383
|
1793335824.3565383
|
|
25254
|
Lunar Gaurdian by @inbaarasan215 | Stardance
|
inbaarasan215
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Lunar Gaurdian by @inbaarasan215 | Stardanc Title: Lunar Gaurdian by @inbaarasan215 | Stardance...
|
1792731023.4980123
|
1793335823.4980123
|
|
6435
|
wmata sound emulator by @sleekez | Stardance
|
sleekez
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: wmata sound emulator by @sleekez | Stardanc Title: wmata sound emulator by @sleekez | Stardance...
|
1792731022.639626
|
1793335822.639626
|
|
52444
|
Block Reality by @rocky59487 | Stardance
|
rocky59487
|
1
|
4.97
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-22T14:45:25Z", "hours": 4.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "During stardance, I built the public website for block reality,an early Minecraft structural analysis mod. The site explain how the project give blocks force 。", "repo": "https://github.com/rocky59487/block-reality", "demo": "https://rocky59487.github.io/block-reality-site/"}]...
|
[{"post_id": 58767, "ts": "202 [{"post_id": 58767, "ts": "2026-08-31T10:26:30Z", "hours": 0.2725, "text": "Block Reality mod is now live on CurseForge!"}, {"post_id": 57271, "ts": "2026-08-29T11:40:48Z", "hours": 0.6989, "text": "Finished v0.3b!"}, {"post_id": 52387, "ts": "2026-08-22T14:37:57Z", "hours": 0.9769, "text": "Add the install tutorial"}, {"post_id": 52284, "ts": "2026-08-22T12:16:49Z", "hours": 2.9161, "text": "I made the first version of the Block Reality website today. I started with Mimo and some HTML/CSS tutorials, then went back to the site and changed the structure, spacing, and styling myself. I finally understand the basic relationship: HTML decides what is on the page, and CSS decides how it looks, so I can now make simple pages and edits without relying on generated code for everything. The JavaScript visual effects were generated with Gemini; JS is still outside my current skill level, while I integrated and tested the result. The site and this first devlog are now online: https://rocky59487.github.io/block-reality-site/ Next I want to improve the mobile layout and learn enough JavaScript to change the effects myself."}]...
|
Title: Block Reality by @rocky59487 | Stardance
D Title: Block Reality by @rocky59487 | Stardance
Devlogs:
I made the first version of the Block Reality website today. I started with Mimo and some HTML/CSS tutorials, then went back to the site and changed the structure, spacing, and styling myself. I finally understand the basic relationship: HTML decides what is on the page, and CSS decides how it looks, so I can now make simple pages and edits without relying on generated code for everything. The JavaScript visual effects were generated with Gemini; JS is still outside my current skill level, while I integrated and tested the result. The site and this first devlog are now online: https://rocky59487.github.io/block-reality-site/ Next I want to improve the mobile layout and learn enough JavaScript to change the effects myself.
Add the install tutorial
Finished v0.3b!
Block Reality mod is now live on CurseForge!
Ships:
During stardance, I built the public website for block reality,an early Minecraft structural analysis mod. The site explain how the project give blocks force 。...
|
1793249421.7709012
|
1793335821.7709012
|
|
22505
|
Frictionless by @davidm | Stardance
|
davidm
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @davidm | Stardance
|
1792731021.7595768
|
1793335821.7595768
|
|
35389
|
My own site! by @AriannaA | Stardance
|
AriannaA
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My own site! by @AriannaA | Stardance
|
1792731018.2847664
|
1793335818.2847664
|
|
43083
|
My StarWebsite by @S-Akhil | Stardance
|
S-Akhil
|
1
|
5.0
|
5
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-03T10:27:02Z", "hours": 5.0, "multiplier": 1.01, "payout": 5, "blessing": "neutral", "text": "I created my own Personal Portfolio Website .Insted of my photo and email I just gave a example image and email.", "repo": "https://github.com/s-akhiltechy/My-Personal-Website", "demo": "https://s-akhiltechy.github.io/My-Personal-Website/"}]...
|
[{"post_id": 39916, "ts": "202 [{"post_id": 39916, "ts": "2026-08-03T07:05:41Z", "hours": 5.135, "text": "Hello, I am currently working on my portfolio website."}]...
|
Title: My StarWebsite by @S-Akhil | Stardance
Dev Title: My StarWebsite by @S-Akhil | Stardance
Devlogs:
Hello, I am currently working on my portfolio website.
Ships:
I created my own Personal Portfolio Website .Insted of my photo and email I just gave a example image and email....
|
1793249418.1924756
|
1793335818.1924756
|
|
27504
|
My very own WebOS by @SilverCanvas | Stardance
|
SilverCanvas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @SilverCanvas | Starda Title: My very own WebOS by @SilverCanvas | Stardance...
|
1792731017.4065208
|
1793335817.4065208
|
|
3186
|
My awesome macropad! by @Madfish | Stardance
|
Madfish
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Madfish | Stardanc Title: My awesome macropad! by @Madfish | Stardance...
|
1792731016.5043757
|
1793335816.5043757
|
|
16154
|
My awesome macropad! by @Mako | Stardance
|
Mako
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Mako | Stardance
|
1792731015.638841
|
1793335815.638841
|
|
25940
|
My very own WebOS by @Just | Stardance
|
Just
|
0
|
9.9
|
0
|
[]
|
[{"post_id": 23299, "ts": "202 [{"post_id": 23299, "ts": "2026-07-06T05:28:14Z", "hours": 0.3789, "text": "Analyzing my code and attempting to debug the close and open window functions."}, {"post_id": 22634, "ts": "2026-07-05T05:54:27Z", "hours": 2.9222, "text": "Found and the syntax issue due to the help from staredance help."}, {"post_id": 21977, "ts": "2026-07-04T06:10:30Z", "hours": 4.0372, "text": "I continued to follow the web os tutorial and spent almost two hours on a syntax error… I still haven’t fixed it :("}, {"post_id": 21345, "ts": "2026-07-03T07:22:04Z", "hours": 1.4, "text": "Started to work on part 2 of the web os tutorial."}, {"post_id": 20535, "ts": "2026-07-02T04:42:42Z", "hours": 0.6428, "text": "I learned how to run html files. (Yay!)"}, {"post_id": 19796, "ts": "2026-07-01T05:47:02Z", "hours": 0.5167, "text": "Started to work on my own web OS!"}]...
|
Title: My very own WebOS by @Just | Stardance
Dev Title: My very own WebOS by @Just | Stardance
Devlogs:
Started to work on my own web OS!
I learned how to run html files. (Yay!)
Started to work on part 2 of the web os tutorial.
I continued to follow the web os tutorial and spent almost two hours on a syntax error… I still haven’t fixed it :(
Found and the syntax issue due to the help from staredance help.
Analyzing my code and attempting to debug the close and open window functions....
|
1792731014.6830738
|
1793335814.6830738
|
|
43074
|
My own site! by @Sifatur | Stardance
|
Sifatur
|
1
|
3.0
|
3
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-06T22:13:14Z", "hours": 3.0, "multiplier": 1.03, "payout": 3, "blessing": "neutral", "text": "I made my own website. The challenging part was to program according to my vision. and iam proud to launch it. If anyone is interest they can test my project.", "repo": "https://github.com/Sifatur1/My-personal-site", "demo": "https://sifatur1.github.io/My-personal-site/"}]...
|
[{"post_id": 42234, "ts": "202 [{"post_id": 42234, "ts": "2026-08-06T21:01:25Z", "hours": 1.0508, "text": "just finished everything"}, {"post_id": 42163, "ts": "2026-08-06T19:25:56Z", "hours": 1.2819, "text": "I completely changed my layout and iam trying to add 3 pages for my info . i need some suggestions from you guys to help me make it leonardo da vinci inspired theme."}, {"post_id": 41294, "ts": "2026-08-05T12:55:08Z", "hours": 0.2628, "text": "Iam Currently working on my first website .Learning new things"}]...
|
Title: My own site! by @Sifatur | Stardance
Devlo Title: My own site! by @Sifatur | Stardance
Devlogs:
Iam Currently working on my first website .Learning new things
I completely changed my layout and iam trying to add 3 pages for my info . i need some suggestions from you guys to help me make it leonardo da vinci inspired theme.
just finished everything
Ships:
I made my own website. The challenging part was to program according to my vision. and iam proud to launch it. If anyone is interest they can test my project....
|
1793249414.4763973
|
1793335814.4763973
|
|
224
|
Untitled by @Niko | Stardance
|
Niko
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Niko | Stardance
|
1792731013.8275313
|
1793335813.8275313
|
|
7955
|
My awesome macropad! by @aditya2pathak_7747 | Star My awesome macropad! by @aditya2pathak_7747 | Stardance...
|
aditya2pathak_7747
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @aditya2pathak_7747 Title: My awesome macropad! by @aditya2pathak_7747 | Stardance...
|
1792731012.9669292
|
1793335812.9669292
|
|
24629
|
My first slack bot! by @dilnurauralova25 | Stardan My first slack bot! by @dilnurauralova25 | Stardance...
|
dilnurauralova25
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @dilnurauralova25 | Title: My first slack bot! by @dilnurauralova25 | Stardance...
|
1792731012.1176302
|
1793335812.1176302
|
|
20854
|
My very own WebOS by @shivam21prateek | Stardance
|
shivam21prateek
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @shivam21prateek | Sta Title: My very own WebOS by @shivam21prateek | Stardance...
|
1792731011.246994
|
1793335811.246994
|
|
43059
|
orbitview by @gautamagrawal5067 | Stardance
|
gautamagrawal5067
|
1
|
11.0
|
64
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-08-07T11:45:11Z", "hours": 11.0, "multiplier": 6.08, "payout": 64, "blessing": "neutral", "text": "I have built a space explorer website called OrbitView that uses NASA APIs to show real-time information regarding asteroids close to our planet Earth. The project contains a modern space-themed design, a glassmorphism interface, responsive design, interactive data cards, and navigation. I wanted to build an educational yet fun space exploration website that would provide information from NASA APIs. The hardest part of the work was implementing the NASA APIs and making sure that the data loading was done successfully in any circumstances. Moreover, the design of the user interface took a lot of time, as it needed to be both beautiful and readable, and fit the different screen sizes. Testing the working of JavaScript modules, as well as the loading of the API data was hard but necessary. The thing that I am most proud of is turning the concept of the project into a working website. All the elements of the website were developed through the process of testing and improving. OrbitView can be tested by opening the website in the modern web browser that is connected to the Internet, since the project uses NASA’s public APIs.", "repo": "https://github.com/gautamagrawal5068-maker/orbitview", "demo": "https://vieworbit.netlify.app"}]...
|
[{"post_id": 42560, "ts": "202 [{"post_id": 42560, "ts": "2026-08-07T11:43:24Z", "hours": 1.9978, "text": "This session brought about the completion of OrbitView. The work that I did included integration of the rest of the pieces together, bug fixing, and improving the overall experience. I was successful in getting the frontend working with the NASA APIs and hence live asteroid data. I also completed the responsive design, made improvements in animations, optimized the performance, and did extensive testing to ensure that all the functionality works perfectly well. The problem: The challenges in this phase of the development were dealing with a couple of bugs such as API request errors, inconsistencies in the UI functionality on various screen sizes, and some JavaScript bugs that affected data rendering. Fixing these bugs involved a lot of testing and several revisions to get everything running. The plan ahead: Now that OrbitView is complete, the way forward is to deploy it by improving the documentation and refining the README file and then deploying this latest build and submitting it as my project for the Hack Club Stardance challenge."}, {"post_id": 41847, "ts": "2026-08-06T10:00:14Z", "hours": 4.61, "text": "In this session, I was able to completely write the CSS code for the whole OrbitView website. Most of the time was dedicated to adjusting the dark-space inspired UI to ensure that all its elements conform to the general futuristic dashboard design style. I made sure that the styling of sidebars, navigation, modals, buttons, information blocks, and responsive design were done to the fullest. I also perfected glassmorphism, animations, spaces, and fonts in order to create an appealing user experience. At this point, with the frontend being completely styled, the website is ready for the functional part of development. The problem: The process of fine-tuning glassmorphism turned out to be quite challenging, as finding the correct balance between transparency, blur effect, and readability involved many trials. In addition, there were some issues with the layout and responsiveness, when some elements overlapped each other or were misaligned at certain screen sizes, and therefore, I had to do several corrections. The plan ahead: After the completion of the CSS code, the next step is the development of api.js file. In it, I am going to implement the NASA NeoWs API to show up-to-date information about asteroids in OrbitView."}, {"post_id": 41085, "ts": "2026-08-05T01:32:19Z", "hours": 3.9389, "text": "This session saw me spend a lot of time setting up the frontend UI architecture. I created style.css to develop the dark space-themed UI where I used glassmorphism to build my sidebars and modals to make it look like a dashboard interface. Also, I began working on the Javascript architecture by splitting it into multiple files (ui.js, api.js, scene.js). The problem: Getting the CSS backdrop-filter (blurring effect) working properly and not making everything too blurry was a pain in the neck. In addition to this, I had some difficulties while trying to test my JS modules because of CORS issues until I figured out that I had to use a Python HTTP server to test them. The plan ahead: Now, the UI is done but it is still an empty shell. Next session, I am going to start working on api.js to get my asteroids from NASA NeoWs API endpoint."}]...
|
Title: orbitview by @gautamagrawal5067 | Stardance Title: orbitview by @gautamagrawal5067 | Stardance
Devlogs:
This session saw me spend a lot of time setting up the frontend UI architecture. I created style.css to develop the dark space-themed UI where I used glassmorphism to build my sidebars and modals to make it look like a dashboard interface. Also, I began working on the Javascript architecture by splitting it into multiple files (ui.js, api.js, scene.js). The problem: Getting the CSS backdrop-filter (blurring effect) working properly and not making everything too blurry was a pain in the neck. In addition to this, I had some difficulties while trying to test my JS modules because of CORS issues until I figured out that I had to use a Python HTTP server to test them. The plan ahead: Now, the UI is done but it is still an empty shell. Next session, I am going to start working on api.js to get my asteroids from NASA NeoWs API endpoint.
In this session, I was able to completely write the CSS code for the whole OrbitView website. Most of the time was dedicated to adjusting the dark-space inspired UI to ensure that all its elements conform to the general futuristic dashboard design style. I made sure that the styling of sidebars, navigation, modals, buttons, information blocks, and responsive design were done to the fullest. I also perfected glassmorphism, animations, spaces, and fonts in order to create an appealing user experience. At this point, with the frontend being completely styled, the website is ready for the functional part of development. The problem: The process of fine-tuning glassmorphism turned out to be quite challenging, as finding the correct balance between transparency, blur effect, and readability involved many trials. In addition, there were some issues with the layout and responsiveness, when some elements overlapped each other or were misaligned at certain screen sizes, and therefore, I had to do several corrections. The plan ahead: After the completion of the CSS code, the next step is the development of api.js file. In it, I am going to implement the NASA NeoWs API to show up-to-date information about asteroids in OrbitView.
This session brought about the completion of OrbitView. The work that I did included integration of the rest of the pieces together, bug fixing, and improving the overall experience. I was successful in getting the frontend working with the NASA APIs and hence live asteroid data. I also completed the responsive design, made improvements in animations, optimized the performance, and did extensive testing to ensure that all the functionality works perfectly well. The problem: The challenges in this phase of the development were dealing with a couple of bugs such as API request errors, inconsistencies in the UI functionality on various screen sizes, and some JavaScript bugs that affected data rendering. Fixing these bugs involved a lot of testing and several revisions to get everything running. The plan ahead: Now that OrbitView is complete, the way forward is to deploy it by improving the documentation and refining the README file and then deploying this latest build and submitting it as my project for the Hack Club Stardance challenge.
Ships:
I have built a space explorer website called OrbitView that uses NASA APIs to show real-time information regarding asteroids close to our planet Earth. The project contains a modern space-themed design, a glassmorphism interface, responsive design, interactive data cards, and navigation. I wanted to build an educational yet fun space exploration website that would provide information from NASA APIs. The hardest part of the work was implementing the NASA APIs and making sure that the data loading was done successfully in any circumstances. Moreover, the design of the user interface took a lot of time, as it needed to be both beautiful and readable, and fit the different screen sizes. Testing the working of JavaScript modules, as well as the loading of the API data was hard but necessary. The thing that I am most proud of is turning the concept of the project into a working website. All the elements of the website were developed through the process of testing and improving. OrbitView can be tested by opening the website in the modern web browser that is connected to the Internet, since the project uses NASA’s public APIs....
|
1793249410.6655953
|
1793335810.6655953
|
|
19479
|
Stardeck by @YodaheWondimu | Stardance
|
YodaheWondimu
|
0
|
31.27
|
0
|
[]
|
[{"post_id": 49980, "ts": "202 [{"post_id": 49980, "ts": "2026-08-19T00:17:58Z", "hours": 11.2794, "text": "Devlog #4: Iterating CAD for component assembly and adding necessary detail With the hardware flow open, I received feedback on my hardware project. A reviewer returned my funding request and advised me to work on adding more detail to my CAD model, since it’s important for actually putting the hardware together and makes CAD your best wingman. Detailed Assembly The detailed assembly would be close to the concept from Devlog #2, but: Instead of blocks for every hardware component, I’ll use open-source .step files as 1:1 reference models. If the model accurately represents the real part and tolerances are accounted for, Onshape fits should represent reality. (Attribution is given in docs/ATTRIBUTIONS.md in my GitHub repository.) Fasteners mattered now, so there was no more pairing of generic screws with generic nuts and calling it a day. The clearance holes from before weren’t as reliable as threaded bosses for mounting purposes, so I had to make replacements where necessary. Hardware Modeling and Fit Raspberry Pi 4B Importing the model for the Raspberry Pi 4B revealed an incorrect assumption. I assumed its 4 mounting holes sat near the corners of the board, but they were actually positioned differently. I adjusted the gap between the mounting rails to allow the Pi to rest and moved the mounting holes to where the Pi could line up on top of them, resulting in a mounting-aware pair of rails that I fastened shortly after. Elecrow RC070 7-inch Touchscreen Display I took the given file from its product page and merged its individual parts into one composite part. After composing, I added mounting holes matching those of the real component. The screen’s width fit perfectly into the top enclosure’s cutout (same width dimension), and with that, I added 0.5mm clearance to all sides of the top enclosure half’s screen cutout in case tolerance reality decides to strike my hardware. Anker Portable Charger/Power Bank This was where it got tricky. There was no available CAD model for the battery pack online, so I had to reverse engineer it myself. Our more realistic battery model had a length of ~153mm, while our placeholder had a length of ~115mm. Since our battery tray was initially modeled to fit snugly around the placeholder model (back when we just needed everything to fit together), our actual battery wasn’t going to fit. Our much more realistic model won over, and I reworked the battery tray with a looser but not as risky fit, centered closer to the side opposite the mounting rails of the inner enclosure’s bottom half. MicroCenter Flash Drive This part required some more of the same principle - reverse engineering - and having the flash drive with me made it easier to create a reference model. Dimensions that are reasonably close to the real thing in Onshape allow us to achieve the same purpose: testing the spacing and enclosure considerations of Stardeck. Challenges Reverse engineering the battery and flash drive was where I learned the most during this revision. I implemented the dimensions that were most relevant to each part’s size and connectivity (since I didn’t need 10/10 looks here) to concoct replicas that came pretty close to the real thing. I also had to design holes that would work with a custom Featurescript for threading. I tried to increase the thickness of certain sides with mounting holes for ThreadCreator’s sake, but what ended up working was switching to a similar Featurescript called BoazThread. What’s complete: Refined key details of the component assembly Related my enclosure hardware to 1:1 hardware models Reverse engineered parts without publicly available CAD models Next up: Refine design further (if required for funding) Receive physical parts Assemble Stardeck IRL Get Stardeck to boot"}, {"post_id": 29786, "ts": "2026-07-16T21:57:29Z", "hours": 8.1269, "text": "Devlog #3 - Printing the Physical Enclosure Good news! This week, I managed to get my 3D printer up and running. Weeks of CAD work finally culminated in a pair of printed enclosure halves. Since I was going for a clamshell design for the first print, I printed both the top and bottom halves to see how they would go together. I knew I was technically doing this to test out tolerances and whatever, but I was secretly excited to be building something outside of Onshape for a change. Settings I mostly used my printer’s default profile, adding tree supports for the floating cantilever sections in the internal mounting rails. They printed cleanly and snapped away easily after fabrication. (Detailed slicer settings are documented separately in docs/printer_settings.md .) The only supports needed were for those mounting rails in the bottom half and the alignment lip on the top half. The results, as you’re about to see, went smoothly. Print Results Fresh off the 3D printer, I had both enclosure halves. The clamshell enclosure worked exactly how I’d hoped, and it seems like it will make disassembly easy enough to fill the internals with electronics (once I have them) and assembly easy enough to not irritate users. The alignment lips kept both halves aligned, and the lip mounting holes worked as a visual aid that told you whether or not each enclosure half was level or not - a perfect circle meant aligned, sliding semicircles meant you had to nudge it a bit. The other visible features - the display mounting area, port cutout, and battery tray - also turned out great. I was surprised to see the top half fit like a glove onto the bottom half first-try. After all, I’ve heard scary stories around an imaginary campfire where one tolerance requires reprinting everything (spooky). Luckily, no such thing happened here. And the mounting holes? They all came out exactly as modeled. The M3 holes on the alignment lips and the M2.5 holes on the display mounts and Pi rails matched the dimensions I designed. Considering how much I’d heard about tolerance problems, seeing everything line up on the first print felt like a small victory. When I Thought I Messed Up So…something happened. I noticed fringing filament that was sticking out of certain surfaces. I thought this would compromise the design’s integrity, and so I searched up the problem. After looking online, I found that this event was known as stringing, where melted filament can ooze from the nozzle during travel and solidify on top of whatever it lands on. I was relieved to figure out that this wasn’t a structural problem, but rather an aesthetic one, which I solved by clipping off any excess filament similar to the tree supports. Summary Printing the enclosure completely changed how the project felt. Up until this point, Stardeck had only existed inside Onshape. Holding both halves in my hands made it feel less like an idea and more like something I was actually going to finish. I don’t have my electronics just yet, but I believe that Hack Club’s funding process will give me the parts that I need to turn my idea into a reality. Speaking of the funding process, I’ve also spent a great deal of time in consecutive work sessions just documenting. I’ve been preparing my JOURNAL.md to showcase day-to-day summaries of progress, screenshotting my Onshape designs, and sharing my fabrication workflow. Steps like these are what allow a project to be considered for hardware grants later, which I need to receive the electronics that’ll make Stardeck a real cyberdeck. The enclosure may only be plastic for now, but it’s the first physical piece of Stardeck. Next comes the stage I’ve been designing around from the beginning: bringing it to life with actual hardware. Next Up: Finish up documentation/design tweaks Submit design for hardware funding Assemble components into the enclosure Craft a booting prototype?"}, {"post_id": 20417, "ts": "2026-07-02T00:37:00Z", "hours": 10.4044, "text": "Devlog #2 - Component Assembly and Design Tuning This week, I was tuning my Stardeck designs to reach feasibility before submitting my design to Stardance for review. I started to test my initial design decisions using Onshape to model the spacing that each part would need, and I used that to finish up a component assembly that reflected how my parts would fit together in the real world. CAD Assembly Space was a critical factor in my cyberdeck because it was what everything inside of my enclosure lived on. Furthermore, my enclosure design evolved often to account for unanticipated constraints. A few of my enclosure features for Stardeck surprised me as I never even knew that I needed them at first. Clamshell Design: Remember how in the first devlog, I was considering using a rectangular prism with a carved-out back to house all the internal components? I found out very quickly that this would still make for a hard assembly once more than two parts came in. A clamshell design - top half, bottom half - would allow me to make the most of the space given because it would allow me to actually reach many parts of the internals. Alignment Lips: This took me a long time to conceptualize after hearing about these for the first time, but it became easy once I thought of a shoebox. The top of any shoebox fits on the bottom half and rests there - not because it’s screwed in place, but because the top half sort of wraps around the bottom half. These made the clamshell more robust as the “shoebox method” promised a safer screwdriver assembly as well. Mounting Rails: Placing the Raspberry Pi, which would be the basis of Stardeck’s computing subsystem, in the exact middle of the enclosure meant that other components - battery, screen, flash drive, etc - could reach it easily. However, it can’t just levitate, so it uses mounting rails to keep it up. The rails also come with holes for the Pi to be mounted onto for added security. Port Cutout: I felt so relieved after realizing that I needed this before shipping off all my CAD files to display on GitHub. The reason why was because it’s the hole in the enclosure that allows external cables to access the Pi’s USB ports. This makes essential functions such as swapping flash drives and connecting keyboards much easier. Overall, it’s a small design feature that makes assembly and maintenance much easier. System Architecture From the last devlog, we already knew how each component would connect to one another in practice. However, I found that for this iteration, the system could be modeled effectively at the subsystem level without a full PCB design or detailed electrical schematic. To follow, I created a System Architecture diagram to demonstrate how the parts of Stardeck interact with each other. After solving the electrical problem, I managed - with several days of me modeling components to depict and assemble - to solve the mechanical problem instead. Both were closely related to each other, which made for a lot of work when planning port maps, looking at diagrams of the port locations on a Raspberry Pi, finding components for the BOM that I want for my build, and so on. Summary I learned a lot about hardware selection, using Onshape to work around physical constraints, and building prototypes with future me in mind. I’m confident this design is ready to be submitted at its current state to Stardance. It’s simple and has just enough functionality without going overboard for a minimal viable product. With funding help from them, I’ll have the parts necessary to go from designing a prototype to fabricating a prototype. Exploded View Part Numbers Top Enclosure Bottom Enclosure Raspberry Pi Battery Pack Screen Flash Drive Alignment Lip Battery Tray Mounting Rails Next up: Print enclosure Assemble real-world components Iterate on the design (if met with an obstacle during fabrication)"}, {"post_id": 10294, "ts": "2026-06-16T22:41:46Z", "hours": 1.4614, "text": "Devlog #1 — Initial Architecture and Packaging Study 🎉What I did this week: Defined system architecture for the cyberdeck (power, computer, input, output) Selected Raspberry Pi 4B as the main controller Created an initial system schematic/diagram to model subsystem interactions Performed a first packaging study in Onshape Verified that all core components fit within the proposed enclosure concept 🎚️Initial Schematic Note: This is a system-level schematic used to understand how components in the cyberdeck interact with each other, paired with a packaging study to estimate spatial requirements. This is an early-stage design exploration. The goal of this stage was to answer the question: What parts will Stardeck consist of, and how do they interact with one another? System Overview The cyberdeck is composed of four primary subsystems: Power Computer Input Output System Description Power subsystem: Provides energy to all other subsystems. This is the foundation of the system. Computer subsystem: The Raspberry Pi acts as the central controller, managing both input and output operations. Input subsystem: The keyboard is the primary input method. Additional input devices may be added later through USB expansion. Output subsystem: The display serves as the primary output device, showing system activity and user interface. 🪛Design Direction After reviewing publicly available cyberdeck designs, I decided on a compact tablet-like form factor. The current design consists of: A front-mounted display embedded into the case A Raspberry Pi and power bank mounted inside the enclosure behind the screen This configuration is chosen to prioritize reaching a functional MVP quickly. Future iterations may introduce improvements such as a rotating or laptop-style hinged display. 🔬Packaging Study Findings All dimensions are approximate and based on early-stage placeholder modeling. Units are in millimeters (length x width x height). Case: 230 x 160 x 40 Includes a cutout on the front face for the embedded display. Screen (initial placeholder): 200 x 120 x 15 Screen (final target, 7 inch): 155 x 87 x 15 Raspberry Pi 4B: 90 x 60 x 25 Slightly oversized in the model to account for cables, connectors, and mounting tolerance. Power bank: 110 x 70 x 20 Based on a typical 10,000 mAh USB battery. Final dimensions may change depending on selected model. Key Finding: The initial screen model was too large. The original estimate produced a diagonal of approximately 233 mm (about 9.2 inches), which did not match the intended 7 inch display size. After correction, the 155 x 87 mm screen model aligns with a 7 inch diagonal and is now used as the baseline for enclosure design. Current Conclusion The current enclosure design appears sufficient to house all core components based on the current placeholder assembly in Onshape. Remaining uncertainties primarily involve final battery selection and cable routing. 👣Next Steps Finalize selection of power bank Choose exact display model Begin KiCad schematic for wiring and power design Refine enclosure geometry in Onshape based on finalized components God bless you, Yodahe"}]...
|
Title: Stardeck by @YodaheWondimu | Stardance
Dev Title: Stardeck by @YodaheWondimu | Stardance
Devlogs:
Devlog #1 — Initial Architecture and Packaging Study 🎉What I did this week: Defined system architecture for the cyberdeck (power, computer, input, output) Selected Raspberry Pi 4B as the main controller Created an initial system schematic/diagram to model subsystem interactions Performed a first packaging study in Onshape Verified that all core components fit within the proposed enclosure concept 🎚️Initial Schematic Note: This is a system-level schematic used to understand how components in the cyberdeck interact with each other, paired with a packaging study to estimate spatial requirements. This is an early-stage design exploration. The goal of this stage was to answer the question: What parts will Stardeck consist of, and how do they interact with one another? System Overview The cyberdeck is composed of four primary subsystems: Power Computer Input Output System Description Power subsystem: Provides energy to all other subsystems. This is the foundation of the system. Computer subsystem: The Raspberry Pi acts as the central controller, managing both input and output operations. Input subsystem: The keyboard is the primary input method. Additional input devices may be added later through USB expansion. Output subsystem: The display serves as the primary output device, showing system activity and user interface. 🪛Design Direction After reviewing publicly available cyberdeck designs, I decided on a compact tablet-like form factor. The current design consists of: A front-mounted display embedded into the case A Raspberry Pi and power bank mounted inside the enclosure behind the screen This configuration is chosen to prioritize reaching a functional MVP quickly. Future iterations may introduce improvements such as a rotating or laptop-style hinged display. 🔬Packaging Study Findings All dimensions are approximate and based on early-stage placeholder modeling. Units are in millimeters (length x width x height). Case: 230 x 160 x 40 Includes a cutout on the front face for the embedded display. Screen (initial placeholder): 200 x 120 x 15 Screen (final target, 7 inch): 155 x 87 x 15 Raspberry Pi 4B: 90 x 60 x 25 Slightly oversized in the model to account for cables, connectors, and mounting tolerance. Power bank: 110 x 70 x 20 Based on a typical 10,000 mAh USB battery. Final dimensions may change depending on selected model. Key Finding: The initial screen model was too large. The original estimate produced a diagonal of approximately 233 mm (about 9.2 inches), which did not match the intended 7 inch display size. After correction, the 155 x 87 mm screen model aligns with a 7 inch diagonal and is now used as the baseline for enclosure design. Current Conclusion The current enclosure design appears sufficient to house all core components based on the current placeholder assembly in Onshape. Remaining uncertainties primarily involve final battery selection and cable routing. 👣Next Steps Finalize selection of power bank Choose exact display model Begin KiCad schematic for wiring and power design Refine enclosure geometry in Onshape based on finalized components God bless you, Yodahe
Devlog #2 - Component Assembly and Design Tuning This week, I was tuning my Stardeck designs to reach feasibility before submitting my design to Stardance for review. I started to test my initial design decisions using Onshape to model the spacing that each part would need, and I used that to finish up a component assembly that reflected how my parts would fit together in the real world. CAD Assembly Space was a critical factor in my cyberdeck because it was what everything inside of my enclosure lived on. Furthermore, my enclosure design evolved often to account for unanticipated constraints. A few of my enclosure features for Stardeck surprised me as I never even knew that I needed them at first. Clamshell Design: Remember how in the first devlog, I was considering using a rectangular prism with a carved-out back to house all the internal components? I found out very quickly that this would still make for a hard assembly once more than two parts came in. A clamshell design - top half, bottom half - would allow me to make the most of the space given because it would allow me to actually reach many parts of the internals. Alignment Lips: This took me a long time to conceptualize after hearing about these for the first time, but it became easy once I thought of a shoebox. The top of any shoebox fits on the bottom half and rests there - not because it’s screwed in place, but because the top half sort of wraps around the bottom half. These made the clamshell more robust as the “shoebox method” promised a safer screwdriver assembly as well. Mounting Rails: Placing the Raspberry Pi, which would be the basis of Stardeck’s computing subsystem, in the exact middle of the enclosure meant that other components - battery, screen, flash drive, etc - could reach it easily. However, it can’t just levitate, so it uses mounting rails to keep it up. The rails also come with holes for the Pi to be mounted onto for added security. Port Cutout: I felt so relieved after realizing that I needed this before shipping off all my CAD files to display on GitHub. The reason why was because it’s the hole in the enclosure that allows external cables to access the Pi’s USB ports. This makes essential functions such as swapping flash drives and connecting keyboards much easier. Overall, it’s a small design feature that makes assembly and maintenance much easier. System Architecture From the last devlog, we already knew how each component would connect to one another in practice. However, I found that for this iteration, the system could be modeled effectively at the subsystem level without a full PCB design or detailed electrical schematic. To follow, I created a System Architecture diagram to demonstrate how the parts of Stardeck interact with each other. After solving the electrical problem, I managed - with several days of me modeling components to depict and assemble - to solve the mechanical problem instead. Both were closely related to each other, which made for a lot of work when planning port maps, looking at diagrams of the port locations on a Raspberry Pi, finding components for the BOM that I want for my build, and so on. Summary I learned a lot about hardware selection, using Onshape to work around physical constraints, and building prototypes with future me in mind. I’m confident this design is ready to be submitted at its current state to Stardance. It’s simple and has just enough functionality without going overboard for a minimal viable product. With funding help from them, I’ll have the parts necessary to go from designing a prototype to fabricating a prototype. Exploded View Part Numbers Top Enclosure Bottom Enclosure Raspberry Pi Battery Pack Screen Flash Drive Alignment Lip Battery Tray Mounting Rails Next up: Print enclosure Assemble real-world components Iterate on the design (if met with an obstacle during fabrication)
Devlog #3 - Printing the Physical Enclosure Good news! This week, I managed to get my 3D printer up and running. Weeks of CAD work finally culminated in a pair of printed enclosure halves. Since I was going for a clamshell design for the first print, I printed both the top and bottom halves to see how they would go together. I knew I was technically doing this to test out tolerances and whatever, but I was secretly excited to be building something outside of Onshape for a change. Settings I mostly used my printer’s default profile, adding tree supports for the floating cantilever sections in the internal mounting rails. They printed cleanly and snapped away easily after fabrication. (Detailed slicer settings are documented separately in docs/printer_settings.md .) The only supports needed were for those mounting rails in the bottom half and the alignment lip on the top half. The results, as you’re about to see, went smoothly. Print Results Fresh off the 3D printer, I had both enclosure halves. The clamshell enclosure worked exactly how I’d hoped, and it seems like it will make disassembly easy enough to fill the internals with electronics (once I have them) and assembly easy enough to not irritate users. The alignment lips kept both halves aligned, and the lip mounting holes worked as a visual aid that told you whether or not each enclosure half was level or not - a perfect circle meant aligned, sliding semicircles meant you had to nudge it a bit. The other visible features - the display mounting area, port cutout, and battery tray - also turned out great. I was surprised to see the top half fit like a glove onto the bottom half first-try. After all, I’ve heard scary stories around an imaginary campfire where one tolerance requires reprinting everything (spooky). Luckily, no such thing happened here. And the mounting holes? They all came out exactly as modeled. The M3 holes on the alignment lips and the M2.5 holes on the display mounts and Pi rails matched the dimensions I designed. Considering how much I’d heard about tolerance problems, seeing everything line up on the first print felt like a small victory. When I Thought I Messed Up So…something happened. I noticed fringing filament that was sticking out of certain surfaces. I thought this would compromise the design’s integrity, and so I searched up the problem. After looking online, I found that this event was known as stringing, where melted filament can ooze from the nozzle during travel and solidify on top of whatever it lands on. I was relieved to figure out that this wasn’t a structural problem, but rather an aesthetic one, which I solved by clipping off any excess filament similar to the tree supports. Summary Printing the enclosure completely changed how the project felt. Up until this point, Stardeck had only existed inside Onshape. Holding both halves in my hands made it feel less like an idea and more like something I was actually going to finish. I don’t have my electronics just yet, but I believe that Hack Club’s funding process will give me the parts that I need to turn my idea into a reality. Speaking of the funding process, I’ve also spent a great deal of time in consecutive work sessions just documenting. I’ve been preparing my JOURNAL.md to showcase day-to-day summaries of progress, screenshotting my Onshape designs, and sharing my fabrication workflow. Steps like these are what allow a project to be considered for hardware grants later, which I need to receive the electronics that’ll make Stardeck a real cyberdeck. The enclosure may only be plastic for now, but it’s the first physical piece of Stardeck. Next comes the stage I’ve been designing around from the beginning: bringing it to life with actual hardware. Next Up: Finish up documentation/design tweaks Submit design for hardware funding Assemble components into the enclosure Craft a booting prototype?
Devlog #4: Iterating CAD for component assembly and adding necessary detail With the hardware flow open, I received feedback on my hardware project. A reviewer returned my funding request and advised me to work on adding more detail to my CAD model, since it’s important for actually putting the hardware together and makes CAD your best wingman. Detailed Assembly The detailed assembly would be close to the concept from Devlog #2, but: Instead of blocks for every hardware component, I’ll use open-source .step files as 1:1 reference models. If the model accurately represents the real part and tolerances are accounted for, Onshape fits should represent reality. (Attribution is given in docs/ATTRIBUTIONS.md in my GitHub repository.) Fasteners mattered now, so there was no more pairing of generic screws with generic nuts and calling it a day. The clearance holes from before weren’t as reliable as threaded bosses for mounting purposes, so I had to make replacements where necessary. Hardware Modeling and Fit Raspberry Pi 4B Importing the model for the Raspberry Pi 4B revealed an incorrect assumption. I assumed its 4 mounting holes sat near the corners of the board, but they were actually positioned differently. I adjusted the gap between the mounting rails to allow the Pi to rest and moved the mounting holes to where the Pi could line up on top of them, resulting in a mounting-aware pair of rails that I fastened shortly after. Elecrow RC070 7-inch Touchscreen Display I took the given file from its product page and merged its individual parts into one composite part. After composing, I added mounting holes matching those of the real component. The screen’s width fit perfectly into the top enclosure’s cutout (same width dimension), and with that, I added 0.5mm clearance to all sides of the top enclosure half’s screen cutout in case tolerance reality decides to strike my hardware. Anker Portable Charger/Power Bank This was where it got tricky. There was no available CAD model for the battery pack online, so I had to reverse engineer it myself. Our more realistic battery model had a length of ~153mm, while our placeholder had a length of ~115mm. Since our battery tray was initially modeled to fit snugly around the placeholder model (back when we just needed everything to fit together), our actual battery wasn’t going to fit. Our much more realistic model won over, and I reworked the battery tray with a looser but not as risky fit, centered closer to the side opposite the mounting rails of the inner enclosure’s bottom half. MicroCenter Flash Drive This part required some more of the same principle - reverse engineering - and having the flash drive with me made it easier to create a reference model. Dimensions that are reasonably close to the real thing in Onshape allow us to achieve the same purpose: testing the spacing and enclosure considerations of Stardeck. Challenges Reverse engineering the battery and flash drive was where I learned the most during this revision. I implemented the dimensions that were most relevant to each part’s size and connectivity (since I didn’t need 10/10 looks here) to concoct replicas that came pretty close to the real thing. I also had to design holes that would work with a custom Featurescript for threading. I tried to increase the thickness of certain sides with mounting holes for ThreadCreator’s sake, but what ended up working was switching to a similar Featurescript called BoazThread. What’s complete: Refined key details of the component assembly Related my enclosure hardware to 1:1 hardware models Reverse engineered parts without publicly available CAD models Next up: Refine design further (if required for funding) Receive physical parts Assemble Stardeck IRL Get Stardeck to boot...
|
1792731010.1167269
|
1793335810.1167269
|
|
25529
|
My very own WebOS by @jose_gurgel | Stardance
|
jose_gurgel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @jose_gurgel | Stardan Title: My very own WebOS by @jose_gurgel | Stardance...
|
1792731009.285552
|
1793335809.285552
|
|
16820
|
Orbital Mechanics Visualizer by @duaesakinahasan | Orbital Mechanics Visualizer by @duaesakinahasan | Stardance...
|
duaesakinahasan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Orbital Mechanics Visualizer by @duaesakina Title: Orbital Mechanics Visualizer by @duaesakinahasan | Stardance...
|
1792731008.4499586
|
1793335808.4499586
|
|
16260
|
My awesome macropad! by @Tobgamer | Stardance
|
Tobgamer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Tobgamer | Stardan Title: My awesome macropad! by @Tobgamer | Stardance...
|
1792731007.6003668
|
1793335807.6003668
|
|
36480
|
Chengine by @mkksh | Stardance
|
mkksh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Chengine by @mkksh | Stardance
|
1792731006.7413445
|
1793335806.7413445
|
|
7044
|
Solarwake by @subhas | Stardance
|
subhas
|
0
|
9.45
|
0
|
[]
|
[{"post_id": 5466, "ts": "2026 [{"post_id": 5466, "ts": "2026-06-09T08:14:25Z", "hours": 2.8053, "text": "Solarwake Devlog: 03 Today was a big day for Solarwake, I had to redo the entire css file to fix the duplication of rule sets. Today I got the base “game” part of the application- but believe I need to change a ton of things. From UI to the way the game feels- it’s clear that Solarwake is no where near done. The biggest upgrade is actually building the “game part” but it’s not good enough for release nor demo. What changed Built the first real gameplay Each mission with different gameplay Built the main game UI Next steps Making it feel more smooth Changing the UI Add scoring, risk, and outcomes."}, {"post_id": 4183, "ts": "2026-06-07T12:26:11Z", "hours": 4.2494, "text": "Solarwake Devlog: 02 Today I focused on redeveloping and restructuring the entire Solarwake web app. I decided that the original approach felt too boring and non user-friendly. This update was about finding the right feel for Solarwake, which is calm, smooth, and interactive. I switched the mission previews to use real 3d using three.js & improved the overall feel through animations, blurs, dropshadow, floating effects, and material. The biggest upgrade was the mission selection screen, which can be visible after clicking “Play Mission”, the app now transitions into the mission control view where the user can select what mission type they want to launch. What changed Reworked the main menu layout Added a cinematic animated space background Added floating mascot Integrated the Solarwake logo Added About and Tutorial buttons Built the Play Mission transition Added mission cards and mission descriptions Added Three.js 3D previews(interactive) Improved the colors, lighting and smoothness Next steps Add real gameplay Connect space weather data into the system Add scoring, risk, and outcomes."}, {"post_id": 3993, "ts": "2026-06-07T04:13:08Z", "hours": 2.3908, "text": "Solarwake Devlog 🌌🛰️☁️ (been doing them on GitHub so this is my first devlog) What is Solarwake? ⤷ A space weather mission control simulator where you can choose a mission, and adjust weather conditions or actions to complete the mission succesfully. Spaceweather is something that is fairly mysterious and creating a mission control to simulate the enviorment in space could help people understand space better. What I built. ⤷ Today I built the first working prototype of the Solarwake dashboard. It has a mission selector, placeholder mission risk values, live Kp data from NOAA, and more. I also implemented a small astronaut dog mascot. My realization. ⤷ After attempting to build a space weater mission control simulator- I realized that it feels too “normal” and not something a user would like. I came to the realization of making it feel more like a room full of screens, live systems, decisions that can affect the mission in real time, and a actual 3d viewer of what’s going on. The change. ⤷ So I am changing the direction of this entire web app. The next devlog + version will have a first screen where users choose what mission to run, and pick what they want to be(a astronaut, ISS mission capsule, etc). After clicking play, they will be able to control what happens to their selection through a full mossion control simulator. The main screen shows a actual astronaut or spacecraft in space and the control panel lets users change data like power mode, shielding, communications etc. 🎯 THE GOAL: Make the app feel more interactive & visual. Currently it feels boring and doesn’t “hit”, users should be able to learn how space weather actually affects a mission in real time through their mission controlling strenghts. 🔮 The future. ⤷ Now I am going to build Solarwake with 2 phases: A mission select screen where users can pick what they want to control A mission control screen where their decisions make a impact visually. This should make Solarwake feel much more like a game simulator instead of a dashboard."}]...
|
Title: Solarwake by @subhas | Stardance
Devlogs:
Title: Solarwake by @subhas | Stardance
Devlogs:
Solarwake Devlog 🌌🛰️☁️ (been doing them on GitHub so this is my first devlog) What is Solarwake? ⤷ A space weather mission control simulator where you can choose a mission, and adjust weather conditions or actions to complete the mission succesfully. Spaceweather is something that is fairly mysterious and creating a mission control to simulate the enviorment in space could help people understand space better. What I built. ⤷ Today I built the first working prototype of the Solarwake dashboard. It has a mission selector, placeholder mission risk values, live Kp data from NOAA, and more. I also implemented a small astronaut dog mascot. My realization. ⤷ After attempting to build a space weater mission control simulator- I realized that it feels too “normal” and not something a user would like. I came to the realization of making it feel more like a room full of screens, live systems, decisions that can affect the mission in real time, and a actual 3d viewer of what’s going on. The change. ⤷ So I am changing the direction of this entire web app. The next devlog + version will have a first screen where users choose what mission to run, and pick what they want to be(a astronaut, ISS mission capsule, etc). After clicking play, they will be able to control what happens to their selection through a full mossion control simulator. The main screen shows a actual astronaut or spacecraft in space and the control panel lets users change data like power mode, shielding, communications etc. 🎯 THE GOAL: Make the app feel more interactive & visual. Currently it feels boring and doesn’t “hit”, users should be able to learn how space weather actually affects a mission in real time through their mission controlling strenghts. 🔮 The future. ⤷ Now I am going to build Solarwake with 2 phases: A mission select screen where users can pick what they want to control A mission control screen where their decisions make a impact visually. This should make Solarwake feel much more like a game simulator instead of a dashboard.
Solarwake Devlog: 02 Today I focused on redeveloping and restructuring the entire Solarwake web app. I decided that the original approach felt too boring and non user-friendly. This update was about finding the right feel for Solarwake, which is calm, smooth, and interactive. I switched the mission previews to use real 3d using three.js & improved the overall feel through animations, blurs, dropshadow, floating effects, and material. The biggest upgrade was the mission selection screen, which can be visible after clicking “Play Mission”, the app now transitions into the mission control view where the user can select what mission type they want to launch. What changed Reworked the main menu layout Added a cinematic animated space background Added floating mascot Integrated the Solarwake logo Added About and Tutorial buttons Built the Play Mission transition Added mission cards and mission descriptions Added Three.js 3D previews(interactive) Improved the colors, lighting and smoothness Next steps Add real gameplay Connect space weather data into the system Add scoring, risk, and outcomes.
Solarwake Devlog: 03 Today was a big day for Solarwake, I had to redo the entire css file to fix the duplication of rule sets. Today I got the base “game” part of the application- but believe I need to change a ton of things. From UI to the way the game feels- it’s clear that Solarwake is no where near done. The biggest upgrade is actually building the “game part” but it’s not good enough for release nor demo. What changed Built the first real gameplay Each mission with different gameplay Built the main game UI Next steps Making it feel more smooth Changing the UI Add scoring, risk, and outcomes....
|
1792731005.8805296
|
1793335805.8805296
|
|
18554
|
My very own WebOS by @tfry1579 | Stardance
|
tfry1579
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @tfry1579 | Stardance
|
1792731005.0071068
|
1793335805.0071068
|