Choose whether the client needs to edit content or review a version. These workflows use the current Platform and Desktop development builds; a public download is not available yet.
For content editing
The agency prepares the Astro project and its editable fields first. Give the client a Content editor seat on the intended project, following team setup.
For managed GitHub onboarding, the account owner uses Invite to BlockBite project on Platform’s Team page. Review the recipient, project and repository access before sharing the invitation.
The client then:
- Opens Desktop in Guest Mode.
- Opens Shared projects, pastes the agency’s BlockBite invitation link and chooses Join project.
- Reviews the invitation and finishes sign-in in the browser. Where GitHub repository access is required, connects their own GitHub account and accepts its invitation too.
- Opens the granted project and follows its download and trust steps before installing dependencies or running the local website.
Available tools follow the client’s current project permissions. Guest Mode chooses the workspace; the agency’s grants determine access. If a project is missing or access is denied, ask the agency to check the grant and invitation.
For review and feedback
In the project’s Sharing page, select the published review version and save sharing. Choose Invite reviewer, enter the recipient’s email and select the shared version. Send an email or create a private invitation link.
The invitation is for that recipient and version. Reviewers can view it and comment when comments are enabled. They do not edit the Siteboard. A review invitation does not require handing over the project’s source code.
Hand over one clear task
Show the client how to open a page, edit a declared field and check the result. Agree on how changes are reviewed and deployed. Editing local content, sharing a review and publishing the live site are separate actions.