Hardest part of the scheduled submissions in Pilot: the server has to hold a student's draft for the first time.
And each send is isolated so one failure can't break the rest.
Check out our build log: https://t.co/ELmYH2iDeX
@korabytes @kora#BuildInPublic#Kora#Korabytes
Being a front-end developer or UI/UX designer is also about expression, studying how design patterns, and what people see (UI) and feel (UX) can affect their attitude toward your product.
I want final year students to feel safe, energy and a willingness to fly.
Pilot's diff view doesn't compare by position.
Every paragraph gets a permanent ID. The diff matches by ID first, then word by word inside each block.
Insert a paragraph? Nothing else lights up red or green.
@korabytescu@thekorahq#Korabytes#BuildInPublicChallenge#kora
Guys, Team Pilot needs your help to get the right name for the AI assist on Pilot. ๐
I came up with KUMO meaning cloud in Japanese.
Fortune on the other hand came up with COMPASS.
And I think compass is common๐.
@korabytescu@thekorahq#Kora#Korabytes#BuildInPublicChallenge
It's very possible for you and your supervisor to chat in your FYP's context.
Easily reference a block in your project or jump to blocks for review.
- With Pilot, you're in the cockpit, you're in control.
@korabytescu@thekorahq#Korabytes#kora#BuildInPublicChallenge#Pilot
A glimpse into the diff views in Pilot.
Supervisors shouldn't have to re-read a whole project to find what changed.
With diff view that's possible.
Still working on the UI๐
Build Log: https://t.co/XHcXpqBsgh
@korabytescu@thekorahq#kora#korabyte#BuildInPublicChallenge
Hard part: my first trail added a point on every scroll event, in a fixed overlay. It lagged and drifted off the plane. Fix: precompute 240 points along the path and draw only up to the plane's position. Same function, no desync.
When your landing page deserves some awwwards ๐- TEAM PILOT!!!
A paper plane flies down the page as you scroll, with two trails.
Technical breakdown below ๐
Build log: https://t.co/XHcXpqBsgh
@korabytescu@thekorahq#BuildInPublicChallenge#kora#korabytes
My friend and I (Team pilot) registered for the KoraBytes "BIP" hackathon with Pilot, a final-year project management system designed to sync supervisors and students.
Stay tuned!
Build Log: https://t.co/rHgJeqMXWb
@thekorahq@korabytescu#korabytes#kora#BuildInPublicChallenge
How it works: The plane's position is a function of scroll progress: GSAP ScrollTrigger scrubs a value from 0 to 1 and I compute where the plane is each frame. Trails follow that same curve, ending at the plane. Scroll up, they retract.
Hard part: my first trail added a point on every scroll event, in a fixed overlay. It lagged and drifted off the plane, and the page was also slow.
Fix: precompute 240 points along the path and draw only up to the plane's position. Same function, no desync.
How it works: The plane's position is a function of scroll progress: GSAP ScrollTrigger scrubs a value from 0 to 1 and I compute where the plane is each frame.
Trails follow that same curve, ending at the plane. Scroll up, they retract.
Hard part: my first trail added a point on every scroll event, in a fixed overlay. It lagged and drifted off the plane.
Fix: precompute 240 points along the path and draw only up to the plane's position. Same function, no desync.
The plane's position is a function of scroll progress: GSAP ScrollTrigger scrubs a value from 0 to 1 and I compute where the plane is each frame.
Trails follow that same curve, ending at the plane. Scroll up, they retract.
Hard part: my first trail added a point on every scroll event, in a fixed overlay. It lagged and drifted off the plane.
Fix: precompute 240 points along the path and draw only up to the plane's position. Same function, no desync.
@korabytes @kora#KorabytesBuildInPublic
The plane's position is a function of scroll progress: GSAP ScrollTrigger scrubs a value from 0 to 1 and I compute where the plane is each frame.
Trails follow that same curve, ending at the plane. Scroll up, they retract.
@korabytes @kora#KorabytesBuildInPublic
The plane must stay on screen the whole way down while swooping side to side. Its height is tied to scroll position and viewport height. Fonts and resizes change page height, so a ResizeObserver rebuilds it.