You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great idea! Currently, we have a url field to redirect to a page about the event.
export interface Event {
id?: number; // announcement id
name: string;
description?: string;
img: string;
startDate: string; // use Server time (UTC+8)
endDate: string; // use Server time (UTC+8)
color?: string; // defaults to automatically detecting the img color (prefer darker colors)
+ url?: string; // link to an informative page about the event
showOnHome?: boolean; // whether we show it in the home dashboard
isGlobal?: boolean;
}
Would using this field as the main source URL and adding a reliability: string property be good enough? Or should we have a another dedicated link for the source image?
Another approach is to make the main description URL a link on the modal's image header while an image credits URL + reliability rating is added to the modal content area.
What would you say is the most intuitive & user-friendly approach to design the UX?
Add a field for Source, whether it's a clickable url or just a free-text field.
Add a tag for reliability of the Source.
For example, when submitting a change to Jinhsi's convene dates, I could have added "WuWa Discord Server" as a source and "Official" as reliability.
Possible choices for reliability (these could be documented in the readme)
-Official
-Speculation
-Leak ({leaker_name})
The text was updated successfully, but these errors were encountered: