Skip to main content
3.6

The Fork

Estimated time: 30 minTool: GitHub, Lovable.dev, Vercel
After this drill, you can:

After this drill, you have forked a sample project, made meaningful changes, and deployed your version — demonstrating that you can build on existing code, not just from scratch.

Why this matters

Most software is not built from scratch. It is built by extending, adapting, and customizing existing code. Forking — taking someone else's project and making it yours — is how open-source software works, how templates work, and how most real professional development starts. This drill introduces the fork-and-customize workflow: clone something that exists, make it your own, deploy your version.

How to do it

  1. 1

    Fork the AI Training Grounds sample project from GitHub

    The repository link is provided in your course dashboard. Click Fork in GitHub. This creates your own copy.

  2. 2

    Import the forked repo into Lovable

    In Lovable: New Project → Import from GitHub → select your forked repo. Lovable connects to the existing code.

  3. 3

    Make three specific changes to customize it for your context

    Ideas: change the color scheme, replace the placeholder content with your own, add or remove a section, adapt the copy for your use case.

  4. 4

    Deploy your customized version to Vercel

    Deploy following the Drill 3.4 process. Your forked version gets its own Vercel URL — separate from the original.

The prompt

PROMPT — Customize the ForkModel: Lovable.dev
I've imported a forked project into Lovable. I want to make the following customizations:

1. [CHANGE 1 — e.g. "Change the primary color from blue to forest green"]
2. [CHANGE 2 — e.g. "Replace the hero headline with: [YOUR HEADLINE]"]
3. [CHANGE 3 — e.g. "Remove the testimonials section and replace it with a FAQ section"]

Please make only these changes. Preserve everything else in the project.

Success criteria

  • You forked a project and imported it into Lovable
  • You made three meaningful customizations
  • Your customized version is live at a Vercel URL
  • You understand the difference between your fork and the original

Common mistakes

Making surface-level changes only (just changing one word)

The customization should make the project meaningfully yours. If someone looked at your version, they should see it reflects your context — not just a slightly tweaked copy.

Deploying before testing locally in Lovable

Preview in Lovable first. Confirm all three changes are reflected correctly. Then deploy.