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

Unauthenticated UX

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
authentication, frontend

Research direction

Start by reviewing the current interfaces and components to identify which ones expose TPEN project data and what authentication they require. Document candidate unauthenticated experiences, then define which pages should be accessible without login and how attempts to join a project should proceed.

Written by the indexing model from the issue text.

Description

core functionality enhancement

The particular user we are talking about here is one using the various TPEN Interfaces who has not logged in. In the most strict sense you should be a registered user in order to use the interfaces. However, there may be some interfaces that can be used without any login at all.

We are talking more than about pages like /about, though that is an example of a page that should not require login. Think about pages that may show TPEN3 information related to projects, collaborators, transcription, etc.

Purely going off of imagination - there could be an interface that lets you search TPEN Projects. This page would not require authentication. Users could see projects by title or subject matter, see one they like, then try to join it and be sent off to make an account. I also think of things like the Manuscripts Browser which could serve the same purpose.

What current interfaces / components in the code could be used without requiring any authentication? We want unregistered users to have some chance at a UX that encounters TPEN project data.

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.