Hop
ae2ffae36d
Hop-State: A_06FN4GBGQFKPXH5B5MK4P0R Hop-Proposal: R_06FN4GAZCEER9W65XJTCVJG Hop-Task: T_06FN4FT3436TX5AV35QM4RR Hop-Attempt: AT_06FN4FT3401X9BHCJVKT52G
1.7 KiB
Hop-native Gitea semantics
HopWeb keeps Gitea's existing forge interface and adds a Hop-specific public home page, brand mark, and semantic vocabulary for collaboration elements.
Install
From the project root:
./deploy/gitea/install-hop-native.sh
Set ENV_FILE when the Compose environment is stored elsewhere:
ENV_FILE=/path/to/environment ./deploy/gitea/install-hop-native.sh
The installer copies the home page, brand mark, styles, and adapter into
Gitea's persistent custom directory, sets the application name to Hop,
restarts Gitea, and waits for a healthy response. Re-run it after editing an
asset or replacing the Gitea volume.
Semantic mapping
| Native route and behavior | Hop label |
|---|---|
| Repository code | Files |
| Issues | Tasks |
| Branches | Attempts |
| Commits | Checkpoints |
| Pull requests | Proposals |
| Actions | Evidence |
| Merge pull request | Accept proposal |
The adapter updates visible text, document titles, form placeholders, tooltips, and ARIA labels. It scopes replacements to Gitea navigation, headings, menus, breadcrumbs, labels, and buttons, so repository content and user-authored prose remain unchanged.
Repository home pages also receive a Hop workflow group in the existing
Gitea sidebar. It uses Gitea's own classes, links, icons, and live counts.
Upgrade check
After changing the pinned Gitea version:
- run the installer;
- confirm Tasks, Proposals, and Evidence in repository navigation;
- confirm Attempts and Checkpoints in the Files view;
- confirm proposal creation and acceptance labels;
- inspect browser console errors; and
- test a narrow viewport and keyboard navigation.