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

Splitscreen Tools arrangement

Open
#160 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by locating the transcription interface and workspace split-screen controls described in the issue. Trace how the tools dropdown, split-screen open/close control, and split layout sizing are assembled. Done should match the intended tool arrangement and avoid the reported oversized tools and double scrollbar, but the issue may need its separate concerns narrowed first.

Written by the indexing model from the issue text.

Description

In the transcription interface, there is a drop down that is visually separate from the split screen tool and it would be better atop the split portion.

In the workspace, I would prefer a single button to open/close the screen and even then perhaps only if the number of tools available exceeds some number. Then the top of the split can offer the options.

If we are putting tools into a dropdown for the user, it makes more sense to have them all in the drop down with the resulting action related to the type of tool rather than forcing the user to know what might happen.

Additionally (maybe for a different issue?) the tools in the split all seem to be slightly oversized (perhaps just a box sizing issue) and leading to a double scroll bar.

Dominant language
JavaScript
Stars
2
Forks
3
PR merge metrics
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.