Welcome, weary internet traveller. You’ve stumbled onto a great slice of the internet.

Keyframes is a creative community. Share your #wip, get #feedback, find inspiration, and chat with people who make things. It is a bunker from the rest of the garbage internet. No popularity contests here. No circle jerks. No regular jerks. Just a wholesome place to shoot the shit and be real about what you’re making.

You can post in public, or private (with a Plus account). Use it to improve your work, or just feel good about creating things again.

Come on in! We hope you enjoy your stay.

Register here for a very fun time ✨️

Or log in if you’re returning. (Welcome back!)

All posts tagged “side-project”

I’m trying to map the basic elements that would be needed in order to have the race calculator. I don’t feel 100% convinced of what should be the right approach: asking the user what they need to know (pace VS total time) or just give all the option and let them figure out. At this point, I’m towards defaulting to set a pace that would generate the total time and they would be able to switch from a pivot to the other option.

I’m sharing some rough sketches of the process from my notebook and incoming progress in this kind of worklog: https://adrianmato.com/blog/worklog/race-calculator

When thinking about the visual execution of new projects I always start with the basic unit of information which is the text and its type ramp. I'm also going back to native fonts since they run fast as hell though I may take the license to use Montserrat for big bold titles when representing the time and other cool data about your running stats.

I'm preparing along with my spouse a pet project that would let people calculate the race pace and total time when running races. It's the perfect excuse to do two things:

- She'd keep improving her front-end skills
- I'd create a small kit of components to build pet projects faster for myself

I'd keep you posted!