Publishing help
Move from local work to a publication plan.
Find a suitable route for publishing a locally created result.
Move from local work to a publication plan.
When you are happy with the local result and want others to use it.
Finishing a website locally should not automatically purchase hosting. Publishing help starts by checking what this specific project needs.
Distinguish static pages from server logic, databases or accounts. Review the proposed services, costs and required setup before approving external changes.
Take a closer look.
Explore the actual screens and controls. Click an image to see every detail.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Determine whether the project is static or also needs server logic and storage.
- 02
Review the plan, required accounts and potential costs.
- 03
Authorise publication or external changes separately. Finishing locally publishes nothing automatically.
How it could work for you.
A simple portfolio may need a different hosting route from an app with user accounts and stored records.
How to assess the result
Advice does not register a domain or deploy anything by itself. Verify current service details when you publish.
Where to find it.
Easy Mode → Done → Publishing help; advanced workspace → Project help
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Available project advice and publication plans stay with the project.
What you need to know
Not every hosting environment has an automatic deployment route. Selecting a plan does not buy hosting or register a domain.