Where should someone start when looking for a contributor's work across several arcades? If activity is scattered among venue documents, knowing the author's name still means opening them one at a time. We needed a place to find both an account's introduction and its work.

Gamma adds public profiles queried by username. Nickname, introduction and join date are connected with document activity, allowing visitors to inspect other contributors as well.

A view of an author's activity

A public profile has a broader subject than a settings screen for the signed-in account. Finding the same author in different arcades, for example, should lead to one place showing where that person has participated.

We therefore present the account's self-introduction alongside activity stored by the service. An introduction alone does not show the work; a list alone offers little room to describe the person.

flowchart TD
    accTitle: The subject of a public profile
    accDescr: Look up the account by the username in the path and display that account’s introduction.
    A["Username in profile path"] --> B
    B["Retrieve that account"] --> C
    C["Nickname, biography, join date"]

Usernames and public addresses

The username in the profile address identifies the account to query. Opening someone else's address must not display the current visitor's nickname. The request follows the addressed account rather than taking its subject from the visitor's session.

The profile shows that account's nickname, introduction and join date. The introduction is self-authored text, while the activity below is retrieved from the service. Readers can inspect both together.

flowchart TD
    accTitle: Document work by person
    accDescr: Apply the same username as the author filter and show the tickets with their arcades.
    A["Retrieve tickets by author"] --> B
    B["Type, time, and arcade"] --> C
    C["Personal document work list"]

Querying accounts and contribution history

Activity queries tickets by the author's username. A ticket is a record of a submitted request. Results show request type, creation time, related arcade and total report count.

Using the same username for account and ticket queries keeps the introduction and work associated with one person. This screen presents the activity list; it does not include direct editing of every request.

Using and interpreting activity lists

Contributors can find their work across venues, while others can discover the author and places involved. Reviewing one arcade's changes now has a route into that person's wider activity.

Report count alone does not establish accuracy. Even a large number of requests still needs interpreting through the relevant documents and submitted values. The profile helps locate those items, with detailed review continuing at the document.

Reference: Username-based profile implementation.