Can the forum add auto-save drafts and author/date-range search?

[Luke45]

As a long-time user of this forum, I'd love to see a feature that allows users to save draft posts and private messages. I often start composing a detailed technical reply but have to abandon it due to an interruption, losing all my work. For the moderators and developers, is implementing an auto-save or draft function technically feasible given the current platform? Beyond that, I think a more advanced search filter, allowing us to search within specific subforums or by post author within a date range, would significantly improve research and discussion quality. What is the general process for reviewing and prioritizing such feature requests, and are there any plans for a user-facing roadmap?

[JeffreyUG]

Auto-save and drafts are technically feasible. For a minimal viable MVP, store draft content in the browser (localStorage or IndexedDB) and optionally sync to the server when online. Drafts would apply to both posts and private messages, with a small recovery widget if the tab closes unexpectedly. Suggested defaults: autosave every 30–60 seconds, show a timestamp, and give users a one-click restore. Also handle multi-device edits via optional cross-device sync, which would require a conflict-resolution strategy. Finally, communicate privacy and retention policy clearly before enabling drafts.

[Jack32]

Advanced search: yes. Start by indexing fields: forum/subforum, author, date, tags, and content. UI can include: multi-select subforums, author autocomplete, date-range picker, and saved searches. For performance, plan a backend rollout (Elasticsearch, OpenSearch) and gradually expose 'within date range' and 'author' filters. A lightweight prototype could begin with text search plus a few filters and scale to fielded search.

[Jonathan.M]

Feature request process: implement a simple intake form or issue in your repo or productboard. Use user stories and acceptance criteria. Apply a prioritization framework (RICE or ICE). Require a quick validation from a few beta users. Provide a rough ETA and a rollout plan. Measure adoption and satisfaction after release; iterate.

[VioletL]

Roadmap transparency: propose a quarterly public roadmap post and monthly updates. Create a beta program and invite community members to test drafts. Track success metrics (draft save rate, feature usage, time to produce a post).

[AmeliaSR]

UX considerations: show clear draft status, auto-save indicators, and automatic versioning. Provide conflict resolution if drafts are edited offline on multiple devices. Provide export/import or save to cloud" option. For privacy, ensure drafts remain private by default until published.

[CharlesL]

Suggested message to moderators/devs: share a one-page spec including: auto-save interval, draft storage scope (posts vs DMs), conflict-resolution policy, data retention, privacy/compliance notes, and a proposed advanced search feature with scope and MVP. Propose a pilot program with a fixed timeline and success metrics, and request a public roadmap placeholder while awaiting prioritization.