docs
/
Walkthroughs

Welcome to Appmint

From signup to your first draft page: create your workspace, finish essential setup, find the builder and verify your first small win.

First edition — lesson draft. These chapters combine documented workflows with labeled research clips and screenshots. The clips are silent research footage, not finished narrated tutorials. Steps that still need a complete recording are identified beside the relevant material.

From signup to your first draft page: create your workspace, finish essential setup, find the builder and verify your first small win.

Your mission

You are starting Cedar Workshop from scratch. Begin with signup, prepare the workspace, then make a simple draft workshop page. Your first finish line is a saved page you can reopen and preview—not learning every feature at once.

  • Understand what Appmint does and where each tool fits
  • Follow the signup and workspace journey
  • Find your way around Studio Manager
  • Plan your first page in Build Studio
  • Write a useful brief for Vibe Studio

Review progress is available when JavaScript is enabled.

1. Sign up and reach your workspace

Your organization is the context for your work. Treat signup as the beginning of a journey, not proof that a site is ready. The recorded form below shows the entry surface; provisioning and confirmation still need a complete capture.

01Public site
02Signup
03Confirm workspace
Research clip · signup form, no submission

Walk through it

  1. Open appmint.io and follow its signup entry. Have your workspace/project name and an email account you can access ready.
  2. Complete the fields requested by the current form. Keep passwords and verification codes outside the recording.
  3. Submit only when ready to create your learning account, then complete any confirmation shown. The existing clip ends at the form; it does not establish the completed confirmation flow.
  4. On the first signed-in screen, confirm the workspace and role. Continue to setup; an existing demo workspace is not the same as a fresh account.
Does seeing the signup form prove a new workspace was created?

Go deeper · why this matters

The current footage establishes only that the entry form renders. A completed signup needs its own end-to-end verification. You can identify your learning workspace without confusing it with another organization.

Recording coverage for this chapter

Capture a fresh signup, confirmation and first landing in a designated test account. Current footage stops before submission.

2. Complete your first workspace setup

Once signup is complete, orient yourself before creating content. Studio’s setup wizard guides the starting configuration, but the demo footage shows an existing workspace. Your new account may have different information or prompts. Follow what the current wizard requests and verify the workspace at the end.

01Confirm workspace
02Complete setup
03Choose a first task
Research clip · existing demo setup; fresh workspace capture pending

Walk through it

  1. Check which organization you are in and the account you signed in with. Record the workspace name for future sign-ins.
  2. Work through the setup wizard’s required business/site details. Review any location, base-data or module choices it presents rather than assuming the demo is a blank organization.
  3. Choose a website as your first project. The observed website-first setup has a Build my website entry; use that route when it is shown.
  4. Before continuing, confirm you are in the intended learning workspace and identify where to return to its setup or Home screen.
What should you confirm before creating your first page?

Go deeper · why this matters

Start in the right context and complete the required setup. Advanced modules can follow the first useful task. You can return to the same workspace and explain the single task you will do next.

Read the detailed documentation

Recording coverage for this chapter

Capture a new test workspace from this starting state through the saved result. Use close-ups on the named controls, keep private account details off screen, and verify the persisted records. This onboarding sequence still needs a complete end-to-end recording.

3. Find your way around Studio Manager

Studio Manager is the console. Build Studio, CRM, content, events, configuration and other areas serve different jobs. Menus can vary by role, so learn the purpose of an area rather than memorizing its position.

01Organization
02Role & access
03The right area
Research clip · demo setup landing, not the full console tour

Walk through it

  1. Identify the workspace and any selected location.
  2. Find Build Studio, CRM and Events. Notice whether your role exposes them.
  3. Open one area, identify the type of records it manages, then return to your starting point.
Why might two colleagues see different menus?

Go deeper · why this matters

Role settings affect menu visibility, while the server still enforces access permissions. Your teammate can choose the correct area for those three tasks.

Read the detailed documentation

Recording coverage for this chapter

Record this sequence in a test workspace. Show the starting context, every meaningful action and the resulting saved state. Avoid jump cuts across steps the learner must reproduce.

4. Shape one useful page

Keep your first page delightfully simple: a workshop name, a short promise and one next action. Build Studio supports components, data-backed content and forms. A preview is your chance to inspect the page before you publish.

01Choose a starting point
02Build & preview
03Verify before publishing
Research clip · wizard entry only

Walk through it

  1. Open Build my website if the setup wizard presents it, or find Build Studio in your workspace. Choose a starting design or template.
  2. Use a clear draft name such as Cedar Workshop Welcome. Add a heading, a short description and one next action. Keep this first version small.
  3. Save the draft using the controls in your build. Reopen it from the page list to check that the edit persisted.
  4. Preview desktop and mobile layouts. If the page includes an enquiry form, submit test data and verify the intended saved record before publishing.
What should you verify after testing an enquiry form?

Go deeper · why this matters

A polished page and a working workflow both matter. Check the stored enquiry as well as the visible response. A visitor can tell what the workshop offers and what to do next.

Read the detailed documentation

Recording coverage for this chapter

Capture the actual canvas, a draft edit, desktop/mobile previews and a verified test submission. The existing clip only opens the wizard.

5. Optional next step: meet Vibe Studio

Vibe Studio is introduced as the generation-led part of the toolkit. A useful brief names the audience, the job, the information and the desired action. The current clip shows its login only; generation and refinement need a separate verified walkthrough.

01Describe the job
02Review the result
03Refine & verify
Research clip · Vibe Studio login only

Walk through it

  1. Write who the page serves: someone looking for a weekend workshop.
  2. Specify the sections, the call to action and the information it needs. Example: “Show upcoming classes and let a visitor enquire about one.”
  3. When a generated result is available, review accuracy, layout and behavior instead of assuming it is ready to publish.
What makes a stronger generation brief?

Go deeper · why this matters

Specific requirements give you something concrete to review and improve. Another person can understand the intended page without guessing its purpose.

Read the detailed documentation

Recording coverage for this chapter

Record authenticated generation and a refinement in an authorized test project; confirm the actual handoff and publishing flow before narrating them.

6. Your first win—and what comes next

You have reached the end of the welcome path when you can return to the right workspace, reopen your first saved draft and explain its next action. Publishing, custom domains and a complete enquiry workflow can be your next lessons. You do not need to finish every integration on day one.

01Return to workspace
02Reopen draft
03Choose the next lesson

Recording planned. This chapter currently uses a workflow diagram; verified footage is still to come.

Walk through it

  1. Sign out and return through the normal sign-in route when you are ready to verify access; confirm the same workspace loads.
  2. Find your draft page, reopen it and check the text and responsive preview.
  3. Write down what remains before a public launch: the action must work, test records must be checked, and publishing/domain settings must be reviewed.
  4. Choose your next path: building and forms, CRM and chat, events, or Appmint Mobile.
Which result finishes this welcome lesson?

Go deeper · why this matters

The welcome path builds confidence through a small verified result. Deeper setup belongs to the next task. Your draft is saved and findable; you know the next task without claiming it is already a live finished website.

Read the detailed documentation

Recording coverage for this chapter

Capture a new test workspace from this starting state through the saved result. Use close-ups on the named controls, keep private account details off screen, and verify the persisted records. This onboarding sequence still needs a complete end-to-end recording.

Continue your setup

Keep exploring

Browse all tutorials