Blazor UI from Wireframe
Budget: $15 – $25 USD
I have a complete wireframe of an application and I want it turned into a working Blazor Server front-end built strictly with Radzen.Blazor components. Every visual element in the sketch needs to become a reusable, well-named component so that future pages can be assembled quickly from this library.
Here is what I need from you:
• Replicate the look and feel of the wireframe exactly, but do it the “Blazor way”—layouts, partials, and Radzen components such as RadzenPanelMenu, RadzenDataGrid, RadzenTextBox, etc.
• Break the UI down into small, self-contained components (e.g., NavMenu, HeaderBar, StatsCard, EditableGridRow) and place them in a clean folder structure.
• Hook up basic two-way binding and sample in-memory data so that forms, grids, and navigation all behave realistically even though no real back-end logic is required yet.
• Keep styling inside Radzen themes or scoped CSS so nothing leaks. No third-party libraries beyond Radzen.
• Deliver a runnable Blazor Server project (VS/VS Code compatible) plus a short README explaining how to add new pages using the component library you create.
Acceptance criteria
– UI matches the wireframe at desktop resolution with standard Radzen responsiveness.
– All interactive elements (navigation links, buttons, editable fields) demonstrate working state changes.
– Components are reusable, clearly named, and documented with XML comments.
– Solution builds and runs with a single `dotnet run`.
If you have solid experience with Blazor Server and Radzen, this should be a straightforward build. I’m ready to share the wireframe as soon as we start.
Here is what I need from you:
• Replicate the look and feel of the wireframe exactly, but do it the “Blazor way”—layouts, partials, and Radzen components such as RadzenPanelMenu, RadzenDataGrid, RadzenTextBox, etc.
• Break the UI down into small, self-contained components (e.g., NavMenu, HeaderBar, StatsCard, EditableGridRow) and place them in a clean folder structure.
• Hook up basic two-way binding and sample in-memory data so that forms, grids, and navigation all behave realistically even though no real back-end logic is required yet.
• Keep styling inside Radzen themes or scoped CSS so nothing leaks. No third-party libraries beyond Radzen.
• Deliver a runnable Blazor Server project (VS/VS Code compatible) plus a short README explaining how to add new pages using the component library you create.
Acceptance criteria
– UI matches the wireframe at desktop resolution with standard Radzen responsiveness.
– All interactive elements (navigation links, buttons, editable fields) demonstrate working state changes.
– Components are reusable, clearly named, and documented with XML comments.
– Solution builds and runs with a single `dotnet run`.
If you have solid experience with Blazor Server and Radzen, this should be a straightforward build. I’m ready to share the wireframe as soon as we start.