Skip to content

Refactor credits page #1782

@wjt

Description

@wjt

Currently the (very nice!) scrolling credits page is constructed by copying the controls and hand-editing text in each section. This makes it harder to keep up to date and expand as we need to add new sections.

I propose to refactor it to separate the data from the presentation. The data could be stored in a tree of resources:

CreditsSection:

  • title
  • optional logo
  • optional URL
  • Array[CreditsSubsection]

CreditsSubSection:

  • optional title
  • Array[CreditsEntry]

CreditsEntry:

  • display name
  • github username (optional)
  • email addresses: Array[String]
  • url (optional)

Having done that, we could then make some scenes that would be instanced to display this data.

The point of having the github username / email addresses / ... data is that we have patches in the git history with different real names & email addresses for the same person; and even if all of those line up, it can actually be hard to match them up to GitHub usernames. Since we have to maintain this data anyway, we may as well store it all in one place. However all 3 of those identifiers should be optional.

XP Summary (total 375)

Subdomain Skill XP
Engineering: Gameplay & Systems Programming Problem Solving 50
Engineering: Gameplay & Systems Programming Creativity & Design Thinking 50
Engineering: Gameplay & Systems Programming Technical Literacy 75
Game Design: Game Feel & UX Problem Solving 50
Game Design: Game Feel & UX Creativity & Design Thinking 75
Game Design: Game Feel & UX Technical Literacy 75

Metadata

Metadata

Assignees

Type

No type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions