# Test SiteHome with TestFlight

Thank you for testing SiteHome. You will use your iPhone to try editing the text and images of your own website. Brian acts as your agency and prepares which website you can access and what you can do.

You can save and share this page. The page itself grants no access: Brian sends personal invitations separately.

## 1. What you need

- An iPhone with an iOS version compatible with the SiteHome build offered to you. TestFlight shows device compatibility.
- Apple's free [TestFlight app](https://testflight.apple.com/).
- A TestFlight invitation from Brian to install SiteHome.
- A separate SiteHome invitation for access to your website.
- The email address that received your SiteHome invitation.

Your Apple account for TestFlight and your SiteHome account have different purposes. Your WordPress, Sanity or Payload password is not your SiteHome password. You do not need an Apple developer, GitHub or agency account.

## 2. Install SiteHome

1. Install TestFlight on your iPhone.
2. Open Brian's TestFlight invitation on that phone and choose **View in TestFlight**.
3. Accept and tap **Install** next to SiteHome, or **Update** if it is already installed.
4. Open SiteHome. Use the latest version Brian has made available to you. Find the version and build number in TestFlight under SiteHome.

No install button or an expired invitation? Contact Brian. A submitted build may still await Apple's processing or approval; an invitation does not make every build immediately available. TestFlight builds expire after up to 90 days. [Apple explains installing and testing](https://testflight.apple.com/).

## 3. Accept access to your website

1. Open the separate SiteHome invitation link from Brian.
2. Sign in or create a SiteHome account using **the same email address that received the invitation**. Choose your own password and complete any email verification.
3. Accept the invitation. If this happens in your browser, open the SiteHome app afterwards and sign in with the same account.
4. Go to **Sites** and open your website. Check its name and address before editing.

You do not need to connect the website again or enter a CMS token. Brian prepares access. Missing website, wrong website or view-only access? Stop there and tell Brian which email address you used. A TestFlight invitation alone grants no website-content access.

## 4. Agree on the test first

Choose one suitable post or page with Brian. Keep the original text or a screenshot so you know what to restore. Agree whether you will only test drafts or may also publish a small change to your real website. Do not edit that same item concurrently with someone else during this test.

**Saving a SiteHome draft does not change your website. Publishing can change the real website.** Publishing starts off for a new connection and requires the appropriate rights. Do not enable it just to finish a test step; check with Brian. Avoid confidential data in test text or feedback.

## 5. First round: explore and save a draft

Allow about 15 minutes. Confusing wording, missing controls and unexpected steps are exactly the feedback we need.

1. Open your website's content. Can you find the right group and agreed item? Try search if it is offered.
2. Check the title, text and image. Do you recognize your website's content? Report anything unexpectedly missing or unreadable.
3. Change a short piece of text in an available field. Check typing, selection and keyboard behavior.
4. If an image field is available, choose a suitable test photo and check the image and any alternative text. Otherwise skip this step.
5. Save a **draft**. Open your public website in the browser and confirm saving has not changed it.
6. Return to the overview, reopen the item or saved draft and check your changes are still there. Try again after closing and reopening the app.
7. Review your changes. Is the target website and content clear? Are text and image exactly what you intended? Stop before publishing unless you agreed to do so.

Some fields or layouts deliberately remain closed, with a reason. This is not necessarily a bug, but tell us if it prevents an important task. Available fields and features depend on the website.

## 6. Only if agreed: publish a real change

1. Check the website and item again, and that its administrator has allowed publishing.
2. Review the exact changes and publish only the small change you agreed beforehand.
3. Open and refresh the public page in your browser. Check the actual result and report any difference from SiteHome.
4. Restore the original content through a new edit, review and deliberate publication if you agreed to do that with Brian.

If you see an error, conflict or unclear result, keep the message or take a screenshot and contact us. Do not repeatedly tap publish when the outcome is uncertain. **Creating new items or taking content off the website is outside this first round** unless Brian agrees separately.

## 7. Optional extra checks

- Try light and dark mode. Are text, fields and bottom controls readable?
- If the AI assistant is available, ask for a small change, review it and save a draft first. An AI suggestion is not permission to publish.
- Sign in again or reopen the app. Can you return to your website and saved work?
- Optionally compare with the [SiteHome web app](https://app.getsitehome.com/) using the same account. Do not edit the same item concurrently on both devices.

## 8. Report a problem or suggestion

In SiteHome, go to **Account → Report a problem**. Some error messages also offer a reporting button. You do not need GitHub.

Describe what you tried, expected and actually saw. Add a screenshot if useful, hiding passwords, tokens, other people's details and confidential website content first. Screenshots are optional. Leave email contact enabled if we may follow up.

Before sending, SiteHome shows which app context is included. Version/build and screen context are included where available; mention the website or item yourself when needed. Wait for **Thanks for your report** to confirm it was sent.

Use this example:

```text
Website and item:
I wanted to:
Steps: 1. ... 2. ... 3. ...
I expected:
What happened, or the exact message:
Every time or sometimes?
iPhone model, iOS version and SiteHome build from TestFlight:
Was this a draft only, or had I tapped publish?
```

If SiteHome will not start, sign-in fails or the reporting form does not work, send the same details directly to Brian through the channel he used to invite you. For crashes or visible problems you can also choose **Send Beta Feedback** under SiteHome in TestFlight. [Apple explains tester feedback](https://testflight.apple.com/).

## 9. After your test

Tell Brian what went well, where you hesitated and your top three improvements. “I did not understand what to do here” is useful feedback. Mention any draft left behind and whether an agreed live change was restored.

Brian collects the reports and agrees the next round with you. Technical tests and successful builds do not replace your experience on the real app. You do not need to share access passwords or sensitive data to give feedback.