Custom Online Document Platform
Budget: $250 – $750 USD
I need a secure, browser-based space where my team can create, edit, and organise documents without bouncing between different tools. For this first milestone I only need a lean MVP: user sign-up/login, folder hierarchy, and a rich-text editor with basic formatting options. A clean, fast interface matters more than packing in every feature on day one, but the code must be modular so we can bolt on real-time collaboration, spreadsheet or presentation support later.
Any modern, well-supported stack is fine—Laravel + Vue, Django + React, Node + Next, or similar—so long as it’s containerised and easy to deploy to AWS or DigitalOcean. Please outline which editor, storage, and auth libraries you’d weave in (e.g., CKEditor 5, TipTap, OnlyOffice, AWS S3, JWT) and why they’re a good fit.
Deliverables
• Source code in a Git repo
• Dockerfile / docker-compose for one-command deployment
• Setup guide and concise architecture diagram
• Quick screen-share demo of the working MVP
Acceptance criteria
• Users can sign up, log in, create, edit, save, and download a document without page reload.
• Role-based access: owner, editor, viewer.
• Documents persist to S3-compatible storage.
• Unit tests cover critical endpoints.
If you’ve tackled something similar, share a link or demo in your proposal along with an estimated timeline. Let’s build a solid foundation we can keep expanding.
Any modern, well-supported stack is fine—Laravel + Vue, Django + React, Node + Next, or similar—so long as it’s containerised and easy to deploy to AWS or DigitalOcean. Please outline which editor, storage, and auth libraries you’d weave in (e.g., CKEditor 5, TipTap, OnlyOffice, AWS S3, JWT) and why they’re a good fit.
Deliverables
• Source code in a Git repo
• Dockerfile / docker-compose for one-command deployment
• Setup guide and concise architecture diagram
• Quick screen-share demo of the working MVP
Acceptance criteria
• Users can sign up, log in, create, edit, save, and download a document without page reload.
• Role-based access: owner, editor, viewer.
• Documents persist to S3-compatible storage.
• Unit tests cover critical endpoints.
If you’ve tackled something similar, share a link or demo in your proposal along with an estimated timeline. Let’s build a solid foundation we can keep expanding.