How to structure a single Oqtane module with multiple pages (Admin dashboard style)? #5931
Replies: 4 comments 10 replies
-
|
The Core Misunderstanding (and why your instinct is correct) Many people assume: That assumption is wrong for complex business apps. Oqtane modules are functional units, not pages. An ERP Admin module with: …is exactly what a single module is meant to represent. ⸻ The Official / Intended Oqtane Pattern ✅ One module ✅ Multiple Razor components ✅ Internal routing via ActionLink This is the same pattern used by Oqtane core admin modules. ⸻ How Oqtane Actually Thinks About Pages An Oqtane module has:
|
Beta Was this translation helpful? Give feedback.
-
|
@Bhushan02-dot there are various ways you can approach this, but at the end of the day the most important aspect to understand is routing. This video describes the fundamentals of Oqtane routing: https://www.youtube.com/watch?v=77_-4OLat_o&list=PLYhXmd7yV0elLNLfQwZBUlM7ZSMYPTZ_f&index=2 (the video is old however the core concepts in Oqtane routing have not changed). So @leigh-pointer is correct - you could use a single module for the ERP Admin. Lets assume you have a "page" with a route of /erpadmin in your site which is where you want to expose all of the ERP Admin functionality. You could have a single ERP Admin module instance on this page (ie. let's assume it is ModuleId: 1). Each route Action can then relate to a Razor component: etc... The only challenge remaining is how to surface your navigation menu so that users can click links which correspond to the routes above. I am assuming that the navigation menu is expected to be displayed on every page so I would suggest embedding it in your Theme component and simply hard-coding the Urls (similar to a default Blazor application and the NavMenu component). Hard-coding is not really a problem as there are a finite number of menu options in your application. |
Beta Was this translation helpful? Give feedback.
-
|
@sbwalker , @leigh-pointer
index.razor : |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hii @sbwalker
I’m building an ERP-style application on Oqtane and I’m a bit confused about the correct/official way to handle multiple pages within a single module.
My scenario
I have one functional module (for example: ERP Admin / Master Data) but it contains multiple pages, such as:
This is similar to an Admin Dashboard, where:
My confusion
In Oqtane:
So I’m unsure about the recommended pattern for:
One module with internal routing?
What I’m looking for
Official or recommended Oqtane approach
Any example modules (admin/dashboard style)
Best practice for ERP or large business apps

below project is already blazor wasm and we want migrate in oqtane
Beta Was this translation helpful? Give feedback.
All reactions