Eucatastrophe

Fixed a small but noticeable error, where navigating back to a previously loaded video page breaks the videos.

Did a lot on the photography tab today!

One notable thing is adding support for videos, and the lazy loading for videos. :D

fixed some relative/absolute file path things (like /image.png vs image.png). So /image.png means it's user.github.com/image.png, even tho you could be at user.github.com/mysite. so u gotta use image.png without the slash!

idk why neocities isn't updating lol

also, I don't know why there are 9 minutes logged. yay for 30 hours though!

made the file structure a bit cleaner, and also logged that it is (should be) synced with the neocities version.

I did something pretty cool!

• Added an optimized pagination, so stuff only loads when I get to that page.

• Also, pages accessible by URL query (JS handled). However, when tabbing through the photobook, the JS just updates the HTML without refreshing the browser (updating ?page= using window.history API instead)

• so this way it's easy to dev while seeing the pages and also easy to load!! yippee

HEYYY guys so this site is going slightly slowly at the moment but I'm gonna fix up the docs and then push it. The docs are contested. idk if I want to keep them, but regardless it was definitely a learning experience and good to figure out !!!

I had to add an image so here

I added photograph page :)

why hello people. I added bloggy page and photograph page :3
css is fun [muffled 3-year-experience of screaming] jk haha.

Made the site, and also a music player (by changing the style of spotify's playlist embed)

Guys I'll figure out the hooks rule breaking soon. It's fine. everything's fine! A certain anxiety disorder is definitely not clutching at me right now. I'm going to go to bed. badbye

Modularized a bit, added a submit button so that you can actually submit a test

2 weeks into school and I've somehow gotten hold of the dreaded burnout haha. Also, I feel like my code is really. not optimal. I'm trying to make everything more modular ;v; Also why is it SO HARD TO FIND RESOURCES!!! I dont want to ask chatgpt

Sorry for not updating, I've been so busy since junior year has started and my time management is really bad ;V; I'm trying my best to free up some time for dev.

Personal mantra: today I will sleep at a reasonable time...
What I did: uh, I don't really remember, something about the quiz page. I plan (tomorrow?) to add a submit button, a clock, freshen up the UI.

I'm setting a personal deadline of 8/30 to do that, so this project can get a move on.

OK it works. I mean, it doesn't build but the docs processing works and I've figured out relevant errors to the past couple devlogs. I'm happy to report that we don't live in a simulation !

ok I think I figured it out. I need a nap

basically two files that I thought were important aren't even part of the document generating workflow. only docs.ts and layout.tsx were actually generating the docs. the other two (parsing frontmatter & adding remark for github-flavored-markdown) weren't even doing anything. hence me spamming whatever into it and it still working.

Hi it's been 2 hours. I am losing my mind.
what in tar nation

I fix bug :pf:

UHHH ok there was a bug on the bee movie question but. I fixed it :pf:

So in the past couple of days:

• modularized the program (which took a while)
• battled with ts-check,
• checked out SVG filters
• html DOM bugs
• general game-content
• figured out the importance of having a debugging function to skip parts of the game ;v;

YAY! i'll ship this now
Attached is: radio buttons that are disguised as marbles. or vice versa.

Did three main things!
1) decided to make it a physics game: Matched up matter.js physics with DOM elements
2) typed in game content and structured the thing
3) spent the last hour fixing hitboxes and modularizing the entire program

(extra) played around with HTML <svg> filters lmao. filters are great.

hilo, I added a safety check against jars without enough sand (in case someone accidentally double clicks after making a jar). Also, more instructions as per review notes :)

Hello, 'tis what I did:

• make 2D circles
• make 2D circles collision work
• suffer
• suffer
• make 2D circles physics work
• make 3D circles work like 2D circles [AI help]
• suffer some more (cursor drag)
• html and math

added settings :3

Hello hello! I made this after the failed glitterjar.js. I still think sand physics is cool.

simple upcoming stuff:
- sand colors
- sand sizes
- sand eraser

later:
- maybe dragging to an xy coordinate (dont cover anyone elses sand)
- better loading

you should buy custom css (if you want)

Soooo Nextra was really hard to integrate into a project. Contentlayer didn't work. Basically, a surprising lot of these libraries seem to be made for websites that are JUST documentation.

So I made a minimal MDX -> html thing using react-mdx-remote & related libraries! Also learned about hooks and did troubleshooting. Anyways, docs looks a lot less broken now lol, and i will now melt on the floor (why is there not a working library for this)

The. Docs work. Barely. asdxvfgds

Hey I'm back again! Apparently the build error was caused by my useSearchParams() part not having a <Suspense> boundary for loading. Search params as the ?practice_id=102932094394 stuff in a website url.

Anyway gonna merge with main so that more pages work :)
I'll prolly ship when I get the docs working too

Smallish updates!

① No more /pages !!!! now using /app.

② Some funky react-dom updates and updating the packages
③ use client (I have yet to really figure this one out)
④ other small front-end things
⑤ Tried to set up nextra (for docs.) not yet, I guess.

We are at 100 commits lol. I don't really have any site image updates, but here's a clippy

HELLO EVERYNYAN.

I have updated the site landing page, and the about page, and the privacy policy, all that frontend jazz ・ﾟ✧・ﾟ✧

been working on making practice test UI :)
Also, next.js migration is done & all the folder stuff has been fixed. it took a while.

Hopefully vercel won't die on me now haha

Next.js migration is almost complete! There are a few bugs with algolia.

Also, added a lot of the backend & frontend configuration for generating practice tests. (The actual test UI isn't there yet)

I barely know what I'm doing with backend so, had to ask GPT about that haha. Idk what image to upload so, here's a good representation of my three braincells trying to work this out

Features added in the last 10 hours:
- searching & algolia config
- dependency issue but it's okay, I'll update react with algoliav4 later
- entire front page

Suffering added in the last 10 hours:
- tailwind
- migrating to next.js (nextra) after gatsby dying and deciding to not use astro,
because of how much docusaurus' figma is fighting a civil war against tailwindcss
- eslint hell
- wakatime isn't even recordin gmy time anymore.?? or it's not showing up. idk man

Innn the last 4 hours or so I made another repository! This one is for storing database qusetions. I also used a bunch of python libraries to read questions from google drive files. Yippee! (These questions are not pirated, they are from the scioly wiki)

Also used Open AI API to generate explanations for questions. Currently using Algolia search for generating questions

currently collecting my team of python libraries to try and do webscraping and pdf reading

Hi. Now when you log in, it actually creates your account! Wow! Also auth persistence across reloads. That's about it

Oh no, I forgot to devlog.

In the past like 13 hours, I checks github commits added functionality stuff, and filler pages for other concepts. I also did a lot of mapping out on paper for the database structure (I've never done this kinda stuff before, kind of scary! haha.)

--- Added stuff ---
0. Overthinking about a certain UI component of multiple choice. idk I was stuck. it took too long but, ah well, it looks a lot better now!
1. A sidebar, with conceptual stuff like practices and tests
2. Dashboard layout! This included: A bunch more react components, a bit of art, some funny widgets that use either JSON or an API
3. Learning to use Firebase (and more React stuff like effects states) and updating that typescript stuff accordingly. That kinda took a while.
4. [not really in the 13 hours, but] Overthinking about the structure of how I'm going to organize things in firebase. I think it works, mapping it out on paper makes me feel better
5. Added like 1 page of content and made the other 2 more... contenty..

Honestly, almost everything in this project is quite new to me (swizzling stuff, React.js, using Firebase, and drawing out how to structure a website). So I'm taking it slow and learning step by step, hence how it takes a while. I think the gradual exposure to new stuff and the trial-and-error helps with my perfectionistic tendencies a bit.

Wow 11 hours. I did quite a bit of stuff, all geared around site setup & basic layout

• (sorta) learned React.js

• set up docusaurus

• set up tailwind

• swizzled the sidebar a little bit

• drew some stuff for the homepage!

• added topics!

• (I am deciding on the dashboard, as well as login features)