SolidConnect Scoreboard Displays
This project is to help designers and CSS developers create and test displays for SolidConnect Scoreboards.
Purpose
- Provide fixed HTML scoreboard templates for supported sports with example data.
- Show how display design work should happen in CSS.
- Provide example themes that demonstrate different scoreboard design approaches via CSS.
Core Rules
- HTML structure is fixed and must not be changed.
- CSS files define the designs and are the place to build new displays.
- Theme loading is query-string based (
?theme=<theme-name>) and maps to files inassets/displays/<sport>/.
Project Structure
.
├── index.html # Theme selector / preview links
├── australianrules.html # Fixed Australian Rules scoreboard markup
├── cricket.html # Fixed Cricket scoreboard markup
├── assets/
│ ├── main.css # Shared/global base styles
│ ├── index.css # Styles for index page
│ └── displays/
│ ├── australianrules/ # Australian Rules theme examples
│ ├── cricket/ # Cricket theme examples
│ ├── ads.css # Shared ad display styles
│ └── slideshow-*.css # Shared slideshow styles
└── CHANGELOG.md
How It Works
australianrules.htmlandcricket.htmlread thethemequery parameter.- The page then loads
assets/displays/<sport>/<theme>.css. - The scoreboard root gets a class in this format:
scoreboard--<sport>-<theme>
This makes it possible to scope theme styles cleanly.
Getting Started
- Open
index.htmlin a browser. - Choose a theme link to preview an existing design.
- Edit or create CSS in the relevant folder:
assets/displays/australianrules/assets/displays/cricket/
- Refresh the page to view updates.
Creating a New Display
- Pick the target sport (
australianrulesorcricket). - Copy an existing theme CSS file as a starting point.
- Rename it using your new theme name, for example:
assets/displays/cricket/my-new-display.css
- Preview it by visiting:
cricket.html?theme=my-new-display
- Keep selectors compatible with the existing HTML structure.
Notes for CSS Developers
- Treat HTML class names and hierarchy as a contract.
- Build designs with overrides/scoped selectors rather than markup changes.
- Use existing themes as implementation examples and reference patterns.
Versioning
See CHANGELOG.md for release history and updates.