Canvas
#0C1117FC Coach #0D1117A shared foundation for every OLVYX Lab app. The FC Club Tracker look is the provisional visual base, with FC Coach differences preserved as visible choices. Product-only patterns have dedicated sections below. Every specimen is HTML and CSS, with small JavaScript interactions.
Review the paired colors and component variants below. Your selections will turn this draft into the final global standard. Existing app design references remain untouched.
FOUNDATIONS / COMPONENTS / PROJECTSEach pair shows the two original values edge to edge, with no border or gap between the colors. FC Club Tracker is on the left, FC Coach on the right. The left palette powers this draft while your choices are open.
#0C1117FC Coach #0D1117#171D24FC Coach #161B22#232A32FC Coach #21262D#0D1218FC Coach #0D1117#2B3540FC Coach #30363D#FF7800FC Coach #FF7A00#FF922EFC Coach #FF9A3D#F3F4F6FC Coach #F0F3F6#A8B1BFFC Coach #8C959F#718096FC Coach #8C959F#22C55EFC Coach #3FB950#EF4444FC Coach #F85149#4EA1FFFC Coach #1F6FEBFC Club Tracker warning #F59E0B and FC Coach draw #F2B84B are both warm amber, but they communicate different facts. Keep both semantic names until you decide whether their hues should match.
Both use compact type, but the font family and weight hierarchy differ.
The orange hues and label colors differ. Compare these on the same background.
The Club treatment is a filled tab; Coach adds a left rail.
The Club variant outlines the selected row. Coach uses an orange rail and fade.
This is the provisional global palette based on FC Club Tracker. The paired alternatives above stay open for review; semantic names describe use, not a final hue choice.
The provisional global typography uses the Club Tracker pairing. The Coach system-font option remains visible in Compare & choose.
Use mono for numbers that people compare or copy. Keep prose in Inter.
Inter 400 / 500 / 600 / 700 / 800IBM Plex Mono 400 / 500 / 600Use a clear metric name in prose and reserve abbreviated IDs for metadata.
Shared compact rhythm. The 4/8/12/16/24/32/48 scale is provisional; FC Coach also uses 14/20/28/36 in its retrospective reference.
Use the scale for padding, gaps, and section rhythm.
Use 7–10px for controls and panels; full pills for compact status labels. Prefer a one-pixel border to heavy shadow.
border: 1px solid var(--border)The Club Tracker shell is the provisional web pattern. The FC Coach desktop shell differs in active rail and sidebar width; see the comparison above.
Real links and layout elements, scaled down for the reference.
The next useful action at a glance.
ReadyFour columns on wide screens, two on medium screens, one on narrow screens.
One primary action per decision area. Use clear verbs and preserve a visible secondary path.
Hover, focus, press, and disabled states are live.
Use links for navigation, buttons for changes, and an ellipsis when an action opens a confirmation step.
“Commit import” is clearer than “Continue” at the final approval gate.
Labels, help, validation, and unknown values remain visible. The shared dropdown already draws on the FC Coach field, arrow segment, and dark option menu.
Choose a value, open the menu, or use Arrow keys, Enter, and Escape. The disabled example stays unavailable.
The selected option uses an orange label on a warm dark row. Selecting an option closes the menu.
Try entering a search, changing a dropdown, and submitting the example form.
Keep “Unknown” distinct from “No” when the underlying fact is missing.
Use plain text alongside color. Tell users what happened and what they can do next.
Compact labels for rows, cards, and summary areas.
Placed near the decision or result they describe.
Records and history were saved.
Resolve each item before you commit.
Check the connection and try again.
Show where the user is, confirm destructive changes, and acknowledge lightweight success.
Use clear headings, aligned values, readable status text, and an explicit empty state. Tables, cards, and metrics should use the same global tokens.
Use semantic table markup when comparing rows. Put the identity first, then status and last change.
| Item | Status | Updated |
|---|---|---|
| Example A | Ready | Today |
| Example B | Review | Yesterday |
Say what is missing and offer a useful next step.
Create the first item to fill this workspace.
Accessibility is part of the component contract, from keyboard states to honest status messages.
Scan by name first, then exact card, score, and ownership. Mobile rows become readable cards.
Table on desktop; stacked record on mobile. Values are illustrative.
| Player | Card | Score | Ownership | Status |
|---|---|---|---|---|
| Alex Morgan CLUB-000184 | Special · 90 OVR · ST | 91.8 | First owner | Ready |
| Sam Kerr CLUB-000185 | Gold · 89 OVR · ST | 87.4 | Unknown | Review |
Exact identity and key attributes without relying on an image.
State the missing content and offer the next useful action.
Add a card from the Player Database or import a reviewed club export.
These examples apply to the club product: exact-card import, ownership history, card views, and squad placement. The components above remain global.
Upload is followed by exact-card review and an explicit commit.
Preview changes before anything is saved.
Keep or remove each missing copy explicitly. Import never deletes it for you.
Events expose provenance and keep changes understandable.
Imported from a reviewed CSV batch.
First owner changed from unknown to yes.
Evolution details attached to the same permanent club entry.
Use tabs for related views of the same item.
Position slots are real buttons; the pitch lines are CSS.
These patterns belong to the Coach product. Their dark surfaces, action hierarchy, and status rules use the shared foundation; the details below describe recording and coaching workflows.
Pause on a decision, choose a range, classify it, and save a durable observation. The timeline is CSS and the controls are HTML.
I forced the pass instead of recycling possession.
Manual observationW/D/L is a compact match result beside the score, separate from analysis and coaching quality. The warm draw color has a distinct meaning from a warning.
Choose one to three focus rules after reviewing a match. Show trend only when the evidence supports it; keep self-assessment distinct.
9 saved moments across 3 matches.
ImprovingLocal jobs, storage, provider cost, and automated analysis availability need explicit prerequisites and recovery copy.
Enough reviewed observations exist.
Evaluation evidence has passed review.
Only then can an automated package be built.
“Automated analysis available” says nothing about whether a match was analyzed.
Start with the global tokens and components. Add a named project section here only when a pattern or rule has meaning in one product.
tokens.css and styles.css as the visual baseline.This shared reference was assembled from the public FC Club Tracker design page and the local FC Coach retrospective design document. Both originals are preserved.
FC Coach source: local retrospective HTML, inspected 25 September 2026. This page uses no bitmap images or SVG illustrations; visual elements are HTML and CSS.
The controls here demonstrate interaction and styling. They do not connect to either app's data or change either app.