Export a project, tokens or a component
These instructions are reviewed against the app source. Final-installer walkthroughs are still pending. Check platform availability and requirements before installing. Windows is an updates list, outside the 1,000 beta places.
File → GitHub & export… prepares reusable packages. You can download them locally or send them to a repository without publishing a website.
Prepare a local package
- Choose Project, Design system tokens or Single component.
- For a component, choose the component to include. Review the available target selections.
- Choose Prepare package.
- Inspect Included files and checksums.
- Choose Download ZIP and inspect the files before sharing.
| Scope | Package contents |
|---|---|
| Project | Editable source, project.modo, registered assets and generated code for selected enabled targets |
| Tokens | DTCG, resolved values, CSS and JavaScript/TypeScript consumption files |
| Component | An isolated editable project, reachable dependencies and generated output |
Full-project packages include CMS drafts. A component can bring dependent components, referenced content and shared design values. Inspect the package rather than assuming it contains only one small file.
Generated web output is HTML/CSS/JavaScript, not an automatic React component. Native source still needs the appropriate tools to build. This export does not collect arbitrary hand-written files, your Git history, local secrets or caches.
Send to GitHub
- Create or choose an initialized repository in your GitHub account, with at least one commit.
- Configure the token requested by the UI for that repository. It needs content write access; creating a draft pull request additionally needs pull-request write access.
- Enter the owner, repository, export branch and folder. The default branch is not an allowed export destination.
- Optionally enable Open a draft pull request.
- Choose Compare with GitHub.
- Review repository visibility, changed files and text differences. Inspect binary files in the ZIP.
- Confirm the current comparison with Confirm push to GitHub.
- Keep the resulting commit or comparison link.
MODO does not create the repository or perform a generic clone/pull/merge workflow. GitHub Pages is the separate website publishing flow.
If files conflict
MODO protects externally modified managed files and unrelated files. Do not erase them to make a push pass. Inspect the remote changes, choose another empty export folder or deliberately reconcile the changes outside this flow, then compare again.
If the commit succeeded but draft-PR creation failed, use the reported commit/comparison link. Avoid repeating the entire export just because the optional PR did not open.
The app integration has been tested with a simulated GitHub service. A real repository can impose additional permissions, SSO or branch policies.
Need a correction? Tell us