WIP: Dioxus Bootstrap migration — hero_foundry #11
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_foundry!11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_dioxus_bootstrap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
DO NOT MERGE
Dioxus WASM frontend migration per lhumina_code/home#26
Add hero_foundry_ui_wasm crate that replaces the Askama/HTMX templates with a fully reactive Dioxus WASM app using dioxus-bootstrap-css v0.1.6 for Bootstrap 5.3 components. All 14 templates (base, base_global, index, blob, tree, commits, repo_list, docs, api_explorer, mcp, plus 4 partials) are migrated to Dioxus components with proper Bootstrap classes via dioxus-bootstrap-css (Navbar, Container, Row, Col, Card, Table, Button, etc.). Server changes (hero_foundry_ui): - Feature-gate askama as optional (default enabled) - Add --dist CLI arg for serving WASM dist directory - Add /assets/{*path} route for static file serving - Add tokio "fs" feature for async file reads Compiles on both native and wasm32-unknown-unknown targets.mik-tf referenced this pull request from lhumina_code/hero_os2026-03-16 16:34:04 +00:00
Pull request closed