Nearu moderation console
An administration console for reviewing posts, managing accounts and configuring a social product.
Used by Administrators managing content, user accounts and product settings.
Running a social product involves more than the public feed. Nearu’s Next.js administration console brings together post review, account restrictions and profile options, alongside configuration screens for moderators, credit packages and subscriptions.
The screens connect to administrative APIs through a shared Axios client. TanStack Query handles server data and mutations, while Better Auth provides the authentication client.
- Context
- Company project, Techsfera
- Interface
- Next.js, TypeScript and Tailwind CSS
- Moderation
- Post review, visibility controls and account restrictions
- Configuration
- Moderators, credit packages, subscriptions and profile traits
- API access
- Axios, TanStack Query and Better Auth
Reviewing posts and accounts
Post-management screens let an administrator inspect a post, accept it, change its visibility or remove it. Account screens provide profile details and controls for blocking and unblocking users, with filtering and sorting to navigate the lists.
Actions such as hiding a post or blocking an account open a confirmation dialog. The dialog names the action before the request is sent, and mutation state feeds the button’s loading indicator.
Keeping product settings manageable
The console includes forms for creating and editing moderators, credit packages and subscription plans. Trait-management screens handle the profile options used by the product, including professions, personalities, activities and feelings.
Shared forms, dialogs and table components give these screens a consistent structure. The moderator, credit-package and subscription creation forms currently have placeholder submit handlers; they represent interface work rather than completed backend workflows.
Connecting actions to the backend
A shared Axios client sends credentialed requests to the administrative API and turns backend failures into error messages. Query hooks keep data fetching and mutations separate from the screen components.
Better Auth handles the client session. The backend also checks the session’s admin role in middleware before allowing access to protected administrative routes. The permission check lives on the server as well as the interface.