Building Admin Portals with React and Node.js

Start with roles, not screens

A good admin portal starts with who can do what. Once roles are clear, navigation, actions, and API contracts become easier to reason about.

• List the actions each role can perform before naming pages.
• Keep navigation role-aware, but keep authorization on the server.
• Write API errors that explain whether the issue is permission, validation, or state.

Make states explicit

Loading, empty, validation, retry, and permission states should be designed early. Admin users work fast, and unclear states slow them down.

• Use skeletons for known layouts and concise empty states for missing data.
• Keep destructive actions behind confirmation and audit context.
• Make retry behavior safe for exports, sync jobs, and bulk updates.

Keep contracts boring

The frontend should not guess domain rules from scattered payloads. Typed API responses and predictable errors make portals easier to test and extend.

• Use shared status names across lists, detail pages, and notifications.
• Avoid one-off response shapes for similar tables.
• Review pagination, sorting, and filtering before the UI is built.

What I look for in review

I check whether the portal can be used during a messy workday: partial data, slow APIs, denied actions, duplicate clicks, and users jumping between list and detail pages.