Files
branderson f3d85f5239 docs: credit Texgriddy and Fredoka; rename the color scheme to Slate
The portal's look is inspired by Texgriddy, an ES-DE theme by
Weestuarty, recreated in CSS without any of its files. The README and
the portal doc now say so, and credit the Fredoka font. The color
scheme was named after Texgriddy's "Chilled" scheme; it's now Slate.
2026-10-15 16:16:00 -07:00

4.6 KiB

Discovery Portal

Overview

The public pages use an arcade portal layout styled after 2010-era Flash game sites, with a homepage built for discovery instead of lists of recent changes. Account and admin pages keep the application layout.

Shell

PortalLayout (frontend/src/components/portal/) wraps the homepage, browse, game, player, favorites, playlists, downloaded and dashboard routes:

  • A framed fixed-width page (1180px, desktop first)
  • A wordmark built from the Site Name setting, with the optional Tagline setting underneath
  • Search, and a user menu holding the library, account and admin links and the mature content switch
  • Genre categories linking to browse by tag: Action, Adventure, Puzzle, Shooter, Platformer, Sports, Strategy, Driving, Escape the Room and Dress Up, plus Animations
  • Keyboard shortcuts: / focuses search, R opens a random game

Color Schemes

Portal colors are token sets in components/portal/schemes.ts. Each scheme sets --p-* properties for the portal's own styles (portal.css) and overrides the shadcn tokens (--background, --primary, ...) so shared components match. The tokens are applied to <body> while the portal is mounted, which takes precedence over the app theme on <html> and also reaches dialogs and menus rendered into the body.

One scheme ships, Slate (slate background, sage boxes). Adding a scheme means adding an entry to PORTAL_SCHEMES; no component changes are needed.

The portal's look is inspired by Texgriddy, an ES-DE theme by Weestuarty: the framed page, glossy tiles with a metallic ring, outlined info boxes, capsule buttons and the slate and sage palette. It was recreated from scratch in CSS; none of Texgriddy's files, images or fonts are used.

Display text uses Fredoka (OFL, bundled via @fontsource-variable/fredoka); body text uses Verdana.

Homepage

  • Game of the Day: the same pick for everyone on a given day, from the Flashpoint curated playlists, with a link to the previous day's pick
  • Time Machine: games released in a given week, starting from a random day between 2005 and 2014. Users can step by week, jump to a random day, or click the date to pick any day. "See all" opens browse filtered to that week. Only games with a day-precise release date are included.
  • Jump back in: the signed-in user's recently played games
  • Playlist shelves: three random curated playlists with a sample of their games

See the Discovery API.

Game Page

Game detail and play are one page (views/GamePage.tsx); the /play routes open the same page with the game already started. Shared playlist links keep the application's detail and player views.

  • Stage: the game's screenshot with its logo and a Play button (or Enter). Playing loads the game in place, starting a play session and fetching the game data if needed. Saves, the Ruffle / original Flash Player switch and Fullscreen sit under the game; in fullscreen the player's own header bar returns. Platforms that can't run in the browser or be streamed point to the Flashpoint Launcher.
  • About this game: description, notes, and release date, developer, publisher, series, platform, play mode and language; developer, publisher and series link to browse.
  • Side boxes: the signed-in user's plays of this game, the rating, and tags linking to browse.
  • Favorite and Add to playlist for signed-in users.
  • More like this: related games.

Default Ordering

Browse lists default to a shuffle instead of title order. The shuffle is seeded and the seed is kept in the URL (seed=), so paging, back navigation and shared links keep the same order; Reshuffle picks a new seed. Searches still default to title order.

Mature Content

Flashpoint's extreme game flag is not set in current metadata, so mature games are identified the way the Flashpoint Launcher does: by the tag filter groups marked extreme in preferences.json (falling back to .preferences.defaults.json, then to the launcher's default groups: Pornography, Fetishes, Violence, Bigotry and Pornography Extreme).

MatureContentService resolves those tags to game IDs once per database load. Search, random, related games and discovery exclude them unless the request sets showExtreme=true.

Users opt in with Show mature games in the user menu. The choice is stored in the browser (flashpoint-mature-content), and for signed-in users also in the account's show_mature setting, which is applied when they sign in on another browser.