element-hq / element-hq/element-meta

[Story] Tailor banner content

Open
#3,312 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

App: ElementX Android App: ElementX iOS T-User Story Team: Element X Platform
Dominant language
No language data
Stars
112
Forks
26
Avg merge
6h 6m
Merged PRs (30d)
4

Description

Description
  • As a project manager for the migration to EX
  • I want to tailor the content of the banner shown to users
  • So I can provide instructions that are specific to us and have it in the language that our users understand

The banner has the following parts:

  • title (30 chars)
  • body (2000 chars)
  • download button

The title and body are texts that can be customized on the server side. In the body, render https:// URLs as links the user can click on.

The link behind the download button can be configured on the server side so customers can point it to the Element Pro app or to a custom app: by default it will point to the EX FOSS app. if the link is an empty string, then do not show the button.

The defaults are:

  • Title: Download Element X
  • Body: Faster sync, a cleaner design, and new features you won't find here. The Element Classic app will be retired soon, so now's the time to make the move.
  • Download button: Downloads the EX FOSS app

Acceptance criteria

  • Tailoring is optional, if no custom content is provided, then defaults are used.
  • The content of the banner can be updated on the server side when necessary

Dependencies

  • None

Out of scope

  • Translating the tailored message according to the user's locale

Questions

  • None

Subtasks

Android
iOS
Rust
Other

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No files, tests, or entry points are named. Start by identifying the Android, iOS, and Rust subtasks and the server-side configuration source; done means optional custom title, body, and download URL are supported, HTTPS URLs in the body are clickable, an empty URL hides the button, and defaults remain available.

Written by the indexing model from the issue text.

Assessment

Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.