After this step: you can open the finished site or application at its address and check whether someone else can use it.
First check the finished project
Walk through the main task as a new user would. In the example app: add an idea, close the site, open it again, and check that the idea remains. Also try to save an empty form. Does the message explain what to fix?
Send this version for an independent review in a stronger model. Let it check code, find errors and repetitions, and propose what to tidy. After agreed corrections and refactoring—tidying the code—check behavior again. Also ask the agent to run checks recorded in project instructions. It should show what passed and what needs fixing. The corrected version should pass independent review too.
Where your project will run
Return to the solution selected in lesson 4. The publishing location should fit what you built and the technology you chose.
- A simple site, such as a profile or content site: I use Sites for this work. You work on the site, view a preview, then publish the finished version and share its address.
- Your own site or application running in selected technology: I also use Google Cloud. You must decide how to run code, where to store data if the app saves it, how to upload later versions, and what maintenance will cost. The agent should prepare this according to the project plan and explain what will run in the cloud.
- Your own address, such as my-app.com: I manage domains in GoDaddy. A domain is the name where you find a site. Connect it to the place where the project runs. You can also begin with the address received at publication.
These are examples from my workshop. Choose a way to run your project that you need and can maintain. Choosing a domain alone does not solve running an application.
What to check before publishing
Ask the agent to go through these points and show the result:
- Does the whole user task work? Buttons, forms, saving, and reopening data—according to what the project does. Also on a phone, if it is meant to be used there.
- Is it comfortable to use? Readable text, keyboard use, understandable errors, and a site that opens without a long wait.
- Is data safe? If there are accounts, a user sees only what they can access. Service passwords must not enter public files. If you store data, check that you have a copy and can restore it.
- What will you do if something stops working? Agree how you learn about a failure, who repairs it, and how you return to the previous working version.
For a simple text site, do not add accounts or a database only to get through this list. Check what actually occurs in your project. The agent should clearly say what it could not check.
Publish and check the final address
When you know the check result and costs, decide on publication. Name the specific project and place where the agent should make it available. Creating a paid service also requires your decision.
After publication, open the address you received and repeat the main task. A working preview on your computer does not yet confirm that the version available to others works the same way.
In the existing plan, record which version we published, its address, what we checked after publication, and remaining problems. In README add a short instruction for running the project, uploading another version, and returning to the previous one. If we save data, also point to the restoration instructions. Show me these files and explain what I should do if a problem appears. Do not create another plan.