Build websites and apps by describing what you need

Build a client request portal for a small translation studio. Clients submit a project with language pair, deadline and notes, then follow its status. Staff assign a translator and move requests through Received, In progress and Delivered. Use fictional sample data, a PostgreSQL backend, sign-in and separate client and staff permissions. Provide a clear responsive interface and setup instructions.

Include these capabilities:
- Create and refine screens, forms and navigation through conversation
- Add a database, sign-in and server-side access rules for your app
- Check the live preview and improve individual flows with follow-up requests
- Publish the project and connect services using your own accounts
- Inspect the generated source and export it to continue with your own tools

Build the complete working project with its routes, data model and interactions. For saved or private data, implement persistence, authentication and server-side permissions. Keep API credentials on the server. For external services, document the required setup and use test mode until real accounts are connected. Do not present a simulated integration as a completed live connection.

Make the interface responsive, with accessible labels, keyboard navigation and visible focus. Include loading, empty, validation and error states. Use clearly labelled sample data, never invented customer testimonials or results. Choose a visual direction suited to this project and keep typography, spacing and controls consistent. Explain how to run, test, export and deploy the source.

Verify this end-to-end flow:
Create two clients and a staff account. Submit and assign a request, change its status and sign in again to confirm it persisted. Verify that each client can read only their own requests, including through direct API requests, and that staff-only controls are protected on the server.