Repository navigation
Show the team's live activity, open on the track map, and call levels Level 0 to 4 - #71
Merged
Merged
Conversation
Lines carry their number at the start and in the picker, which now sits above the map. The reading guide is one row. Zones use the stage names, cleared stations turn yellow with a check, and the map and the phone strips mark the next quest to clear. Phone strips show the line's tagline and which lines each transfer station joins.
Clearing every quest in a stage now stamps the passport, which gains a roadmap group of five stage stamps; the tracker beside the tab note opens the passport instead of keeping its own count. L3 and L4 quests are the passport's comment, first PR, runner and Builder stamps, with their repos listed below as the stage's repos. The goal chips give way to a single start-finder button, with a way back while a suggested route is shown.
The track map is the first tab, and phones now get the map itself, panned sideways, with the line-by-line list folded underneath. Levels read as Level 0 to Level 4 across the roadmap, map, cards and finish card. The roadmap copy is shorter: one line for the tabs, no stage kicker, no tags on the cards, and a plain 'stamp when done' goal.
…n in A line under the hero shows what the team just did on GitHub, the contributors section lists everyone who contributed in the last 30 days with what they did, and the join section opens with the loop the hub runs on (learn, contribute, get named, share) with today's numbers. Activity comes from GitHub when a visitor opens the hub and from a snapshot the deploy builds every day otherwise. New events: section_view, live_click, loop_click and click_event for the events section.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The hub shows that it is alive and who keeps it alive, and the track map comes first. Five commits. The first two were pushed to #69 after it was merged, so they come along here.
Carried over from #69
Track map first, Level 0–4, less to read
L0–L4in data and links.Alive: activity, credited by name
api.github.com/orgs/CausalInferenceLab/eventswhen a visitor opens the page.data/activity.json.scripts/build_activity.pybuilds that file on every deploy and now also daily. It fills in PR titles, which the events API leaves out.The loop, visible
"참여하기" opens with four steps, each linking to its section:
A dashed line under them says the shared link brings the next person back to step 1. The step cards below lose their big numbers so the two numberings don't clash.
Events
section_view(section): curriculum, contrib, activity, events, posts, join. Sent once per page view when about a third of the section is on screen.live_click(placement: ticker | feed,target: builder | github | repo | feed,kind,repo)loop_click(step)click_event(action: signup | record | next_strip,event_order,placement) for the events section and the next-event strip.click_join.Checked
HUB_DEBUGfires each new event once, with the expected params.Generated by Claude Code