Spaces Review QA
Use this page to review Spaces Help before publishing or adding screenshots.
Product Review
| Question | Pass condition |
|---|---|
| Does the overview explain Spaces purpose? | A reader knows Spaces is for marketplace/co-working operators. |
| Are products explained as sellable offers? | Products are not confused with customer purchases or private resources. |
| Are bookings and subscriptions operator-owned? | Operator review is separated from customer self-service. |
| Are refunds handled carefully? | Refunds are explained as review/workflow, not guaranteed outcomes. |
| Are payments public-safe? | Payment setup guidance avoids secrets and sensitive detail. |
Support Review
| Question | Pass condition |
|---|---|
| Can support triage product issues? | Product issue template and troubleshooting checks exist. |
| Can support triage booking/subscription issues? | Booking and subscription templates exist. |
| Can support triage refund issues? | Refund handoff and safety guidance exist. |
| Can support triage payment setup issues? | Payment setup template and safety rules exist. |
Engineering Review
| Question | Pass condition |
|---|---|
| Does help match route ownership? | Spaces pages cover marketplace operator routes only. |
| Are provider internals avoided? | No Stripe/bank/provider secrets or internal accounting detail. |
| Are uncertain refund/payment details marked as gaps? | Content gaps page and source inventory remain explicit. |
| Are screenshots safe? | Screenshot plan requires demo data and hidden payment details. |
Copy Review
| Question | Pass condition |
|---|---|
| Is the writing simple? | Operator workflows use concrete examples and checklists. |
| Is it American English? | No British spelling in operator-facing copy. |
| Is it comprehensive? | Setup, locations, resources, products, bookings, subscriptions, refunds, payments, integrations, analytics, and availability all have coverage. |