Chapbook tutorials

1. Open connection setup and choose Sign in with GitHub. Copy the code, open GitHub, approve access and return here.
2. Search your repositories, select your website and choose Connect this website. The app checks the branch and website settings before changing your connection.
3. Returning users see their saved account. Use Refresh repositories after a failed request. Temporary outages do not require a new sign-in.
4. For a private repository, open Advanced. Enter its owner, name, branch and a token with Contents read and write access, then choose Connect with this token.

Cancel or close setup to keep the existing connection. Expired access needs a new sign-in; permission errors need the correct repository access or organisation approval.

1. After signing in, expand Create a new website. Enter its name and choose a theme. Compare desktop and phone layouts in the theme gallery.
2. Choose Create my blog. Follow any GitHub Pages setup instruction in the result panel.
3. In Site settings, add your name, description, links and professional details. Existing sites show the themes installed in their own repository.
4. Save, wait for the website build, then check the public site on desktop and phone. Review navigation and long headings.

If creation stops after the repository was made, retry with the same name to resume that repository. You can change its theme later.

1. Open Write, start a post and choose a template or blank page. Add a title and text.
2. Add images or a gallery with useful alt text and captions. Preview an interactive block and try its controls.
3. Preview the post and run the pre-publish check. Fix blocking errors, then choose Publish now to put it on your website. Save draft to GitHub keeps it unpublished; scheduled posts keep their chosen date.
4. Saved · website updating means GitHub received the files. Use Check website build, then open the website after the build succeeds.

A successful save and a finished deployment are separate steps. If the build fails, read its log before repeatedly publishing. Local drafts remain available in the editor.

1. Open the existing post from Posts, edit it, preview and publish to update the same post.
2. For a future release, choose Schedule, select a future date and time, and complete the pre-publish checks.
3. Confirm its scheduled status. The site's scheduled-publishing and deployment workflows must be enabled and working.
4. Check the public URL after deployment. Use the takedown action to return published work to draft.

The template checks schedules hourly. Publication happens on a workflow run after the due time, rather than at an exact minute.

1. Choose a theme such as Practice, Petal, Contour, Cut or Still. Add real business details and services in Site settings.
2. Configure availability, event types and confirmation emails with your booking provider. Paste its HTTPS event link into your website's booking field.
3. A Cal.com event link supports a visitor-loaded calendar on the Appointments page. Other providers open through their booking link. Services can have separate links.
4. Test the published booking flow using your own test details. Check the saved appointment, calendar entry and confirmation delivery.

For paid appointments, connect a supported payment account in the provider and use its test mode first. A displayed price does not activate payments. The provider stores appointments and handles emails and payments.

1. Keep the editor open and read the error. Network outages, rate limits and expired tokens need different fixes.
2. Wait and retry an outage or rate limit. Reconnect expired access. Correct a wrong repository or branch in setup.
3. After publishing, check the website build before expecting the new page. Repository access alone does not prove every token or branch permits writes.
4. Export drafts before changing devices, clearing browser data or forgetting a device. Keep the backup somewhere you control.

Refreshing the repository list does not erase drafts. Clearing browser storage can erase work that has not been published or exported.