Code Ownership & Versioning

Meku is a code-first platform. Every project you generate is production-ready React + Tailwind code that you fully own. This section explains how ownership works, how to export projects, and how to manage versions with GitHub or local workflows.

Code Ownership

All generated code belongs to you. Meku does not lock the projects inside the platform.

• Full access: Download or export projects anytime.
• Custom hosting: Deploy projects on Vercel, Netlify, or your own servers.
• Integrations: Export directly to GitHub for collaboration.
• Flexibility: Fork, migrate, or scale projects as needed.

Code ownership means you are free to maintain, extend, and distribute the projects without restrictions.

Exporting Projects

Meku supports multiple export methods:

• Download ZIP: Get a full project archive, ready to run locally.
• Export to GitHub: Push projects directly to a GitHub repository for version control.
• 2-way GitHub Sync: Meku supports 2-way sync with GitHub. Changes made in Meku can be pushed to GitHub, and updates from GitHub can be pulled back into Meku. This makes collaboration seamless for teams working directly at the source.
• Copy snippets: Copy individual components or pages into an existing project.

Example Workflow:

# Clone exported repo from GitHub
git clone https://github.com/username/my-meku-project.git
cd my-meku-project

# Install dependencies
npm install

# Run locally
npm run dev

Versioning with Git

Version control enables you to track changes, roll back, and collaborate effectively.

• Initialize Git:

git init
git add .
git commit -m "Initial commit from Meku"

• Push to GitHub:

git remote add origin https://github.com/username/my-meku-project.git
git branch -M main 
git push -u origin main

• Branching strategy
  • Use main for stable code.
  • Create feature branches for new iterations.
  • Merge after testing.

Note: Use restore if an iteration breaks layout or logic.

Best Practices

Follow these practices to maintain long-term project stability.

• Export frequently to keep backups.
• Use GitHub branches for feature isolation.
• Store API keys and secrets in .env (do not commit).
• Document changes in commit messages.
• Regularly pull updates before re-exporting from Meku.

These habits make AI-assisted development reliable and team-friendly.