Skip to content

Dev portal 2/4: first-visit experience splash + "interested" voting#232

Open
dmccoystephenson wants to merge 1 commit into
feature/dev-backlog-syncfrom
feature/dev-splash-and-interest
Open

Dev portal 2/4: first-visit experience splash + "interested" voting#232
dmccoystephenson wants to merge 1 commit into
feature/dev-backlog-syncfrom
feature/dev-splash-and-interest

Conversation

@dmccoystephenson

Copy link
Copy Markdown
Member

Summary

Stacked on #231. Second phase of the dev-portal plan.

  • ExperienceSplash — shown once per visitor on /: "I run a server" (dismiss, stay on the plugin catalogue) vs "I build plugins" (go to /dev). Remembered via a dpc-experience-chosen localStorage flag so it never reappears; backdrop/Escape dismiss counts as "I run a server" rather than trapping the visitor. The "Dev Portal" nav link from Dev portal 1/4: mirror open GitHub issues/PRs into a /dev backlog console #231 remains the way to switch anytime after that — deliberately not a permanent redirect on /, since that would fight with the "Home" nav link.
  • Extends the existing like mechanism to a third target type, issue (keyed repo#number) — one line in LikeService.ALLOWED_TYPES, no new backend concept. The /dev item list gets an "Interested" column reusing the same LikeButton already used for plugins/guides.

Why

This is the "users are a thing now" half of the ask: reuse what already shipped (login + likes) instead of building a parallel voting system, and let the splash be a light touch rather than gating the whole site behind a choice.

Test plan

  • ./mvnw test — 130 tests, 0 failures (1 skip, same as main)
  • npm run lint — clean
  • npm test — 84 tests, 0 failures
  • npm run build — compiles; / and /dev both render
  • Not manually clicked through in a browser (sandbox has no browser) — logic covered by experience.test.ts and the existing LikeButton/likeService test coverage instead.

🤖 Generated with Claude Code

Adds an ExperienceSplash shown once per visitor on the homepage — "I run a
server" (stays put) vs "I build plugins" (goes to /dev) — remembered via a
localStorage flag so it never nags a returning visitor; the Dev Portal nav
link (added in the prior PR) remains the way to switch anytime.

Extends the existing like mechanism (already live for plugins/guides) to
issues: `targetType: 'issue'`, keyed by `repo#number`. No new backend concept
— the /dev console's item rows get an "Interested" button reusing LikeButton,
so which of the ~100 open issues people actually want becomes visible without
building a second voting system.

Second phase of the dev-portal stack (builds on #231).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant