element-hq / element-hq/element-web

Ability to customise the registration page

Open
#19,378 3 comments 1 reaction 0 assignees View on GitHub
A-Registration O-Uncommon T-Enhancement
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Your use case

#### What would you like to do?

We can already provide custom HTML for "/welcome" and "/home" - I'd like to be able to do the same for /register

#### Why would you like to do it?

I'm hoping to use token-based registration for https://chat.ansible.im. As of right now, enabling this on my test Synapse means tokens use the fallback auth in Element Web, which looks like this:

![image](https://user-images.githubusercontent.com/827786/137114914-1978c50c-2449-4bac-b8ff-b62fe8efb3a8.png)

I've highlighted the "start auth" link because it's not obvious that you need to click this. While I would clearly love full support for tokens in Element, right now just being able to customize the register page would be enough (as I have no plans to use any other forms of auth at this time). I can also make the registration page fit the rest of our branding, which is a plus.

I can image other organisations would benefit from such customization too, and it completes the set with /welcome & /home

#### How would you like to achieve it?

We are able to provide custom HTML files for "welcome" and "home" (eg https://github.com/ansible-community/ansible.im). Ideally having a "register" in this repo would work too.

### Have you considered any alternatives?

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by locating the existing custom HTML handling for the /welcome and /home pages and compare how those routes select their files. Extend the same behavior to /register, then verify that a supplied registration HTML file is served and that the existing pages still work.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.