jpohalloran

I’m excited to share Kinda Hard Golf with you all!

It’s a 2D web-based golf game where each day brings a new, short-but-tough hole. The goal? Get to the top in as few shots as possible. It’s free to play, no download or account required — but fair warning: it’s kinda addictive.

Built natively for the web using TypeScript, PixiJS, and Rapier for physics, with several Cloudflare services powering the backend.

I’d love your thoughts, feedback, or bug reports — and yes, it’s kinda hard. :)

Thanks! —James

Hey! Congrats on the launch! At a glance looks very cool and useful. One piece of feedback I might give would be to give the user a bit more upfront knowledge of how it works before signup. I personally usually click away once I get to a signup screen unless I already have a medium/high degree of buy-in. Best of luck!

Exactly right. We tackled inline editing early on, but it had a lot of hidden complexity. Tina's fields are completely customizable, and if we support inline-editing it would be more challenging to make custom fields work while overlaying the site content. There were also challenges around the inline-editing implementation being very entwined in the user's codebase. We do hope to circle back to inline editing in the future, we just want to make sure we land on a stable solution.

CLI Tool for proofing links on your site, for use-cases where pre-generating static HTML isn't an option. Can be used w/ SSR, Server Components, Pages behind an auth wall, etc.

To setup the GitHub integration, you will need to setup a GitHub App for authentication. You'll need to reference the GitHub App's secret within your implementation, so you'll need a backend function. Vercel & Netlify make it really easy to to do with with their API functions.

There's a guide here showing how to set up GitHub on a NextJS site (and eventually hosting on Vercel): https://tina.io/guides/nextjs/github/initial-setup/

totally! The team has making strides recently to split up the packages so that only the lightest layer needs to be loaded upfront, and the Tina UI can be loaded dynamically when in edit-mode. I'll loop in some members of the team that might be able to speak more to that.

Tina dev here! We have some examples in the works of sites with Tina-specific editing routes (meaning your production pages are bundled without Tina)!

johalloran.dev? or tinacms.org? both are completely static! But tinacms.org can switch to SSR in edit-mode.