Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Collab Phase 2: Realtime Client and Presence UI (No Save Behavior Change Yet)

Open
  • Is something wrong?
#555 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
frontend, networking

Research direction

No files or tests are named. Start by reviewing the TPEN-services websocket skeleton dependency and the existing interface entry points for active editing, then trace the current feature-flag and save behavior. Done means presence and cursor updates work in active pages, reconnect and token refresh are handled, and save behavior is unchanged when enabled or disabled.

Written by the indexing model from the issue text.

Description

collaboration cross-repo frontend phase-2 websocket

Summary

Implement websocket client integration and collaborator presence UI without changing persistence behavior yet.

Scope

  • Add websocket client service with reconnect and token refresh handling.
  • Join project and page rooms for active editing context.
  • Send and render presence/cursor/selection events.
  • Keep current save endpoints unchanged in this phase.
  • Gate by feature flag.

Acceptance Criteria

  • Collaborator presence appears in active page.
  • Cursor updates are visible with acceptable latency.
  • Existing save behavior remains unchanged when feature flag on.
  • Full disable when feature flag off.

Dependency

  • Depends on TPEN-services websocket skeleton issue.
Dominant language
JavaScript
Stars
2
Forks
3
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CenterForDigitalHumanities/TPEN-interfaces

All issues in CenterForDigitalHumanities/TPEN-interfaces

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.