Skip to content

feat(dashboard): add polished Fortal dashboard example - #95

Draft
leoafarias wants to merge 18 commits into
mainfrom
feat/fortal-dashboard
Draft

feat(dashboard): add polished Fortal dashboard example#95
leoafarias wants to merge 18 commits into
mainfrom
feat/fortal-dashboard

Conversation

@leoafarias

Copy link
Copy Markdown
Member

Stack

Depends on #80 and intentionally targets feat/fortal-polish. Review only the dashboard example delta in this PR. Merge #80 first, then retarget this PR to main.

Description

  • Adds a workspace-only, non-published Fortal dashboard example for macOS and web, covering overview, customers, orders, settings, and the component gallery.
  • Preserves the responsive sidebar/drawer, avatar and compact kebab action surfaces, data-grid interactions, and live theme controls.
  • Consumes feat(fortal): align visuals with Radix Themes 3.3.0 #80's current public Remix APIs. Rich product triggers use a small dashboard-local popover composition; this PR makes no Remix library/API changes and adds no dependency or lockfile changes.

Related Issues

Related to #80.

Visual Evidence

Desktop (1440x900) and compact (390x844) layouts were verified locally, including both account menus, compact row actions, and the navigation drawer, with no console errors or warnings. Screenshots are pending upload before this draft is marked ready for review.

Validation

  • fvm dart run melos run ci — passed; 17 dashboard tests and 2,105 Remix tests.
  • cd packages/dashboard && fvm flutter analyze — passed with no issues.
  • cd packages/dashboard && fvm flutter build web — passed.
  • cd packages/dashboard && fvm flutter build macos --debug — passed.
  • git diff --check — passed.

Checklist

  • My PR includes unit or integration tests for all changed/updated/fixed behaviors.
  • I have updated or added relevant documentation (doc comments with ///).
  • I am prepared to follow up on review comments in a timely manner.

Breaking Change

Does this PR require users of the package to manually update their code?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

Preserve the origin/main component contracts while adding the canonical Fortal theme, visual recipes, effect rendering, and an explicit parity/deferred-capability manifest.

Render the generated Fortal wrappers from the Mix prerequisite and keep functional component expansions out of this visual-only layer.
Rename fortal*Styler helpers to fortal*Style so @MixWidget infers Fortal*
names from the Style suffix, and surface every recipe parameter
(highContrast, fallbackLength, etc.) on the generated widgets.
Base automatically changed from feat/fortal-polish to main July 30, 2026 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant