Awesome!

Beyond simply copying and pasting the url, I've decided on two additional use cases for sharing from my platform:

- Republishing on other publishing platforms (Medium, Hashnode, etc)
- Republishing on microblogging platforms (Twitter/X, Bluesky, Threads)

CodeCook.live is a publishing platform. First up, I simplified the buttons on the user’s list of sessions:

• Copy link (the most common way to share)
• Share button (to open the dialog we are about to build)
• Go Live (for starting a CodeCook live code session)

CodeCook.live The publishing platform for live coding that turns your commits into live code cooking sessions

You can also follow along at codecook.live/johnnybuilds... where I’ve enabled chat.

I'm starting up a new CodeCook session on rethinking the traditional share dialog for sharing content. Follow along on this post thread as we explore how I can make sharing better on my publishing platform for live coding. #buildinpublic

If you prefer to read this CodeCook session in blog post format, check it out at codecook.live/johnnybuilds...

And with that our projects page looks much nicer!

As a bonus, I added a button to the `EditProjectForm` to allow people to easily generate a new screenshot for their project using this same function.

CodeCook.live The publishing platform for live coding that turns your commits into live code cooking sessions

Then I use the utility function in my `createProject` server action to capture the screenshot and upload it to S3 at a url keyed to the username and project id. You can see the code at codecook.live/johnnybuilds...

I’ve done this sort of thing before. We can use Puppeteer to capture a screenshot of a specified webpage by navigating to its URL and rendering it in a headless browser. I make a simple utility function to do this: github.com/johnnybuilds...

The first thing I notice is that we could have images for the projects. We allow you to upload screenshots after you import your project, but people might be likely to miss that. What if we made it automagic?

I’m starting to share this little project I’ve been working on and one thing that stands out to me is that the Profile and Project pages are a bit plain. I'm going to share my progress here in this thread. As a starting point, here is what the profile page looks like right now. #buildinpublic

I’m starting to actually share this little project with people now and one thing that stands out to me is that the Profile and Project pages are a little plain. As a starting point, here is what the profile page looks like right now.

CodeCook.live The publishing platform for live coding that turns your commits into live code cooking sessions

You can check out the session where I added chat to CodeCook in a session on CodeCook at codecook.live/johnnybuilds...

Finished adding chat to CodeCook. Looking forward to my next live code session be a little more "live" #buildinpublic

CodeCook.live The publishing platform for live coding that turns your commits into live code cooking sessions

Next up, I'm going to add a way for anyone to join a chat as a guest. I’m actually publishing as I go on codecook.live/johnnybuilds... as well, where you can see my efforts happen live. Hopefully I can get the chat fully working soon. #buildinpublic

My prompt to Cursor: I want to refactor the chat interface to be a twitch chat drawer on the right that pushes the content over. It takes a quite a few prompts and ultimately actual manual coding (😱 the horror!!!) to get it right. github.com/johnnybuilds...

In my last session on my publishing platform live coding, I started to add chat. Now I’m going to pick up from where I left off, starting with a UI refactor. Here’s a screenshot of where we’re at.

Renewing another live coding session on where I finish adding chat. Follow along at codecook.live/johnnybuilds... with any luck you’ll see a chat window show up there at some point during the session.

Thanks! I've got a waitlist up at codecook.live

CodeCook.live The publishing platform for live coding that turns your commits into live code cooking sessions

I'm going to work on adding chat to CodeCook so I'm starting up a live session (the first ever!) Unfortunately it won’t have chat because that’s what I'm building 😀 codecook.live/johnnybuilds...

You can see the chart at publicbuilders.org/xvb

I've been tracking follower growth of 100+ #buildinpublic accounts for a few months now. Originally, Bluesky was the clear leader for getting followers, especially for those that don’t already have a big audience. Unfortunately, 𝕏 has caught back up. I'm still hopeful for 🦋 but it is concerning

I piece together icons from free icon sets like lucide and hero icons

I’ve got live coding working on my publishing platforming for live coding. I’m thinking of calling live coding for introverts. I also have no idea what I’m doing 🙃 but its fun as hell #buildinpublic

The first live session of CodeCook is unfortunately just me on localhost listening for commits to CodeCook. #livecoding

I’d venture to say Bluesky’s API if fucking excellent actually

The final episode of Severance Season 1 is one of the biggest payoffs to a season of TV that I can think of.

Cook a little bit with v0.dev

Instead of writing tests when starting a project, go all in with strict typescript interfaces. No any! With Cursor, it is much easier to enforce. Once you've baked long enough and want to make sure you don't break stuff, add tests. Puppeteer can record clicks and Cursor can scaffold up your tests.