Crew Log

What Crew Log Is

It brings together member intros from Slack #welcome, resource threads from #resource-threads, polls from #pulse, and launches from #ship-it, with their replies and reactions.

Why It's Different

A discussion can help you understand a resource, compare an experiment, or improve how you use a system. Crew Log keeps those conversations attached to the work while you move between resources and Slack.

Your intro starts in Slack and becomes part of the Lab. Resource discussions stay attached to the resource that started them, connect to Slack threads, and roll up into Crew Log so the community can catch up from one place.

Intros From #welcome

Your Crew Log intro starts in Slack #welcome. Post who you are, what you're building, and what you want out of the crew. The intro appears in the Crew Log Intros tab so members can meet you from the dashboard too.

Replies to that intro stay attached to the same conversation. Slack stays fast and human; Crew Log keeps the intro visible after the day has moved on. #welcome is open to everyone in the Lab’s Slack, including invited guests, and members see intros and resource discussions in Crew Log, so share only what you are comfortable with the whole community reading.

Resource Discussions

After you have introduced yourself, Builder+ members can start a discussion below an accessible Lab resource. Crew Chief creates the matching parent thread in Slack #resource-threads, and the discussion appears in the Crew Log Resource Threads tab and on that resource page.

This keeps the resource context attached to the conversation. People can see what video, lesson, or prompt started the thread before they jump in.

Pulse and Ship It

Pulse is where the crew asks questions. Type /poll in #pulse to ask a question with up to five answers, or /poll prediction for a Yes/No call. Everyone gets one private vote, shared across Slack and the Lab. Change it any time while voting is open. The person who asked closes voting from Manage poll on the Slack card, and a prediction is resolved once voting has closed. Only the totals are visible, and the thread is where people explain their choice.

Ship It is where the crew celebrates progress. Type /ship in #ship-it to open a short launch form, or /ship followed by your message to post straight away. Add your App Store link and your app icon appears beside your announcement in Crew Log. Use Edit launch on your post to fix a typo or share an update, and Withdraw launch if it shouldn't be there. The thread under each launch is the discussion.

Reply Wherever You Are

Every connected thread can continue from either side. Reply in the Lab and it posts into the Slack thread. Reply in Slack and it appears under the same conversation in Crew Log, and on the resource page for resource discussions.

If Slack cannot create or receive a synced resource discussion, the Lab does not create a website-only copy that other members might miss. It asks you to try again instead, keeping the conversation aligned.

Reactions, Edits, and Deletes

Supported reactions and message changes stay aligned across the connected thread. The goal is simple: the important context should remain readable whether someone joined from Slack or from the Lab.

Crew Log does not archive every Slack room. It focuses on the synced community surfaces that belong beside Lab content.

How To Use It

• Join Slack from onboarding, Crew Log, or your Profile page.
• Post your intro in #welcome so it appears in the Crew Log Intros tab.
• Open a resource and start a discussion when you have a question, note, or useful build thought.
• Ask the crew with /poll in #pulse, and share what you shipped with /ship in #ship-it.
• Reply from Slack or the Lab on any connected thread.
• Use Profile to reconnect or repair Slack access if your account ever looks out of sync.

For the full workspace map, read the Slack Community guide.