Learn Joisk.
One small thing at a time.

Before you start

A browser and a Joisk account. Sign in at Sign in when the workspace asks you to save or create.

How to do it

1. 1Open Chat and start with one concrete question or goal.
2. 2If the answer becomes a project, keep the brief in Chat and let it build the first version.
3. 3Review the result, ask for one focused change, and keep the useful version saved.

Before you start

Know what you want to understand or make. A short goal, audience, and desired format are enough; add a reference file only when it helps.

How to do it

1. 1Open Chat and write the outcome you want, not only the feature name.
2. 2Include constraints such as audience, tone, device, or a reference format.
3. 3Read the response, then ask for the next smallest change instead of restarting the whole request.
4. 4When Joisk offers a Builder or Studio path, follow that visible handoff so the project context stays attached.

Before you start

A signed-in account and a brief that names the project's purpose. You can also start from a template in Discover when one fits.

How to do it

1. 1Open Chat and type what the project should help someone do.
2. 2Choose a project direction when the start screen offers one, or let the brief define it.
3. 3Press Start building. If sign-in appears, complete it in the inline prompt so the brief can continue.
4. 4Open the project workspace, inspect the preview, and ask for one targeted change.

Before you start

A signed-in project context when the Studio asks for one, plus a clear prompt. Decide whether you need an image, video, audio, or 3D result before choosing the tool.

How to do it

1. 1Open Tools and choose the matching Studio.
2. 2Describe the subject, intended use, and any reference or duration the control requests.
3. 3Review the tier, format, and visible estimate before starting a generated action.
4. 4Wait for the result to appear in the Studio history, then preview or download it from there.

Before you start

Name the audience, the primary action, and the smallest version that would be useful. Keep private credentials and real personal data out of the brief.

How to do it

1. 1Start with the outcome: “Help a visitor book a time,” “Help a team track requests,” or “Help a player reach a goal.”
2. 2Add the key screens or states, the tone, and any references Joisk should follow.
3. 3Submit the build and watch the visible activity/status surface instead of assuming a request finished.
4. 4When the first version is ready, use the preview and ask for a focused edit.

Before you start

A project with a previewable version. If you know the exact element, use the preview selection control; otherwise describe its label and location in Chat.

How to do it

1. 1Open Preview in the project workspace and check the primary path at the viewport you care about.
2. 2Click the relevant element when the preview offers click-to-edit, or describe its label and location in Chat.
3. 3Read the proposed diff or review state before applying the change.
4. 4Reopen Preview after the edit and check both the changed path and the nearest unaffected path.

Before you start

A project with at least one saved build. Keep the version that is currently public in mind; private edits do not become public until you publish them.

How to do it

1. 1Open the project's History or Versions surface.
2. 2Compare the candidate with the version you last trusted.
3. 3Restore the earlier version when needed, then reopen its preview.
4. 4Make the next edit from the restored version and publish only after review.

Before you start

A signed-in account and, for project-linked assets, the project you want to work in. Use invented or approved fixtures for disposable tests.

How to do it

1. 1Open the project's Assets panel or the account Assets view.
2. 2Upload a supported file or create a result in a Studio.
3. 3Check the asset label and project association before reusing it.
4. 4Download or place the asset through the visible control; keep the original when an edit is non-destructive.

Before you start

A signed-in project context and a prompt. Use a reference asset only when you have permission to use it.

How to do it

1. 1Open Joisk Image and describe the subject, composition, and intended use.
2. 2Choose the visible quality tier and review the estimate before generating.
3. 3Compare saved results, select the one you want, and use its preview or download action.
4. 4Reuse it from the project or account asset library when the destination supports that type.

Before you start

A signed-in project, a prompt or supported reference input, and the duration, resolution, and aspect choices the Studio exposes.

How to do it

1. 1Open Joisk Video and choose text, image, or reference mode.
2. 2Set the duration, resolution, aspect, and optional camera treatment.
3. 3Review the estimate and submit once. Watch for Queued, Rendering, Finalizing, and Ready.
4. 4When the job is Ready, preview or download the saved video from the render history.

Before you start

Local source media you are allowed to edit. The editor can use local videos, images, audio, and project context; cloud generation is a separate action.

How to do it

1. 1Open Video Editor and import the local source files you need.
2. 2Place clips on tracks, trim the in/out points, and adjust the visible audio controls.
3. 3Play the sequence through the important transition and check captions or text overlays.
4. 4Save the edit or export through the control the beta surface makes available.

Before you start

A signed-in project, a short description of the sound, and a duration when the selected mode asks for one. Use a voice or likeness only with the required consent.

How to do it

1. 1Open Joisk Audio and choose Music or Voice.
2. 2Describe the sound and set the duration or voice controls the mode provides.
3. 3Review the tier and estimate, then generate once.
4. 4Play the saved result, select it for reuse, or download it from the Studio history.

Before you start

A signed-in project and a clear description of the object or asset. Check the output type shown by the current Studio before planning a scene around it.

How to do it

1. 1Open Joisk 3D and describe the model or asset you need.
2. 2Review the visible quality tier and any input requirements before starting.
3. 3Inspect the saved model result and confirm its asset type before reusing it.
4. 4Attach it only through a compatible project or Studio control.

Before you start

A previewable project version, an intentional public audience, and a check that you are not including secrets, personal data, or unapproved media.

How to do it

1. 1Open Review or the publish control in the project workspace.
2. 2Check the main path, empty states, links, forms, mobile layout, and visible content.
3. 3Resolve any security, content, or readiness warning the review surface shows.
4. 4Publish the reviewed version and copy the resulting public link only after it is visible.

Before you start

A published project and a decision about whether it should be public. Remove private notes and test data before sharing.

How to do it

1. 1Open Published and choose the project you want to share.
2. 2Use the visible Discover or profile action and review the preview of the public card.
3. 3Open the public link in a signed-out or private window to verify what a visitor sees.
4. 4Update the project and republish when you need the public version to change.

Before you start

A published site and an eligible account. Do not change DNS until Joisk shows the exact records for your domain.

How to do it

1. 1Open Account → Domains.
2. 2Add the domain and select the published site the panel offers.
3. 3Copy the shown CNAME or verification TXT records to your registrar.
4. 4Return to Joisk and choose Verify; wait for the certificate/status result before switching traffic.

Before you start

Your own payment-provider account. Confirm its merchant, processing, tax, refund, marketplace, and payout terms before publishing a Buy action.

How to do it

1. 1In Chat, ask JoiskBot to “set up payments” or open Publish → Get paid.
2. 2If Connect Stripe is available, choose this project's test or live environment and finish Stripe's connection page. Otherwise paste an https checkout link from your provider.
3. 3Review the button label, price copy, destination URL, and what the buyer receives.
4. 4Publish only after a safe test confirms checkout and, for a Stripe connection, the expected webhook fulfillment. A connected status by itself is not proof of fulfillment.

Before you start

A project with a saved version. If you are exporting for another host, verify any runtime, asset, and environment requirements before leaving Joisk.

How to do it

1. 1Open the project settings or export control.
2. 2Choose Export and download the source package when the action is available.
3. 3Keep the downloaded source and its version information together.
4. 4For phone access, share the published web link or use the browser's Add to Home Screen / Install action where supported.

Before you start

A supported Windows beta package from the official Download page, a folder you choose, and a signed-in Joisk account.

How to do it

1. 1Install the current Windows package from Download; check the version shown there.
2. 2Open or start a conversation, then choose the project folder when the app asks.
3. 3Read each proposed local action. Commands such as dependency installation, tests, or builds require the app's approval control.
4. 4Open the preview when it appears and return to the conversation for the next change.

Before you start

The email or Google sign-in method you used for the account. Never send a password, reset link, token, or private key to support.

How to do it

1. 1Open Sign in and use the account method you recognize.
2. 2If you need a password reset, use the visible reset path and return through the normal sign-in page.
3. 3Open Account and choose Projects, Assets, Published, Plans & usage, Billing, Domains, or Settings.
4. 4Sign out before handing the browser or a shared test device to someone else.

Before you start

A signed-in account and a connection to the Joisk server. If the server cannot return a current snapshot, treat the state as unavailable rather than zero.

How to do it

1. 1Open Account → Plans & usage.
2. 2Check the current plan, weekly window, category quantities, active operations, and the server-confirmed reset time.
3. 3Read infrastructure separately from AI usage; storage, bandwidth, email, database, compute, and build measurements are not interchangeable.
4. 4Use the visible refresh or reconciliation action when the panel says a result is pending.

Before you start

Know whether you are a new account or an existing subscriber. Use the signed-in Billing panel for current subscription status, period end, and payment-method actions.

How to do it

1. 1Read Plans & pricing for the Plus $25, Pro $100, and Studio $200 monthly lineup, their yearly prices, and its current checkout status.
2. 2For an active subscription, open Account → Billing and choose the visible management action.
3. 3Confirm the price, currency, interval, renewal, and failure state in the account or provider portal before changing anything.
4. 4Keep included weekly AI allowance, one-time AI resets, and infrastructure resources separate. Infrastructure overages require explicit opt-in, a saved payment method, and a spending limit; AI never bills automatically.

Before you start

An account you own and the minimum token or key scope shown by the connection UI. A provider subscription is not the same thing as an API key.

How to do it

1. 1Open the account Settings/connection panel and read the purpose and scope before connecting.
2. 2Use a fine-grained token or key created for this integration; never paste a production secret into a prompt or support message.
3. 3Confirm the connected status, then perform only the Push/Pull/Test action you intended.
4. 4Disconnect from the same panel when you no longer need the integration; revoke the token at its provider too.

Before you start

The project or Studio surface that started the action. Keep any visible request, job, operation, or receipt identifier.

How to do it

1. 1Read the current status in the original conversation, project, render history, or account Usage panel.
2. 2Refresh the status or saved history once if the connection has recovered.
3. 3If the status is ready, use the saved output. If it is failed, read the reason. If it is uncertain, stop and reconcile.
4. 4Escalate with the visible timestamp and identifier when the bounded recovery does not resolve the state.

Before you start

The route or Studio name, what you expected, what you saw, and the approximate time. Use a marked fixture or disposable account for reproduction where possible.

How to do it

1. 1Check the relevant guide and retry only the safe, bounded recovery it describes.
2. 2Open Help for guided topics or Contact for a person.
3. 3Include the visible error, request/job/operation ID, browser or app version, and whether the result was ready, failed, or uncertain.
4. 4Leave out passwords, reset links, tokens, private keys, payment numbers, personal documents, and unredacted private conversations.