Cursor Origin | Code hosting
Present code hosting as a complete lifecycle: establish a repository, review changes, pass checks, merge, then deploy.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Cursor Origin|Code hosting · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Motion and composition
Local motion · Composition rules
Converge two entry routes into the repository list
Start by creating or syncing a repository; show its list entry only after naming and confirmation. Keep navigation selection aligned with page content so the move from creation to management is clear.
Use a pale workspace with purple surroundings and minimal accents for buttons and the current repository. Use monospace for code and clear sans serif for headings and labels.
Ground the review in specific code
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Cursor Origin|Code hosting · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="14" data-end="21"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>After entering changes, show diff context, select several lines, and open the Q&A menu. Keep the selected region, question entry, and answer tied to the same content; whole-page scrolling is not a review action.
Merge after checks pass
Emphasize merge only after check status appears, then enter CI or deployment after clicking. Use short headings as pauses between creation, review, and release, always followed by an action.
| Step | Required prerequisite |
|---|---|
| Repository appears | Created or synced |
| Review code | Specific changes exist |
| Merge permitted | Clear check status |
| Deploy | Post-merge result |
Preserve the lifecycle when changing target platforms
Replace repository name, diff, question, and deployment destination. Do more than change navigation labels: creation source, review content, and published result must belong to the same project.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Adapt to content or code lifecycles, preserving create→check→merge→publish
- Keep review status consistent when replacing repository code and destination
Production constraints
Navigation / creation form / repository list / code diff / context menu / check status / merge button / deployment target
- New-repository and sync entry points lead to the same repository list, then PR review
- Explain the code before merging; only after checks pass should the button become the final action
- CI and deployment follow merging; use black-and-white headings to separate the rhythm