Dashboard
Make KPIs, risks and next actions easier to scan and filter.
Sites
Turn an idea into an interactive Site
Describe the experience, add content and constraints, review the private preview, and refine what is on screen through conversation.
WebsitePrototypeInteractive
The Site-making loop
DescribeAudience, job and content
→BuildWorking interface and behavior
→PreviewCheck the real experience
→PublishShare only when ready
✓When the web experience is the deliverable
Tracker
Turn a plan into milestones, owners, dates and visible status.
Prototype
Test an interactive workflow before committing to a full product build.
Build through a review loop
Treat version one as a working prototype
Specific feedback on the visible Site improves the result faster than rewriting one very long prompt.
Give the first Site enough real material
A Site becomes useful when the prompt describes an audience and job, then supplies realistic content, data and rules.
Team reporting
Provide the KPIs, risks, decisions and next actions that the dashboard should surface. Explain which filters or comparisons help the team make decisions.
Training hub
Supply the learning resources, videos and exercises, then describe how employees should move through them and what completion should look like.
Workflow prototype
Describe the user, the sequence of actions and the decision you want to test. The prototype should help people react to the workflow, not merely admire the visual design.
Sites
Publish only what you have checked
The preview is private working space. A deployment is a live URL. Confirm audience, content, interactions and data handling before crossing that line.
PreviewAccessDeployment
From private to live
Private previewReview every change
→Saved versionCreate a return point
→AudienceSelected people, workspace or public
→DeploymentA live production URL
✓Before you publish
Test the experience
Open links, submit forms, check sign-in behavior and try interactive features as the intended visitor.
Confirm the audience
Site sharing and any sign-in built inside the Site are separate controls. Check both.
Remove risky material
Do not publish confidential, sensitive or third-party content you do not have the right to share.
Know where Sites stops
Good fit
A lightweight app, portal, tracker, dashboard or learning hub where the experience itself is the main outcome.
Consider a full software build
Use conventional development when the hard part is a specialised backend, private infrastructure or regulated data handling.
Versioning, domains and technical limits
Publishing involves more than pressing a button. Preserve a return point and understand the limits of the hosting environment.
Save a version before deployment
A saved version gives you a clear state to return to if a later change creates a problem. The preview remains the place to review changes before they affect the live Site.
Custom domains require ownership
Where supported, you can connect a domain you already own by adding the DNS records provided by ChatGPT. Sites does not register or purchase the domain for you.
Some architectures will not fit
Specialized frameworks, private networks, databases, background services or strict infrastructure requirements may fall outside the supported hosting runtime. A conventional software build may be more appropriate.