Document Management System Development

I am looking for an experienced developer who has built a document management and template feature similar to the following specification: Feature Overview: • Documents Page: • Sub-menu 1 – Player Documents: • A hub for documents received from various events with features like search (by player name, event name, document name) and multi-filters (date range, event name, document status, submission info). • Ability to add offline-uploaded documents (image/PDF) that are tagged accordingly. • Clicking on a document row should display an overlay with details and options for verification or flagging. • A consent popover appears when attempting to edit a document. • Sub-menu 2 – Templates: • A repository for reusable document templates. • Actions on template rows include selecting, downloading, editing, duplicating, deleting, and renaming. • Draft functionality for incomplete templates. • A “Create template” button leads to a dedicated template creation page. • Document Editor: • Banner section with zoom and page navigation, preview, draft, or final save options. • A left section for editing the document name (editable on hover), accessing search and custom fields, and pre-filled registration data. • A right section managing all fields as layers with the ability to reorder and access field formatting options. • Support for tooltips and conditional fields (where fields appear only after an anchor question is answered). • Player Interaction: • A flow where players or guardians fill in personal details, review or edit pre-filled documents, and proceed through a guided form with validation prompts, leading to review and payment. Project Requirements: 1. Previous Work & Examples: • Please provide examples or case studies of similar work (especially if you have developed document management features or digital signing/document sealing functionality). 2. Code Sharing & Ownership: • It is critical that any code delivered is original work or that you have the legal rights to share and license it. • If you intend to incorporate any open source components, they must be under permissive licenses (e.g., Apache 2.0, MIT, or similar) that allow integration with a proprietary, closed source system. • The final code and deliverables must be fully assignable to me without any encumbrances. 3. Technical Stack: • I am open to suggestions regarding the best technology stack for this feature, but it must be compatible with our existing closed source application environment. 4. Documentation & Support: • Complete documentation of the code and setup instructions is required. • A brief period of post-delivery support for integration issues is appreciated. Additional Notes: • I am particularly interested in understanding if this feature has been built before by someone, and if so, what the approach was. • Please clarify if any third-party libraries or open source components will be used, and ensure that their licenses are compatible with proprietary usage. • Feel free to ask any questions for further clarification. Timeline & Budget: • Please include your estimated timeline and budget for this project in your proposal. Thank you, and I look forward to reviewing your proposals!